Menu
▾
▴
[gstreamer-bugs] [Bug 350477] [Registry] Provide a way for plugins to delegate the 'changes' behaviour
|
From: GStreamer (bugzilla.gnome.org) <bug...@bu...> - 2006-08-13 12:08:20
|
Do not reply to this via email (we are currently unable to handle email responses and they get discarded). You can add comments to this bug at http://bugzilla.gnome.org/show_bug.cgi?id=3D350477 GStreamer | gstreamer (core) | Ver: HEAD CVS Jan Schmidt changed: What |Removed |Added -------------------------------------------------------------------------= --- CC| |th...@ma...= m ------- Comment #5 from Jan Schmidt 2006-08-13 12:08 UTC ------- <ensonic> bilboed, I think the extra extensions will also have an extra p= ath, when the registry comes across a new gst-plugin (that registers custom path/ext) it needs to scan anyway <ensonic> bilboed, the custom paths need only be scanned with the custom extension registered for it <bilboed> ensonic, yeah, was thinking about it again ... and there's no w= ay to avoid having to scan the directories seperately/again <ensonic> bilboed, i don'T see the 'again' <bilboed> ensonic, if an existing plugin modifies a registered path for e= x <natyaht> bilboed: the whole point of registering a plugin path should be= to mark the plugin that 'owns' that path as dirty <bilboed> ensonic, or scanning an existing path with modified extensions <bilboed> natyaht, the combination of extension and path, yes <natyaht> yes, but that should just trigger the plugin being loaded in or= der to register all its elements <bilboed> natyaht, of course <natyaht> so, if a plugin is registering a new path... <natyaht> that implies it has just been loaded <natyaht> which implies it has just registered all the elements it knows = about <bilboed> natyaht, aaah, true <natyaht> which means you don't need to go back and scan the directories <ensonic> ... and then the registration info is corect anyway <natyaht> so, I think these things should be a new type of plugin feature --=20 Configure bugmail: http://bugzilla.gnome.org/userprefs.cgi?tab=3Demail ------- You are receiving this mail because: ------- You are the QA contact for the bug. |
