I'd like to enable multiple guis build too. I'd name them gtk-gnash, sdl-gnash, fb-gnash etc. etc. The rationale is that sometime you really want two or more versions. For example, a framebuffer AND a gtk based gnashes. Also, we know that gtk better integrates into the firefox browser, so it is good if each plugin can call the better integrated gui... We might have a 'gnash' shell script that takes a --gui argument and fails if that gui is not available, and have some smart default like starting the fb gui if not in an X context etc..
--strk; On Mon, Oct 16, 2006 at 02:46:02PM +0200, Bastiaan Jacques wrote: > Hello, > > In my most recent commit, I enforced the use of --enable-gui=KDE > when --enable-klash is specified in the arguments to configure. For > those of you who don't know, Klash works much like the Mozilla plugin; > it spawns a new klash process which embeds into a Konqueror window. > > The change was needed because we currently only allow for one GUI to be > build at a time and unfortunately Klash does not play nicely with a GTK > GUI. > > The main problem with this change is that it is no longer possible for > people to install klash _and_ a GTK based gnash (with an optional > mozilla plugin). > > My question is: should we adjust the build system to allow for multiple > GUIs to be built? In effect, this means we would have seperate binaries > like Gnash (GTK), Klash (KDE), Slash (SDL), Flash (FLTK), et cetera. > > My gut feeling tells me that it's probably not worth the effort, but if > people think this would be useful, I'll consider doing it. > > Bastiaan > > > _______________________________________________ > Gnash-dev mailing list > [email protected] > http://lists.gnu.org/mailman/listinfo/gnash-dev -- /"\ ASCII Ribbon Campaign \ / Respect for low technology. X Keep e-mail messages readable by any computer system. / \ Keep it ASCII. _______________________________________________ Gnash-dev mailing list [email protected] http://lists.gnu.org/mailman/listinfo/gnash-dev
