No offence to anyone, but I think the RAD idea needs some sort of management. Put someone in charge of RAD for Code::Blocks. I know having more than one RAD provides diversity and options, but it also wastes too much time on re-inventing the wheel.
In this case, 3 people are doing essentially the same thing! All are re-inventing the same wheel!
Why not organise everyone into diverting their energies working on the same wheel?
Getting all the developers together produces far better results than three separate solutions which are semi-complete with half-hearted to no decent documentation.
We use upCASE's code as the basis. We discuss what we want in Ver 1.0 of RAD for Code::Blocks. We set goals for each version, etc. This is where all developers wanting to get involved has their say at what they want to add. The person in charge of RAD makes sure everyone agrees to the features they want to add.
We start off with, a version that is labelled EXP (eg : Ver 1.0-EXP) for experimental. This is where developers throw in their contribution, add a new feature, etc. This is not guaranteed to work 100% stability.
After all the features (goals) have been achieved, we freeze development and test.
=> Ver 1.0-ALPHA-1, Ver 1.0-ALPHA-2, etc.
We fine-tune and tweak for max stability and performance.
=> Ver 1.0-BETA-1, Ver 1.0-BETA-2, etc.
=> We also take the time to document the new features and tutorials, etc.
Once its solid as a rock, it will be released
=> Ver 1.0-STABLE.
=> With full documentation.
=> This is the complete and polished one.
Yes I know, this approach requires more effort. BUT:
(a) All developers will have a strong purpose and their energies are focused on the goals. (So they don't feel so overwhelmed and have more time to spend on family, etc).
(b) Developers won't be doing redundant things. (I find it ridiculous if 20 people are doing the same thing!)
(c) The result is a FAR more polished RAD than anything (open-source wise) out there.
(d) The community will recognise it (Code::Blocks and RAD) without the need to advertise. If you're good at something, you don't need to say a thing. Your creation and skills says everything for you....And if you know your software is crap, you could do what MS does and start ridiculous FUD campaigns like "Get the Facts".
(e) The overall IDE with RAD will be a far more polished solution, which could rival some commercial solutions. Everyone loves rock stable software.
(f) If you attract attention of companies supporting open-source, you get quite a number of new features from them. (It could be something that no one else has thought about, but they like to add to your code). Who knows, you may even get monetary support from organisations and folks who love using your tools.
You may have wondered why I'm suggesting all this. Well, its that I'm sick of most open-source solutions doing things without properly defined goals and management. ie : Its all over the place. Bugs remain open, documentation and help files is incomplete, etc, etc. A simple thing like a checklist really does go a long way!
Everyone is wanting to do their own thing and the result is a software that isn't good as it should be. That pisses me off. Half-baked solutions written by programmers in their spare time. (Bill Gates is laughing, as all this software isn't a threat to his profits).
What's worse is they lack the proper documentation. Every newbie would like to contribute and use open-source software...But if there is no documentation with tutorials and such included with software, folks get a little fustrated and use something else.
Take wxWidgets as the prime example. There is no proper tutorials to get newbies started and understanding of the tools...Sure, a book is coming to address this issue...Why didn't they have some documentation like a electronic handbook in the first place? There wouldn't need to be visiting Amazon.com to buy a stinking book just to get a clear grasp of wxWidgets. (You saved a few thousand trees as well).
I'm saying all this because I see Code::Blocks have alot of potential. This potential could be ruined if everyone does their own thing.
mandrav has laid out the basis (Code::Blocks) for us to build on. All we have to do is organise ourselves into teams that are responsible for a particular plug-in. (Or a feature of that plug-in)...Say wxWidgets's network component, etc.