Developer forums (C::B DEVELOPMENT STRICTLY!) > Plugins development
RAD TOOL developers wanted
upCASE:
Hi!
Ok, so here it comes: The new updated development release/snapshot of my GUI editor.
First a new screenshot:
You can download a copy of this beast at http://www.upcase.de/stuff/wxRapid.zip
- I implemented most of the widgets in a basic form (meaning: some og them don't work as expected).
- wxPropertyGrid has been updated to a development release after a short mailing with its creator Jakko.
- XRC code generation works almost perfectly.
- For the XRC code, a cpp/h file will be generated that loads the XRC and gives you control over the used variables.
- Basic support for event handlers has been implemented. I used a hacked version of wxLongStringProperty for that, displaying a STC editor. wx classes should be colorized.
- Event handling code will be generated in the cpp/h files, but don't expect too much :D
I hope you find this a good thing. Still, a lot is missing. There will be Menu bar editing and Status bar creation (it's there in a basic form) in the next release, maybe tool bar support too. Some problems with not existing widgets (like wxCalendarCtrl) for XRC will have to be reviewed. Aynway, I think it's getting better and better. Hopefully there will be something that really works in the near future.
Oh yes: There will be "pure" C++ code generation.
Cross your fingers that I find the time for these changes :D
rickg22:
OK I think diversity is good. Evolution in action! :D Survival of the fittest *evil grin*.
And I'm sure that someone'll be able to integrate upCase's wxRapid with C::B. But you know, I think we should post a thread on each plugin under the development forum. And then each author would explain *in his own words* how his plugin works.
This way we could do a brainstorm and perhaps merge the important parts of each plugin.
mean, there are COMMON things in the plugins. Like the properties pane, the object tree (above the properties), the widgets palette, and of course, the GUI area. So if each one says how each one is implemented, maybe someone out there can take the best out of each and paste the code like crazy :P.
So feel free to create your "my RAD Editor" threads. I'm 100% sure that many good things will come out of it.
Anonymous:
I' m up for joining byo on wxSmith with two requests:
1. A proper plan of attack--er, some kind of informal or formal documentation--is draw up and modified as needed to manage this very important project. Something like an action list of development items subdivided as needed. Or something else.
2. Since this is apparently the first and only RAD plugin, all other standalone candidates are reviewed for partial inclusion to minimize reinventing the wheel, as it were. Perhaps all involved can make their case for their own priorities. This doesn't mean each would be involved, but any code could be contributed and reviewed.
My reasoning for this is that, while others have stated the obviousness in diversity, it occurs to me that "united we stand, divided we fall". I would hate to see all this fabulous energy wasted. I've also seen other project deteriorate due to lack of perseverance--note the other attemps at public domain RAD tools that have wasted away. So let's capture this energy in a unified effort while we still can.
I expect (1) will take some time (month or two) and (2) will impact (1) and may depend on the cooperation of others.
DreadNot:
Sorry :oops:. Wasn't logged in. The above was mine.
DreadNot
rickg22:
Yes, I forgot to mention :P While diversity is a good thing in evolution, so is DNA recombination.
Anyway, I just tested byo's plugin, and I think we can work from there: Improve the interface, etc. However, without a manual (or blueprint) it'd be hard to improve specific parts. What *particularly* worries me is the object construction handling of events. Byo's approach is to make a derived class out of each widget. While it does work, i'm sure there's an alternative approach, like trapping the events so they won't get to the widgets or something. I think I read something in the wxWidgets manual about disabling events for GUI designers (and that's what we're doing, right?)
upCase, how did you implement this part?
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version