On Thu, Sep 04, 2003 at 03:28:46PM +0200, Dirk Meyer wrote: > As Michael wrote: we are waiting for the new recorderserver to move > into the main cvs branch. After that is done, we should release > 1.4-rc1 or 1.4-pre1. > > Here are also some random thoughts about the next release and what we > should put in it: > > o Move the splashscreen settings into the skin.
Yes, though the default background should probably be the skin default; the one that it's using now is quite harsh because of the 'grid' > o Some files in src/tv look like they aren't used (imported) > anymore. Do we still need them? The files are ivtv.py, > program_search.py and program_display.py (they only depend on > eachother), and please take a look if all plugins still work. Ask Rob :) > > o What is the status in tv? We will get a new recordserver, but what > about live pause? Does it work? Aubin, what is your status on a xine > plugin for tv? Maybe someone can send me a short list what is > working, what someone is working on and what is on the todo list. The problem with the xine plugin isn't Python, but that I can't figure out how to send a channel change request to libxine from fbxine. My C/C++ mixture reading isn't so good :) > o I want to remove testfiles as discussed some weeks ago. I will > create a small tarball on the website. Or maybe we don't need it at > all? Might as well put up a tarball, but it definitely doesn't need to be in CVS. > > o Remove the runtime directory from the freevo cvs tree. Freevo itself > doesn't need the runtime and should be 100% Python. I would create > an extra repository for the runtime because it should still be under > cvs control. Makes sense... > o Since Freevo should be 100% Python, Gustavos audio goom display > should also get a repository on it's own. Or maybe a repository > freevo-apps containing all non Python apps we will write. The binary > of cause should be part of the runtime. And I'm thinking of a way to > integrate the tool itself. A seperate repo. makes sense; maybe call it "freevo-support" since most of the major Linux packages seem to have one like that (kde-support, gnome-common) etc. > * creating the lircrc if it's missing based in /etc/lircd Are you thinking of using pattern matching to "guess" what the buttons are for? That might be difficult... > * create better default settings based on the graphic card used (I > will need help from users to get their settings for this) There are a couple of things in pygame/SDL that you could use: 1. Make an array of output types and the respective "ideal" resolutions, i.e. mga - 768x576, x11 - 800x600, etc. Use pygame.display.list_modes and pygame.display.set_mode to try them... Aubin ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Freevo-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freevo-devel
