Re: [Wxdevide-devs] Whats up?

[Malcolm N. <m.n...@wa...>]

Tony Reina wrote:
> We released RC4 a few days ago. It has AUI support which Mal added 
> since we'll likely being using it for the wxDevIDE GUI. You may want 
> to get RC4 if you're going to work with AUI.
>
> I don't think anyone has done more on the API docs. Feel free to give 
> it a try if you like. Esteban is on vacation. I think that by the 
> beginning of Feb we'll have a full wxDev-C++ 7.0 release.  After that 
> everyone will be moved to working on wxDevIDE 1.0.
>
> -Tony


I am also working on extending wxAui as we currently support it. I am 
adding control bars, which don't really exist in wxW, but are useful 
when designing multiple toolbars. I am also implementing wxAuiToolbar's 
to work with the control bars.

Basically the idea is that the user can add up to 4 bars, and should 
place them at the 4 edges of the frame/dialog. (of course if he only 
needs toolbars at the top, as wxDevIde does then he only needs to add 
one). He drops wxAuiToolbars into these control bars, then populates 
them as he desires, and finally adds a wxAuiPaneInfo component and sets 
the ToolBar flag. The intention is that the layout in the designer will 
be replicated in the final program, but I don't see this as a fixed 
requirement for this release. wxToolbars remain functioning as they 
currently do (being parented to the frame and expanding to the full 
width of the frame).

I also wanted to add support for adding wxAuiPaneInfo components to 
things such as tree/edit/list/grid controls but the current 
implementation of wxDevC++ is preventing this (which will need to be 
adressed when we design for wxDevIde).

Curently the simplest way to get things such as tree/edit/list/grid 
controls being controlled by wxAui is to drop a panel, a wxAuiPaneInfo, 
then a sizer and the required component. It functions quite well.

I have done some work on making the wxDevIde dialogs/frames sizer based 
instead of the fixed position used previously (a residue from the delphi 
design), and will return to this as soon as I get this current addition 
to wxAui support in wxDevC++ implemented. (I also am going to move my 
wxForms based project over to wxDevC++/wxDevIde (assuming we will still 
be able to read the .wxform from wxDevC++ in wxDevIde).

I am also pleased to see that the wxDevs are looking at implementing a 
wxButton with image support, which solves a problem I foresaw with using 
the wxCustomButton from the designer (accelerator support).

So all in all I have been/am pretty busy wrt wxDevC++ and wxDevIde (can 
we shorten that to wxDI ??)

Great to see Kinming back, and on both projects.

Best wishes to all and a Happy New Year all round.

Mal