[haiku-commits] Aw: Re: haiku: hrev47086 - in src: kits/media servers/media
- From: "Stephan Assmus" <superstippi@xxxxxx>
- To: haiku-commits@xxxxxxxxxxxxx
- Date: Wed, 2 Apr 2014 11:02:51 +0200
Hi,
> Gesendet: Mittwoch, 02. April 2014 um 10:42 Uhr
> Von: "Axel Dörfler" <axeld@xxxxxxxxxxxxxxxx>
> An: haiku-commits@xxxxxxxxxxxxx
> Betreff: [haiku-commits] Re: haiku: hrev47086 - in src: kits/media
> servers/media
>
> > 2feaa37: Move media plug-in support to application side.
> > Now, the format handling is done by each application. The node
> > monitoring is removed, instead the apps will scan the plugin directory
> > when first using the media kit classes. Restarting the application is
> > needed to update the media formats list.
>
> While my answer to your question to the mailing list may come have a bit
> late, I
> feel your solution is inferior to what was there before.
> Having to restart applications for add-on changes is something we tried to
> avoid
> everywhere, and so far managed to do AFAICT.
> If the add-on has already been loaded by the application, it will continue to
> work, anyway.
> That the previous implementation was not ideal, does not mean it's okay to
> replace it with something even worse.
>
> Generally, when asking for input on a mailing list, you should have more
> patience :-)
While it seemed a bit hasty to go through with the implementation so soon after
asking for input, I must say that I didn't particularily liked your suggestion.
The assumption that add-ons are always installed for both architectures, with
the same name, is just an assumption. I find Adriens solution just fine. And as
he pointed out, apps did not really benefit from live-updates to the available
formats. Aside from MediaConverter, all apps I have ever contributed build the
UI for choosing plugins only once.
Best regards,
-Stephan
Other related posts:
