>What king of gui functions are we talking about here? Are we talking about
>buttons like "Disable sound" or "toggle fullscreen", "enable ne2k
>emulation" etc? If so, how will this gui communicate with the various
>plugins? Will we have (or do we have) some global or per vm structure to
>contain these settings and some common mechanism for querying & updating
>it from the plugins?
>If a widget set based on SDL is used for this GUI, will it be part of the
>same plugin that does, say, the vga & vesa emulation? That would not be
>nice for anyone who wanted to replace the vesa plugin with something else
>(eg matrox emulation) but retain the gui functions without duplcating
>code. If it were a seperate plugin though, how would it communicate with
>the other plugins which also use SDL?
I assume, there will be a lot of different GUIs. At least the people of KDE
and Gnome will be eager to develop a Plex-GUI that fits in their environment.
Therefore, I think it's better to keep things modularized and not bind
functions directly to special widgets.
I'm not very used to C/C++ and especially I'm completely lost in the deep
discussions here, but I would like to give a KDE client a try.
I don't see the different clients as part of the main source, they can still
exists in different CVSs. But it should be easy to choose the library of
choice when someone creates a client.
Philipp
PS: Keep on doing this great work. I'm such impatient in waiting for the
Plex86 ;-)
--
Sent through GMX FreeMail - http://www.gmx.net
