On 7/26/07, Ahmed Ghoneim <[EMAIL PROTECTED]> wrote: > On 7/26/07, Mohammad DAMT <[EMAIL PROTECTED]> wrote: > > if a vendor wants to provide an audio package > > which can't be handled by the standard libquran, the vendor can just > > provide the audio package and the plugin. > > how is the vendor going to supply the plugin? inside the audio package > directory structure?
No. They will ship under (in Linux) /usr/lib/libquran/ > how is the lib going to determine if can handle the format or not? MIME types? Yes. > should the should the package info contain something that says "use > this plugin". i.e. should the plugin be package specific (each package > has a plugin) or should be system (lib) specific with some kind of > mapping from MIME to plugins? Yes, this is probably needed. For example a vendor could prefer to have it's audio set to use it's own plugin instead of the system's one. Even if the system already have a plugin which can handle the audio set. A plugin.txt probably needed inside the audio subdirectory containing the plugin name. _______________________________________________ Developer mailing list [email protected] http://lists.arabeyes.org/mailman/listinfo/developer
