VB Classic (A True VB 7.0)

[Schmidt]

@SuperDre & Olaf

Maybe a new thread should be started to discuss the complaints about the old IDE and what features we would all like in the new IDE?

I'd find that not necessary at the moment - in my initial GIT-Repo-Opener-Step (just give me a few more weeks, to bundle something up),
I will upload a wireframed and widgetbased-Version, which in its "Panel-Areas" tries to mimic the current VB6-MDI-version (most of the PanelAreas still empty,
only filled with mockups or stubs). Also the Menu-Stripes and ToolBar-Stripes I will only provide with the first entries - and the modal-dialogues
I will replace with a generic "Todo-MessageBox".

From that Wireframe it should be easier then, to "spread the work-load" without causing team-efforts to overlap.

I'd like it when we could use *this* Forum here for the rough overview, where the project currently is, reflecting the current
state in a kind of "still open, ...already worked on by PersonX, ...already finished"-List where developers can "check themselves in"
for a certain Todo-task, to fill the "still blank spots" in the wireframe-model - and make it clear for others, who's currently working on what -
which are the Todo-Tasks which are still "open" - and what tasks are already done ...

Maybe *that* should then go into a new, separate Todo-Thread, where the initial post is used to reflect the current state.

Basically I'd like to treat the GUI in the same way as the initial requirement for *.bas and *.cls compatibility - let's discuss enhanced features
(much) later - first let's try to come up with something which resembles the original as closely as possible - only if there are
"cheap and obvious enhancements possible already in the first throw"- then of course let's apply them - but those topics will
then come up along the way in the GIT-repo-Pull-Requests - and we could discuss implementation-details there then.

Edit: Forgot to comment on the SDI-capabilities of the old VB6-IDE - and how to achieve that in the VB7-IDE...

This feature would (if there's enough contributors who'd be willing to approach this) not that difficult to implement,
since in the new Form-engine (which offers the hosting-areas for the new Widget-Framework) there's no difference between
"Client-Panels" or "TopLevel-Forms" - both are of type cWidgetForm.

So, Code (and Widgets) on a certain Panel (interacting with such a cWidgetForm-Base), which in the first throw will be implemented as Docking-Areas -
can later on easily be hosted also in a TopLevel-cWidgetForm-instance (ToolWindows etc.), by just switching the instantiation-line of the cWidgetForm-variable -
so SDI-mode will not be a real problem if that is wanted - but it can be achieved later on, without "wreaking havoc" in the original CodeBase - and so I'd like to
delay this step until we came clear with the MDI-version initially (which I think is the mode, the VB6-IDE is currently used by most Devs).


Olaf