Developer forums (C::B DEVELOPMENT STRICTLY!) > Plugins development

RAD TOOL developers wanted

<< < (16/19) > >>

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?

Navigation

[0] Message Index

[#] Next page

[*] Previous page