RAD TOOL developers wanted

[Anonymous]

I agree to the poster abov me.... Truly diverisfication and freedom of choices are cool, but.... First of all, rather than having the freedom to choose between 3 half-backed RAD-Tools, I'd like to have 1 that really works and that really makes progress.

Still, something I'd also like to notice: while C::B surely needs a RAD-Tool, I think whatever is going to be the "the standard" wxWidgets RAD-Tool should not be bound to an IDE. Seen from this point of view it may not be bad that there's more than one RAD-Tool in the pipeline. So my plead would be

a) the dev's of the 3 RAD-Tools should please _WORK TOGHETHER_ to create ONE REALLY GOOD RAD-Tool instead of 3
b) whatever comes out of this work should also be able to function as standalone app


just my 0.02 $

[takeshimiya]

It would be cool to have the RAD working as a standalone app BUT, it would be very time consuming, because the RAD developer would be himself doing a lot of things that are already included in C::B.

As real life examples see:

-DialogBlocks: It is a standalone app, but as time has passed, Julian had to make it almost like an IDE to be more usable (it haves a code editor, generates MSVC projects, compile and debugs programs), so at the end is like having an IDE inside the RAD (instead of having a RAD inside the IDE ).

-MFC editor from MSVC: It doesn't come as a standalone app, for the same reason avobe.


So at first having the RAD as a standalone app appears to be ok, but as the time passes the RAD developer would be implementing all the things an IDE haves.


IMHO in the situation that makes sense to have a standalone RAD is in a XRC only resource editor.

[Urxae]

If a standalone RAD tool is wanted, maybe a stripped-down version of Code::Blocks could be created that only has the things that would be needed for RAD?
Since it's modular, it may not be too hard to do, removing all other plugins and maybe disable the text editors might go a long way. (Are the text editors necessary for writing event handlers? Not sure what a 'standalone RAD tool' is supposed to do and not do...)

This is basically what happened with Eclipse: It started out as an IDE in which almost everything was a plugin, and a year or so ago they released a rich client platform.

Something to think about...

[Lexx]

Hi!

I use DialogBlocks for wxWidgets and C++ applications.
http://www.anthemion.co.uk/dialogblocks

Lexx

[Anonymous]

Whould it be possible to use José Hurtado's own plug-in system and xml parsing code into wxSmith and ask them to join this team?

[heromyth]

Does anybody pay attention to  visualwx(http://visualwx.altervista.org/). However, it does not open source.

[rickg22]

I'd rather have an open source tool (I think we had talked about this already - look at what happened to Linux and bitkeeper - search in slashdot -). But thanks for the suggestion :-)

[baboo]

Hey,
What happened with the RAD tool... We are all waiting for a release to test it, to give some feedback at least.
Give me some info if there are any news, please.
Thanks a lot.

[takeshimiya]

My current solution: use DialogBlocks until wxSmith gets stable (I'm refering not that it's crashing, but stable on the API and code generation)

[byo]

Hey,
What happened with the RAD tool... We are all waiting for a release to test it, to give some feedback at least.
Give me some info if there are any news, please.
Thanks a lot.

RAD tool is included in Windows version of RC2 installer but not selected by default.

[byo]

My current solution: use DialogBlocks until wxSmith gets stable (I'm refering not that it's crashing, but stable on the API and code generation)

DialogBlocks seems to be good suggestion - I haven't working with it but it seems to be very usefull

[takeshimiya]

Yep, it's the current most well featured RAD for wxWidgets, it's similar to Code::Blocks (supports multiple compilers).
And it's developed by Julian itself, so that says something

The best about DialogBlocks is that it blends well the C++ code and the widgets, so every time you edit a widgets the changes get reflected in the code (or the XRC)

It automatically inserts code (or XRC handling) between ////@begin and ////@end like:

Code Select Expand

////@begin WxCoolBarSampleApp initialisation
    // Remove the comment markers above and below this block
    // to make permanent changes to the code.

#if wxUSE_GIF
    wxImage::AddHandler( new wxGIFHandler );
#endif
    wxCoolBarSampleFrame* mainWindow = new wxCoolBarSampleFrame( NULL, ID_FRAME );
    mainWindow->Show(true);
////@end WxCoolBarSampleApp initialisation

And you can insert validators and variables to each widget in your dialogs.

Fortunately wxSmith is catching up very fast!

[baboo]

"RAD tool is included in Windows version of RC2 installer but not selected by default."
....
Man... RAD tool is included on Windows version and not on linux version? ... hmmm  :? :cry:
Why?

[byo]

"RAD tool is included in Windows version of RC2 installer but not selected by default."
....
Man... RAD tool is included on Windows version and not on linux version? ... hmmm  :? :cry:
Why?

There is source code but must be manually compiled in C::B (wxSmith is not yet included into automake build ) and some files need to be copied into wxSmith's data directory . There's post about this somewhere . I have some difficulties with current CVS version, but RC2 should work fine

[mandrav]

(wxSmith is not yet included into automake build )

This is because you 're adding/removing files all the time
Seriously, I can (and probably will) add it in the build system but are you willing to add/remove files to/from the build when you change the project? I.e. you will have to keep it in sync with the project files...