[Wxdevide-devs] wxDevIDE

[Nuklear Z. <nuk...@gm...>]

last time we used this list i think we had all gone different ways, id like
to know if any work has been done on this project by anyone since then. I am
going to get back on it, but it will be somewhat slow probably, just don't
want to duplicate effort.

i plan on looking for a gtk solution to resizable control unless one has
been found
building a shell for the editor module
probably forking the codebase to strip out the delphi-ish code for a cleaner
start point on the gui and possibly look at AUI-ing the main form
i might draft a project file and workspace file format. also i think aside
from compiler profiles the project needs build targets, an annoying lack in
dev.
also a current project file needs a way to add a compiler profile, i don't
know if that's done in wxdev but it crossed my mind.

i guess that might be base for a file release for version .001 unless we
have a different versioning method in mind. possibly the same as dev then
0.0.0.1 ? or 0.0.0.1A (for alpha)
i think the second release might have a semi-working project file parser
that would load the project files from the tree ctrl when clicked on. the
editor options dialog should just be built from scratch within the module,
(my template idea was not working and kinda unintuitive) but the dialog and
editor should not interact. the configuration module should be all that is
needed. also a global config module based on wxconfig is a good idea imo, i
remember talking about a separated one but been to long to remember details.

ill update the editor module docs once i have a decent bit of code figured
out. project file docs ill do before writing code since it will be easier
with wxdev and code::blocks to look at. i think all config, wxform, project,
workspace, whatever should be xml. i think we decided on that anyway. we can
use the wxXMLconfig class on wxforum until its added to wxWidgets unless
they already did i haven't looked. i did check that it works fine. also
other xml can be done in wxXML i think they have that class stable now.
(wasn't in 2.6, i think it is in 2.8)

and for the form designer i have an idea on spacers, instead of a spacer
panel, since we are going for wysiwyg it should be nonvisual somehow. im
thinking if the ide gui bits needed for the form designer are far enough
along creating the designer will be easier. also for a start point on using
a compiler down the line maybe code::blocks code can be used until we can
write the appropriate makefile generators and stuff. possibly the debugger
too, but that is a good ways off yet. also maybe a small delphi program can
be used to convert the delphi wxform icons/images to image files/xpm
probably by default. then placed in the images directory for use. the wxform
format for the c++ designer is probably better off not being based on xrc
format. its kinda limited and we don't have enough flexability to do
everything we need. since designer code mangling is xml based we could
hypothetically support win32 or gtk but they wouldnt be wysiwyg obviously.
also a gui widget can be several classes in code since the widget doesn't
export code the xml does, so we just need a way to identify the gui widget
in the xml to allow for different class code, also gui plugins would make
sense.

im leaving out the plugin stuff since i dont know how to do it. obviously
the gui part is not as big an issue since its basically injecting into the
gui but the other bits are out of my league. if the main form is written
correctly adding the plugin parts wont be too tough and it gives some place
to start drafting the interface.

ill take a look at trac and put up some notes maybe. that covers what ive
been thinking about lately. i still need to put a machine together since my
last box fried and i gave away the monitor. a bit short sighted i suppose
but ill live.

Nuklear Zelph