Developer forums (C::B DEVELOPMENT STRICTLY!) > Development
Modified & Improved wxWidgets Project Wizard
RJP Computing:
--- Quote from: Biplab on February 16, 2007, 08:33:47 pm ---@rjmyst3
...
wxFB does not support addition of Event Handling at the present moment. So if an user regenerates the UI in wxFB, it can overwrite original source. Though subclassing is an option which is available in wxFB, but it could make the matter complicate for newbies (I could remember my ordials even some time back ;) )
...
--- End quote ---
wxFormBuilder does support event handlers now as well as having a wizard to generate your inherited class. These are in in wxFormBuilder v3.0+
byo:
--- Quote from: Biplab on February 16, 2007, 08:33:47 pm ---@byo
I've tried only old wxSmith plugin long ago. So I need ur help to add support of this. What I suggest is to add another page (Just like version selection page) where user can select wxSmith or wxFormBuilder or None for GUI development.
IMHO, adding support for wxSmith would be far more easier as it's already integrated. Though I don't use it, I appreciate your hard work involved in that plugin. :)
--- End quote ---
To integate wxSmith into current wizard, two things have to be done:
* Sources need few changes - this could be handled by [IF ...] macros so I guess there won't be a problem with it :)
* wxSmith must be notified about new project and must create some internal bindings. I thought about adding few functions responsible for this task and add them to squirrel so script could call them.
Of course this is my first idea :)
Regards
BYO
rjmyst3:
--- Quote from: Biplab on February 16, 2007, 08:33:47 pm ---In my opinion we can add the file (wxFB project file) to C::B Project as a dummy one which will not be compiled or linked. It will open externally in wxFB.
--- End quote ---
This should work.
--- Quote from: Biplab on February 16, 2007, 08:33:47 pm ---wxFB does not support addition of Event Handling at the present moment. So if an user regenerates the UI in wxFB, it can overwrite original source. Though subclassing is an option which is available in wxFB, but it could make the matter complicate for newbies (I could remember my ordials even some time back ;) )
--- End quote ---
The files generated by wxFB are not meant to be edited at all. The intended approach is that users create a class which inherits from the class that wxFB generates. The newest version of wxFB will create this class for the user, upon their request, so it should be easier for new users to get started. The newest version will also generate event handlers.
--- Quote from: Biplab on February 16, 2007, 08:33:47 pm ---Do you want the wizard to stop generating the sample source and rather use files generated by the GUI builder; or you just want to add a GUI project file so that user can Copy-Paste it (Though this is a bad idea)? As I've said, adding support for wxSmith would be easier in this regard for the first option. One important point to note is the first option would require the wizard to be modified thoroughly and would break few important features. :)
--- End quote ---
I think we should create the sample with the GUI builder and use those files.
So, to sum up for wxFB, the wizard would generate the wxFB project file, the wxFB generated files, and the user's files which inherit from the generated classes.
TDragon:
The wizard works quite well and has progressed quite a bit. There are only two things of note:
1. wxpng[d] and wxzlib[d] were added unnecessarily to both my GCC and VC2005 projects. (shared, multi-lib, non-unicode)
2. The tooltip text for the new checkbox says "This is available for GCC only", implying that compilers other than GCC would not be able to use the debug libs.
Keep up the good work!
Biplab:
--- Quote from: RJP Computing on February 16, 2007, 09:19:09 pm ---wxFormBuilder does support event handlers now as well as having a wizard to generate your inherited class. These are in in wxFormBuilder v3.0+
--- End quote ---
I think I have missed it. I have compiled the recent svn build few days back. But didn't try using the event handling. :)
--- Quote from: byo on February 16, 2007, 09:53:03 pm ---To integate wxSmith into current wizard, two things have to be done:
* Sources need few changes - this could be handled by [IF ...] macros so I guess there won't be a problem with it :)
* wxSmith must be notified about new project and must create some internal bindings. I thought about adding few functions responsible for this task and add them to squirrel so script could call them.
--- End quote ---
* First one is easy. This code is available in cbplugin wizard (Handling [IF] macros) and I need to copy-paste that
* Second one I didn't understand. Please explain me a little bit. :)
By the way I'll try wxSmith to understand it.
--- Quote from: rjmyst3 on February 16, 2007, 10:11:18 pm ---This should work.
--- End quote ---
Then this can be done easily. :)
--- Quote from: rjmyst3 on February 16, 2007, 10:11:18 pm ---The files generated by wxFB are not meant to be edited at all. The intended approach is that users create a class which inherits from the class that wxFB generates. The newest version of wxFB will create this class for the user, upon their request, so it should be easier for new users to get started. The newest version will also generate event handlers.
--- End quote ---
Ok, then it can be tackled in following way.
This is when user does not want any GUI builder.
--- Code: ---#include "TestApp.h"
class TestFrame: public wxFrame
--- End code ---
This will be when user is using wxFB.
--- Code: ---#include "TestApp.h"
#include "TestFrameGUI.h"
class TestFrame: public TestFrameGUI
--- End code ---
where TestFrameGUI class will be generated by wxFB.
I hope for wxSmith the changes will be similar. :)
--- Quote from: TDragon on February 17, 2007, 02:22:51 am ---1. wxpng[d] and wxzlib[d] were added unnecessarily to both my GCC and VC2005 projects. (shared, multi-lib, non-unicode)
2. The tooltip text for the new checkbox says "This is available for GCC only", implying that compilers other than GCC would not be able to use the debug libs.
--- End quote ---
1. I checked that and I found that it works without them, too. :) I'll not make any further changes to this as this minimum config works fine with static and dll libs. Please don't misunderstand me, but changing this means I need to change the last two panels and as well as the script code itself. :)
2. I didn't add this to other compilers as there could be problems during linking. At least VC will not accept it. ;) But surely, if it works with other compilers, please inform me. I'll update the wizard. :)
Regards,
Biplab
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version