On Tue, 2007-01-16 at 20:20 +0100, Dirk Meyer wrote: > That is what Freevo 2.0 is doing. Freevo 1.x is very complex with too > many dependencies and modules accessing some stuff from others. Like > you wrote before, some plugins access internal stuff of the mixer. To > avoid that we moved many parts out of Freevo into the kaa media > repository. Each module in there is easier to maintain and the > dependencies are clear.
I wouldn't say Freevo 2 will be less complex; in fact I think it will be more complex in terms of dependencies and how components interact simply virtue of the fact that we have much higher expectations and want many more features. But it will be much better designed with clearer interfaces, which means with respect to complexity it scales much better. > > As I see it, the most complicated part of Freevo should be the GTK > > interface. > > I don't see much hope for Freevo 1.x to get an easy config app. It is > just because that we use python code as config file. To keep it > simple, we have kaa.config for 2.0 and it should be easy to write a > config gui for it. I disagree with the direction of a gtk UI for configuration. I think configuration should be web-based. After installing freevo, the web server should work out of the box, and the user can just copy/paste a url into a browser to configure it. Jason. ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Freevo-devel mailing list Freevo-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freevo-devel
