On 05/11/2010 13:48, Evan Hisey wrote: > Either way , it looks like some much better documenting of existing > plugins needs to be done. 5 of the six you listed are plugins I have > never seen in Freevo and really have not idea what they do. I suspect > that may be true for many other users. I know there are a lot of > useful plugins but they either have very poor descriptions and or poor > directions on how to setup. > > Evan <snip>
I don't think anyone would disagree with you there and in an ideal world the authors would have written a wiki page as a condition of the plugin being accepted but that's not likely to happen. This is one area though where those of us lacking in programming skills can help out in a big way. It doesn't take in depth knowledge of python to work out what a plugin does and update the wiki with that information. In fact it would be a nice easy exercise for someone to learn how to patch by updating the documentation within the plugin itself. This is important when running freevo -- -i tv.genre for example which should provide a description of the plugin and the configuration requirements. I'll take this opportunity to say if anyone can help with this now is the time. If a few people could do 3 or 4 plugins each quite a lot could be achieved. A wiki page with your name beside the plugin you're going to do would prevent duplicate work being done. Any takers? John ------------------------------------------------------------------------------ The Next 800 Companies to Lead America's Growth: New Video Whitepaper David G. Thomson, author of the best-selling book "Blueprint to a Billion" shares his insights and actions to help propel your business during the next growth cycle. Listen Now! http://p.sf.net/sfu/SAP-dev2dev _______________________________________________ Freevo-devel mailing list Freevo-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freevo-devel
