Re: [Wxdevide-devs] Designer Development

[<Nuk...@gm...>]

I have not done or thought anything about it in a while. I did realize that  
we could use wxObject and IsOfClass() as a designer tree base of some kind.  
I think storing images in a folder and using the name in place of ascii  
code is a better approach unless we just save everything as an xpm. that  
however lacks some features like alpha blending. That is all i really  
figured out so far. i pretty much have given up on software development so  
i wont be too useful.

Nuklear

On Jan 29, 2011 8:52am, M Nealon <mal...@gm...> wrote:
> Hi All (Tony?),

> I am currently investigating the designer for wxDevIDE.


> One point that I am unsure about is in fact the importing of wxform  
> information into the designer (getting ahead of myself here I know). One  
> of the problems is the icons for the menu (possibly anything with  
> images). The information is saved in the wxform file as a series of ascii  
> strings. What someone needs to do (looking at everyone else here) is to  
> investigate some sort of export function which will export the wxform  
> information into a format which we can then use for the new wxidefrm form.



> What I suggest is that we create our own wxform format (which I have  
> chosen to call wxidefrm which is a reasonably faithful representation of  
> the current wxform format but with images contained within in some  
> standard easily used/identified format.



> I have to do a lot of investigation wrt the designer, but I might be able  
> to make a start in getting something into an IDE.


> What I intend to do as a first step is to make a start on the SDK for our  
> plugins (of which the designer is just one) as I develop the designer,  
> unless anyone has any ideas as to the SDK for the plugins (hopefully with  
> sample code - then PLEASE provide them).



> However, I do get the impression that we have all left the project and  
> are just letting it die, is this so?


> What I/we could do is develop the designer as a plugin for CodeLite  
> and/or Code::Blocks until we get our own IDE up and running, but if there  
> is no interest in developing wxDevIDE then I don't think that there is  
> much point to investigate implementing some sort of plugin architecture,  
> and I should just concentrate on developing the designer for some other  
> IDE (CodeLite and/or Code::Blocks) that already has a plugin architecture  
> in place.



> I suppose what I am really asking is "is wxDevIDE dead?", and if so what  
> do we as a group (if we are still a group) or I as an individual do now?


> regards
> Mal