Developer forums (C::B DEVELOPMENT STRICTLY!) > Plugins development
RAD TOOL developers wanted
upCASE:
Hi!
--- Quote from: mandrav ---
I think it would be better to make it a custom editor, registered for XRC files (for example). I haven't looked at your code, but to implement a custom editor in C::B, you just inherit from EditorBase (which inherits from wxMDIChildFrame and when we ditch MDI it will inherit from wxPanel). Unless you are doing magic stuff in your initialization code, I believe it should be pretty easy to embed you editor in C::B :D
--- End quote ---
I'm not quite sure I got that, maybe due to my fair knowledge of how C::B was implemented and how the SDK works. Currently the editor is a MDI Frame, too. So you mean I should implement it so that it gets "embedded" into C::B on start? Like adding a toolbar, menu etc. to the main editor?I just played with the plugin generator plugin and saw that it has options for that currently disabled.
--- Quote from: mandrav ---
We can add the code in CVS and you can work from there. This way more people might want to join you :D
And don't forget the motto of open source: release-early, release-often ;)
.
--- End quote ---
Good idea. I'll straighten things out in the code to get loading and saving to work properly and maybe add some more widgets. Then I'll be happy to upload. In some parts the code is a real mess :D Extreme programming, here I come :D Maybe I should comment the code in some places, although I doubt that it will be easy to understand. The handling for events when adding widgets (especially into sizers) is pretty complicated and I still have to clear the massive object dump I get at the moment :D
mandrav:
--- Quote ---I'm not quite sure I got that, maybe due to my fair knowledge of how C::B was implemented and how the SDK works. Currently the editor is a MDI Frame, too. So you mean I should implement it so that it gets "embedded" into C::B on start? Like adding a toolbar, menu etc. to the main editor?I just played with the plugin generator plugin and saw that it has options for that currently disabled.
--- End quote ---
Take a look at this thread. It was the first attempt at creating a custom "editor". It also contains a link to a test plugin I hacked up quickly to test it. Download it and take a look.
To really embed your editor, it can't be an MDI frame. It must be an EditorBase (which is a wxMDIChildFrame for now). Also, until we add a docking library in C::B, your tool windows should have the wxFLOAT_ON_PARENT style flag.
Anyway, I think you should download the test plugin mentioned above and see for yourself. If you don't get it yet, or you think that it's too much of a hassle, you can initially set your application as a registered XRC MIME handler and have C::B launch it (optionally modal) as an external application.
Or you can go on asking me (publicly or in private) anything you don't understand yet ;)
Yiannis.
rickg22:
--- Quote from: upCASE ---Maybe I should comment the code in some places, although I doubt that it will be easy to understand.
--- End quote ---
Why not grab Windows Paint (TM) and make a nifty diagram of how the classes work?
--- Quote from: Mandrav ---To really embed your editor, it can't be an MDI frame. It must be an EditorBase (which is a wxMDIChildFrame for now). Also, until we add a docking library in C::B, your tool windows should have the wxFLOAT_ON_PARENT style flag.
--- End quote ---
And you may also want to take a look at the codecompletion plugin to see how it allocates a tab in the left pane (for the property editor).
upCASE:
Hi!
--- Quote from: rickg22 ---
--- Quote from: upCASE ---Maybe I should comment the code in some places, although I doubt that it will be easy to understand.
--- End quote ---
Why not grab Windows Paint (TM) and make a nifty diagram of how the classes work?
--- Quote from: Mandrav ---To really embed your editor, it can't be an MDI frame. It must be an EditorBase (which is a wxMDIChildFrame for now). Also, until we add a docking library in C::B, your tool windows should have the wxFLOAT_ON_PARENT style flag.
--- End quote ---
And you may also want to take a look at the codecompletion plugin to see how it allocates a tab in the left pane (for the property editor).
--- End quote ---
1. Once the time comes, I let doxgen do the job :D
2. Good idea, I'll check it out.
As I won't be online until Tuesday (since in germany monday is a holiday and my wife and son won't approve I spend the time coding :D), I htought I give you a little yummy for the weekend and upload my development beta release as a binary to try out.
Get it here: http://www.upcase.de/stuff/wxResEdit.zip
Please comment on bugs and improvements. Saving and loading works to some extend, XRC code generation seems to be fine. Note that only some widgets are implemented and editing a project after loading it will lead to crashes when trying to add new stuff to sizers.
Have a nice weekend!
takeshimiya:
As I've wrote on another post:
=)
A RAD for wxWidgets inside CodeBlocks
One of the best wxWidgets RADs right now (IMHO) is DialogBlocks, so I think that we have 2 great options
-Ask Julian Smart about making a plugin of DialogBlocks for CodeBlocks, or better yet, convince Julian to distribute by default the combo of CodeBlocks+DialogBlocks plugin (the best combo for replacing VC+MFC).
-Ask Julian to donate most of the DialogBlocks code.
He already has done that for another IDE (CodeDragon - wxStudio), but that project isn't maintained anymore.
http://www.anthemion.co.uk/dialogblocks/
http://wxstudio.sourceforge.net/
Anyways the first step and most easy would be to ask Julian to make DialogBlocks generate CodeBlocks projects (currently DialogBlocks generates Visual C projects, makefiles, etc a very handy feature)
Note that I encourage to do a RAD from scratch, but I'm afraid that it never gets finished nor maintained anymore.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version