Chad Robinson wrote: > Dirk Meyer wrote: >> This is also a good place to place a help request here: we need >> help to develop Freevo. Not only python programmers, we have many >> tasks on the todo list. So please, if you have some time, help >> us. If not, I guess the next major release will be 2005. > > I would love to help, and I know enough languages that I'm not > afraid of Python. However, it would be much easier for developers > new to Freevo if you took an hour to put together a "hacker's guide > to Freevo" with some of the basic logic behind how things work. It > took me a long time to decipher how some of the play threads were > managed and I'm still not sure I get it all.
There is a small incomplete PluginWriting HowTo in the Docs directory. But I agree, we need more internal docs. I started adding many comments inside the files I touched (see the image directory for details). But a global doc how files interact and what is were in the source is missing. I guess I need to write a comment what the file does in each file and a small doc about the global design. > Here are some sample questions that might be nice to answer: Feel free, if answering your questions will result in more developers I'm happy to answer. > 1. What are the __init__.py files in each directory? They are called when you import the module. E.g. when you say 'import video', the src/video/__init__.py file is parsed. An __init__ file should not contain much code (I know, we have big __init__ files, but that is bad). Were __init__ is usefull: look at gui/animation/__init__.py. There is an 'from render import create'. After that staement you can use gui.animation.create. > 2. How does one interface with and control the current play list for > the audio/video player(s). For instance, if you want to insert a new > entry before the next item, how would you do this? How does one > iterate across the play list to begin with? All the playlist stuff is in playlist.py. Right now, you can't interface with it, but you can change that if you like. > 3. What are some of these files for to begin with? There are 20-30 > key main and sub-level directories. It might be nice to have a 1-2 > sentence description of the files contained within and their > function. It doesn't have to be long, but at least briefly > descriptive would be nice. On top of my todo list now. Expect more docs on Monday. > Here are the things I would write if I could even figure out where > to start: 1. A function that would take the current audio item's > author, iterate the playlist for the next occurrence, then insert > that item after the current. (This is a "play another song by this > person" function. You can also go by genre/source.) You need to rewrite the playlist.py part for that. Our playlist code is very limited. You may also want to take a look at the sqlite interface (Aubin: what is the current status?) > 2. While viewing a channel, or especially when switching, it might > be nice to have a button (or during switching have an option to do > this automatically) that briefly shows a bar with the TV guide row > for that channel so you can see what's now playing and what's coming > up. Also on my todo list. That is a bit more complicated, the tv part will change. > 3. It would be nice to have the password-protection controls a > little easier to access. Specifically, the ability to enter numeric > passwords via the remote. Maybe this is possible already, but it > doesn't work for me and it's hard to set up anyway - I was thinking > of something arrow-button-based. It is possible, but very bad documented. You can put a password file in a directory. But it would be call to have an item in the directory configure menu to set/del a passwd. > I would be more than happy to contribute documentation, as well, but I haven't > wanted to start until I personally know more about Freevo. We need two kinds of docs: for developer and for users. If you look at the WiKi, I guess there are many things you know that is not in the docs. >> o Web: we also need a better WiKi and maybe someone to do all the web >> updates. Post some news and stuff like that. I don't know what is >> possible on sourceforge and what is not. Or if you have a root >> server somewere were you can host and maintain out website, that >> would be really cool. > > I'm a little confused by this one. You already have a fairly nice and > relatively informative (if out of date) page on Sourceforge, at > http://freevo.sourceforge.net/ > Is there something this isn't letting you do? The WiKi sucks. There is no login so some stupid bots add porn links to it and we have to remove them later again. This isn't very hard, but I don't like it. Dischi -- A man generally has two reasons for doing a thing. One that sounds good, and a real one. ------------------------------------------------------- This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 Project Admins to receive an Apple iPod Mini FREE for your judgement on who ports your project to Linux PPC the best. Sponsored by IBM. Deadline: Sept. 13. Go here: http://sf.net/ppc_contest.php _______________________________________________ Freevo-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freevo-users
