[vlc-devel] Gui for Mozilla's plugins
a.millet89 at gmail.com
Tue Sep 22 17:03:07 CEST 2009
Amongst the five suggested answers to the gui problem, three didn't seem to
receive a great support from the community.
Still remain the following choices :
- Using XUL and related technos: a solution with pros and cons.
- Using Native APIs to implements very simple widgets, which will be harder
to maintain, but has a broader scope.
Which way do you thinks we must follow ?
2009/9/21 Pierre d'Herbemont <pdherbemont at gmail.com>
> I might be very mistaken here, but I thought there was a way to access and
> write to the page DOM via NP APIs. If this is true this is the way to go for
> in page. However, fullscreen controls seems to be much more problematic.
> Platform specific code is required here.
> On Sep 21, 2009, at 2:17 PM, Rafaël Carré <rafael.carre at gmail.com> wrote:
> On Mon, 21 Sep 2009 14:04:36 +0200
>> Alexandre Millet <a.millet89 at gmail.com> wrote:
>>> We are a group of two students working in computers sciences in Paris.
>>> As some of you may already know, during our first year's internships
>>> we choosed to work on VLC and enhance the Mozilla plugin's GUI.
>>> We would like to add a control GUI to the plugin (play, pause, seek,
>>> ...) and we are searching what is the best way to achieve it.
>>> This is an overview of the advantages and disadvantages of each
>>> - Qt, is very simple to use, extremely portable but the weight of the
>>> dependencies may be high, QtGui + QtCore exceed 10mb.
>>> - GTK+ is slighter than Qt but it is not built with portability in
>>> mind (especially on Windows).
>> i don't like those for the reasons you mentioned
>> - The GUI can also be made in XUL, the downside in that it won't work
>>> on other browsers that support the NSPlugin API (opera, webkit, ...).
>> that's a bit sad but it doesn't bother me much
>> - The fourth solution would be to integrate the GUI into the VLC core
>>> and inject the user interface directly into the VLC vout.
>> i very dislike this idea
>> - The last solution would be to use native code. This implies that the
>>> GUI must be developped one time for each platform and is a pain to
>> this looks interesting
>> I imagine the GUI would be quite simple (buttons, progress bar, slider,
>> labels) and there could be a way to factorize toolkit-specific code.
>> Now another question is which toolkit to use on UNIX?
>> Rafaël Carré
>> vlc-devel mailing list
>> To unsubscribe or modify your subscription options:
> vlc-devel mailing list
> To unsubscribe or modify your subscription options:
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the vlc-devel