Developer forums (C::B DEVELOPMENT STRICTLY!) > Development

Modified & Improved wxWidgets Project Wizard

<< < (32/41) > >>

rjmyst3:

--- Quote from: Biplab on February 17, 2007, 07:48:35 am ---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.

--- End quote ---

Sounds Perfect!  :D

TDragon:

--- Quote from: Biplab on February 17, 2007, 07:48:35 am ---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. :)

--- End quote ---
What I'm saying is that your description is misleading. Saying that an option called "Use __WXDEBUG__ and Debug wxWidgets lib" is available for GCC only implies that non-GCC compilers can't use the debug wxWidgets lib -- which is obvioulsy wrong, since the wizard correctly generated a debug target for VC2005 using the debug libs. You just need to reword things.

Biplab:
Yes, TDragon I noticed that discrepancy after my commit. Actually in the code there is check so that it does not affect any other compilers. Somehow missed to change the text. ;)

I'll change that in next commit.

byo:

--- Quote from: Biplab on February 17, 2007, 07:48:35 am ---
* 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.

--- End quote ---

Ok, I've modified result of wxWidgets wizard little bit to support wxSmith and whole project is in attachment. I've also tried to change files right in wizard's files, but this may be useless since some changes to these files are required when using wxFormBuilder too. If I could make a suggestion, I propose adding these three macros:

* [IF NORMAL]
* [IF WXFORMBUILDER]
* [IF WXSMITH]
Then it would be really easy to modify template files to use one of three schemes.
wxSmith also require one more file (included as wxsmith/wxwizardframe.wxs in attachment), but that should be really easy ;)

About this second 'thing' - wxSmith adds some extensions to C::B projects - each resource is mapped to source/header files and to .wxs file (containing resource's structure or some required extra stuff). Usually these bindings are read from cbp file using C::B's extensions support . But when project is generated from wizard, there's no way to support it. So the first solution I've found is to add special wxSmith-related function to squirrel (and thus allowing them in wizards), which would notice wxSmith about new project and would let it create proper bindings. This function would be enough to properly add full wxSmith support for project.

Regards
  BYO

[attachment deleted by admin]

Biplab:
Thanks Byo for the code. I'll go through it. :D

Actually Today I tried wxSmith again to understand it. But could not post as there was some problem during posting. I've created the following page. Please have a look at it.



My idea is also similar of using macros. Already it's in use in one place. While you add the support to add extension to project file, I would start working with basic templates of wxSmith and as well as wxFormBuilder. :)

Regards,

Biplab

Navigation

[0] Message Index

[#] Next page

[*] Previous page