>But you will find that if you remove CustomBrowse and TrackStat all of >a sudden it will only use half of that. I know - but that's not due to a few options, or a bit of code to support the options.
I actually think it would be better to split CustomBrowse into a smaller plugin for core stuff, and one or more extra plugins that can be installed if required. eg. for custom menu configuration through templates, another one for mixers, maybe one for headers/footers (which I'm sure is not customised by many people, as this is advanced/scary!). There are actually only ~12 options for the CustomBrowse plugin settings. Some of these could potentially be removed; eg. hard-code the location of various directories. Menu name and position could be hard-coded; SBS core functionality (or another plugin) should allow all menus to be configured. I doubt there's much code/resources being consumed behind any of these options, and 12 is not a large scary number. Other configuration stuff is for managing menus within Custom Browse. Maybe this consumes a lot of memory, and is not often used. i.e. once set up, a user may use the menus, but doesn't need to HTML configuration screens very often. _______________________________________________ plugins mailing list plugins@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/plugins
