Hei list, I am really interested in contributing in freevo hacking, (wrote some plugins allready) but one big problem is, that I do not really know the plans of the head hackers yet!
When I wrote plugins for 1.x I found a lot places in the code that should be redesigned or even cleaned from cross dependencies and other software design problems... but thinking about freevo 2 I hope for a wonderfull (software-)world where everything is fine and where hacking is easy and self understandable... Thus I am not longer interested in hacking for freevo 1.x as long as I think that my code will not be needed in freevo 2 anymore... Shouldn't we go straight to freevo 2 and forget all the detail problems of 1.x? In fact: I am interested in coding for freevo 2 but I do not see the big plan behind it yet...: - how will the configuration be? - how will the plugin structure be? - the event handling, polling? - what could the interface be between core and modules (like kaa)? - and so on. I think a discussion like that could bring freevo ahead, and bring freevo hackers together. I propose that today the most freevo users are hackers as well, and it should be possible to organise them... Andreas ------------------------------------------------------------------------- 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
