Aubin Paul wrote:
> Are there any major changes expected before 1.4 or should we start
> doing pre-releases? It's a big change, and it would be nice to have
> the packages all available at release time too.

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. 

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. 

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. 

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? 

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.

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.

o Besides some small changes I would like to move my tasks to
  usability. 

  - Right now we have 4 config files: freevo.conf, local_conf.py,
    lircrc and the init configuration file. I want to make that easier
    by auto-creating some stuff. Krister made a start by adding rom
    drive detection, Aubin added tv channel list creation. I'm
    thinking of 

    * creating the lircrc if it's missing based in /etc/lircd

    * create better default settings based on the graphic card used (I
      will need help from users to get their settings for this)

  - Better Error messages. Not only local_conf.py not found, better
    output were Freevo looked for it and why this file may be needed
    and how to write it. Some for freevo.conf

  - Write some docs.

o I have one big task on my personal list right now: if Michael is
  finished with the headline plugin for now, I will use it to extend
  the skin in two ways. The rss files also contain a <description> for
  most of the items. So

  - make it possible to have a 'default' menu with information
    area. The listing will show the headlines, the info area the
    description of the item. I don't want to add headline as type to
    the skin, a basic 'info' class showing item.description is better
    for future use.

  - make it possible to get a blank screen from the skin. Maybe the
    plugin wants to display some stuff, independed of skin settings
    with no menu at all. 


OK, I guess this mail is long enough, comments please! 


Dischi

-- 
Always remember you're unique, just like everyone else.


-------------------------------------------------------
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

Reply via email to