On Wed, 5 Jul 2000, Bryan Patrick Coleman wrote:
> Can libXMI just be used instead [of XMI-like functions in LibGWT]? Then
> I can get ahead sooner since much of the fbdev port of gdk is on top of
> XMI.
Not really. However, gwtmi* functions are just pure wrapper for mi*
functions. They have the same arguments, it's just the first one that
changes: it's a gwt_window_t instead of a ggi_visual_t.
(Rq: The "wrapper" does some clipping and iteration over the various
rectangles composing the window visible region - and call the usual mi*
function.)
In the end, I'd like to remove this wrapping layer - but for this I need
to hack the visual method set and... well... I guess this may be
error-prone. So I'd like to do that when the feature-set of LibGWT is
fully stabilized (it nearly did... but then LibXMI came... ;-).
> > - there is currently nothing dealing with any sort of "window
> >manager" inside LibGWT.
>
> Does OpenAmulet do this internaly? I remember you talking about OpenAmulet
> before but decided to work with GTK+ since it is C based.
GTK+ also has a much wider user base! Your work might prove much more
useful. (OpenAmulet is more of an experiment.)
OpenAmulet can manage sub-windows on X11 and MS/Windows so, it has some
internal provision for built-in decoration and management of windows.
It is seldom useful on conventional platforms, but it proved useful for
this port to GGI (not very beautiful however).
> Perhaps we could lay out a plan of attack here. It always good to plan
> before leaping into the cravass!
Don't worry... I have enough plans to keep you busy until 2010... :-))
> Will do! I want to have all the flexability that exists under X on the
> console as well if not more :)
GGI is much more flexible than X... ;-)
Rodolphe
