On Sat, 11 Mar 2000, Angus Leeming wrote:
> Ok, read and digested your recent postings. Also had a play
> with fdesign/read the documentation. Also downloaded and
> installed doc++, so that we can document this stuff.
>
> Allan > I don't want to have to repeat all the work I did
> Allan > last time however. If Angus and John want to do it
> Allan > all again from scratch that's fine by me and I'll
> Allan > help you everyway I can: co-ordination of who's
> Allan > doing what via a web page at devel.lyx.org for
> Allan > example, maintaining a `dialogs' branch for you to
> Allan > work against and committing your work for you,
> Allan > words of wisdom from my experience doing it all
> Allan > last time.
>
> Fair enough. How about this for a sensible roadmap:
>
> 1. You finish your script and port all the stuff in the old
> lys-devel branch over to SigC++. (Incidentally, I DO use
> this branch, so "stop haranguing me about it"!)
>
> 2. We/I port anything left over to SigC++. Ie remove all GUI
> stuff from src/ so that all communication is through
> Dialogs.h
Pretty much what I was thinking.
> 3. We start up a GUI design discussion of "The best way
> forward". Ie, we thrash out a clean structure of base and
> derived GUI classes.
Shouldn't be too difficult to recognize patterns as the dialogs are moved
across. Cleaning up the converted dialogs into a better structure can be
overlapped with the porting of old dialog code.
> 4. I (+anyone else!) implement this for xforms, keeping the
> design discussion going of course.
>
> 5. Implement other GUIs. Once a structure has been
> established/implemented, this should be clean and
> straightforward.
Note that programs like KDevelop tend to build a lot of this stuff for
their appropriate desktop so xforms can be our refernce implementation but
the others needed follow the same structure. All they have to do is use
Dialogs and DialogBase.
> This roadmap has the enourmous advantage that everything
> will continue to work at all times.
That's the plan.
Allan. (ARRae)
