Grilo Config suggestion



Hi,

As I see some plugins need some some config keys set (e.g. YouTube), or some config keys may be set optionally (e.g. filesystem).

But if I am not wrong there is no way in the current API to discover what keys are needed, except to read in the code or documentation.
This prevents to add a new plugin to an existing app without having hard coded knowledge in the app about the plugin.

Wouldn't it be better to add the individual config keys as GObject properties in the GRIO Plugins? The the available properties ( Like User, password etc.) could then  be discovered by  g_object_class_list_properties.

Regards,
Roland



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