Re: GUI-Independence continued; some ideas...

2001-03-29 Thread John Levon
On Thu, 29 Mar 2001, Allan Rae wrote: > Still tripping down memory lane... > > Suggested/rejected GUII implementation number two. Both of the above > cases just end up being yet another restrictive cross-platform toolkit. > We don't need that. If you want one of those then just create a port to

Re: GUI-Independence continued; some ideas...

2001-03-29 Thread Allan Rae
On Thu, 29 Mar 2001, Andre Poenitz wrote: > > Suggested/rejected GUII implementation number two. Both of the above > > cases just end up being yet another restrictive cross-platform toolkit. > > We don't need that. If you want one of those then just create a port to > > the cross-platform toolki

Re: GUI-Independence continued; some ideas...

2001-03-29 Thread Andre Poenitz
> Suggested/rejected GUII implementation number two. Both of the above > cases just end up being yet another restrictive cross-platform toolkit. > We don't need that. If you want one of those then just create a port to > the cross-platform toolkit of your choice and use that. Oh, I did not sugge

Re: GUI-Independence continued; some ideas...

2001-03-29 Thread Allan Rae
Wow a trip down memory lane... On Thu, 29 Mar 2001, Andre Poenitz wrote: > > Kalle> What could be done would be something like this: > > > > #ifdef XFORMS > > typedef FL_OBJECT* WidgetPtr; > > #elif defined QT > > typedef QWidget* WidgetPtr; > > #endif > > This should get encapsul

Re: GUI-Independence continued; some ideas...

2001-03-29 Thread Kalle Dalheimer
On Thursday 29 March 2001 14:28, Edwin Leuven wrote: > It seems to me that having 5 implementations in one file separated by > #ifndef's is not a good idea. I'd rather see 5 different implementation > files. Not only will the code be cleaner, but I also like the idea of > having the xform code in

Re: GUI-Independence continued; some ideas...

2001-03-29 Thread Andre Poenitz
> Kalle> What could be done would be something like this: > > #ifdef XFORMS > typedef FL_OBJECT* WidgetPtr; > #elif defined QT > typedef QWidget* WidgetPtr; > #endif This should get encapsulated in a real class, say "Widget", with different implementaions for Qt, xforms, etc. > K

Re: GUI-Independence continued; some ideas...

2001-03-29 Thread Edwin Leuven
It seems to me that having 5 implementations in one file separated by #ifndef's is not a good idea. I'd rather see 5 different implementation files. Not only will the code be cleaner, but I also like the idea of having the xform code in the xform dir, the qt code in the qt dir, etc. Although n

GUI-Independence continued; some ideas...

2001-03-29 Thread Angus Leeming
Kalle Dalheimer and I have been having a discussion about possible ways forward with the GUI-I stuff. Thought you might be interested (and of course, I'll be able to find this on the archive in future!) Feel free to comment... A Angus> Incidentally, how do you find the new scheme? Angus> Any