Yes and no. The file is there
primarily for the developers, so they can test if everything works reliably before it goes "really public", and so they have a feeling of how it is intended to be used.
It is the exact same project as the normal wx26 project, except that it a lot more comfortable, because you don't need to change paths every time you check out.
For everybody else, I think it is dangerous to use it because it is really, really good. If you have used it once, you will be tempted to use it in all your projects immeditately. But if you do that and we change one tidy bit, you will have to change all projects again. So better wait until it is "officially out".
Yiannis already found one issue today. The edit compiler options dialogs filter the variables through
wxFileName, and
wxFileName does some completely unnecessary Smart replacements which break the scope operator (you get $\(:wx) instead of $(::wx) in the edit box).
This is nothing that prevents the new build scheme from working, but it is quite annoying when you edit your project files because you have to correct it every time, which is absolutely unnecessary.
So the scope resolution operator will have to be changed (better than rewrite half of the application). Yiannis is currently testing with '#', giving the scheme
$(#wx.base), this seems to do fine.
