Hi, On Sunday 09 October 2011, meik michalke wrote: > i think we discussed that when the feature was implemented. the idea is > similar to the all.pluginmap file, that is, with all.maps=FALSE only files > called "<package_name>.pluginmap" will be added by default, and what you > want to be loaded automatically should be in that (meta) file. that way > you are able to provide experimental/alternative pluginmaps you don't want > to be found by default in the same package.
ah, yes, now I remember. > i fixed the above issue by > adding a rkwarddev.pluginmap with a <required> tag including the actual > pluginmap. i'd say it should stay as it is. we could change the name of > the eventual meta file perhaps, like into "index.pluginmap", to make its > purpose more obvious. maybe even i won't forget about it the next time, > then... or, perhaps we could reverse the convention. E.g. all .pluginmaps would be included by default, except for those with names starting with "_" or ".". That would still allwo plugin authors to "hide" some .pluginmaps, without the need to bundle all "official" plugins in a single map. > however, i had the same problem with koRpus, and i could only fix it by > manually removing its pluginmap entry from the "All known plugin maps" list > in the rkwardrc file. in the long term, it would be nice to have this list > completely in the configuration dialog, and checkboxes next to them like > in the package management dialog. by the checkbox you'd then be able to > (de)activate pluginmaps, and non-existing pluginmaps should be removed > automatically. new plugins should still be added & activated by default. Yes, that's definitely the way to go. But of course it will take time to implement... Regards Thomas
signature.asc
Description: This is a digitally signed message part.
------------------------------------------------------------------------------ All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2dcopy2
_______________________________________________ RKWard-devel mailing list RKWard-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rkward-devel
