Stephen Rowles wrote: >> Sounds good. As I mentioned I'm sure that the tivo has a much more >> intuitive way of doing all these, I just wanted to point out that the >> functionality exists in freevo. Maybe some of these plugins should be >> activated by default or maybe the documentation should be better but >> that's another debate :) >> > > I that that you have hit the nail on the head for a large amount of > Freevo's draw backs. When I had some issues in the past, and wrote about > things I found frustrating, nearly all of them were fixable by activating > the appropriate plugins or adjusting my config. > > The problem is without asking the list, finding out what to adjust or > activate is next to impossible. > I'd certainly agree. I've been involved with freevo for years and read all the lists to try keep up with things as it's the only way to know everything that's available. 4 things come to mind that would help: 1. CLI config wizard. 2. GUI config editor. 3. Improve the web interface's config editor. 4. Better wiki documentation 5. More contributors to do 1-4
For 1. I think that Duncan has plans to work on this. For 2. there's already the ability to choose some features, for e.g. pressing 'd' on a directory will bring up a wealth of config options, maybe someone could expand on this? For 3 this still needs a fair bit to get to a nice and friendly interface. For 4 it's really the community's responsibility, the developers will code and answer questions but it's the end users that should be helping to make the wiki work. 5 seems to be an ongoing struggle, there's only one person working on 1.x and two working on 2.x excluding occasional contributors. In reality all 5 of the above are needed for things to take a bit step forward. > One thing that would be great would be to consider how Freevo should > behave out of the box, maybe more things should be activated by default. I > know that work is being done on making config easier and hopefully this > will make things easier too as a user can browse the possible options, and > see what is available. > A simple idea for this would be a local_conf_eveythingenabled_example.py to go with the current local_conf_example.py. John ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Freevo-users mailing list Freevo-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freevo-users
