Developer forums (C::B DEVELOPMENT STRICTLY!) > Development
Modified & Improved wxWidgets Project Wizard
Biplab:
Thanks a lot. :D
I'll try to commit it tomorrow (I need to clean the code ;)).
Biplab:
A Big update has been applied today. :D
Newer Features:
* Wizard now Wizard now supports creation of wxDialog / wxFrame based app.
* Wizard now supports wxFormBuilder to be selected as 3rd-Party GUI Builder alongwith wxDialog / wxFrame option.
Modifications:
* PCH include header has been reverted to wx_pch.h
* PCH Pre-Processor definition has been changed to WX_PRECOMP
Many Thanks To: :D
* rjmyst3 and byo for raising the feature request.
* byo for supplying the wxDialog template.
* rjmyst3 for testing the development versions and providing valuable feedback for tighter integration with wxFormBuilder.
Known Issues:
* There is one issue with PCH support. Presently all the apps generated will compile successfully. But there will be an additional amount of Pre-Compiled Header generated in some cases.
wxSmith support will be added soon.
Committed in revision 3543 and 3544.
Regards,
Biplab
byo:
--- Quote from: Biplab on February 25, 2007, 07:37:11 pm ---wxSmith support will be added soon.
--- End quote ---
Should I start working on the "special function" added to squirrel? IT should be done in one day, but probably current Message-Box implementation would be better for testing purposes ;)
BYO
Biplab:
--- Quote from: byo on February 26, 2007, 01:01:07 am ---Should I start working on the "special function" added to squirrel? IT should be done in one day, but probably current Message-Box implementation would be better for testing purposes ;)
--- End quote ---
Please add it. As the first part is over, adding wxSmith support should not take much time. ;)
Biplab
rjmyst3:
--- Quote from: Biplab on February 25, 2007, 07:37:11 pm ---Known Issues:
* There is one issue with PCH support. Presently all the apps generated will compile successfully. But there will be an additional amount of Pre-Compiled Header generated in some cases.
--- End quote ---
I did some more looking into this. The way wxFB works right now is, if the "precompiled_header" property has content, the #include statement will be generated, but if left empty, wxFB does not generate anything.
So I suggest:
If the user wants pch support, set wxFB's "precompiled_header" property to "wx_pch.h", and wxFB will generate this:
--- Code: ---#include "wx_pch.h"
#ifdef __BORLANDC__
#pragma hdrstop
#endif //__BORLANDC__
#ifndef WX_PRECOMP
#include <wx/wx.h>
#endif //WX_PRECOMP
--- End code ---
If the user does not want pch support, set the property to nothing (an empty string) and wxFB with generate this:
--- Code: ---#ifdef __BORLANDC__
#pragma hdrstop
#endif //__BORLANDC__
#ifndef WX_PRECOMP
#include <wx/wx.h>
#endif //WX_PRECOMP
--- End code ---
The wizard should be able to modify the contents of wxFB's .fbp file to change the property, just as it would any other source file. It is just xml.
Will this solve the pch problem?
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version