[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Gnash-dev] multiple GUIs

From: Martin Guy
Subject: Re: [Gnash-dev] multiple GUIs
Date: Thu, 19 Oct 2006 14:37:04 +0100

Agreed, --gui=<gui> --renderer=<renderer> --sound-handler=<sound>

remember --mp3decoder=<mad,ffmpeg> too.
I thought --sound-handler was a configure option, not a gnash option.
For gnash --audio={gst|sdl|none} might be better or --sound or
something similarly snappy as an option to override runtime
autodetection. Then there are arts, esd, alsa, oss... :(

> MG>   Maybe it is too late to kill off the name "klash" but mapping it
I don't think it's too late to kill klash, why do you think its late ?
Mostly because the name is already public and in use. Example, there
is already a klash debian package separate from gnash, and there seems
to be a redhat package too.

%package klash
Summary:   Konqueror flash movie player plugin
Requires:  %{name} = %{version}-%{release}
Group:     Applications/Multimedia

%description klash
The gnash flash movie player plugin for Konqueror.

  Not that that's a problem - we can always tell them to make klash
depend on gnash and turn klash into a one-line shell script.
  Having a specific klash binary is a technical advantage to KDE
users if a significant code size reduction is obtained by removing the
alternatives that KDE never uses. If not much in the player itself,
certainly it is an advantage for it not to pull in the sdl and gtk
libraries and everything that they depend on, even if only at
package-installation time.
 The same argument could be made for the mozilla plugin as opposed to
the generic player. More names required?


reply via email to

[Prev in Thread] Current Thread [Next in Thread]