Hello list, I'm glad to announce a new version of the filebrowser plugin, you can get it from http://www.stud.uni-karlsruhe.de/~uqg8/vdr/filebrowser/vdr-filebrowser-0.0.4...
This release includes a directory "developers" containing an example how to use filebrowser in your own plugin - any comments on this are especially welcome. I decided against using Service() that you don't need to have users of your plugin to install the filebrowser plugin.
Changelog:
- Added some #ifdefs for simple recycling of filebrowser's classes in other plugins - refer to developers/filebrowserdemo/README on how to do this (thanks to Gerhard Steiner) - Superseded the possibility to change the base directory via setup menu by sources command to protect system files (inspired by Andreas Leipelt) - Changed file pattern matching not to treat beginning period specially - Use ksh-style file pattern matching - refer to http://www.gnu.org/software/libc/manual/html_node/Wildcard-Matching.html#ind... on how to use this - Possibility to define filters in sources.conf - Added possibility to call plugins image mplayer mp3 via filebrowser. You need to apply appropriate patches to the plugins (or ask their maintainers to add them to upstream)
Your comments, bug reports and patches would be appreciated, regards Holger
This file resides in $PLUGINDIR/filebrowser/sources.conf so it shouldn't collide with the one in $VDRCONFDIR. The name "sources.conf" was infered from *sources.conf files in $PLUGINDIR that serve a similar purpose, the prefix was removed for I use an own directory for the config files. Should it be a bad idea to name the files in a plugin's dedicated config directory the most convenient way?
Regards Holger
Holger Brunn wrote:
Well, basically you can name your files whatever you like. I just thought that if, in a discussion, somebody speaks about the "sources.conf" file, it might be unclear which file is actually meant.
Personally I have no problem with that, because I only use plain vanilla VDR ;-).
Klaus