On Sat, Oct 25, 2003 at 01:22:37PM +0200, Robert Rozman wrote: > I see that there are two different fucntionalities currently done in Freevo: > one being TV GUI and other fetching data to display on TV. What do you think > about solution that we separate those two functionalities further away and > put some sort of buffer between them (like mySQL or any other lighter > database). In this way we get some sort of backend (fetching all those data) > and GUIs (in this case we can have more than 1) that are only in GUI > function...
There is a buffer; there is something called the record_server, which handles data fetching, and providing a simple interface for scheduling recordings. It's already possible to use both the TV interface and a web interface to search, and schedule programs. It's all done via XML-RPC, and you can thank Rob for that :) > It would be certainly easier to connect them to database rather than to > Freevo. At some point doing Freevo in backend/frontend would be necessary > cause tommorow users will have more and more TVs, video outputs and PCs. So > taking this step earlier could be advantage in future... Hypothetically, it could be possible to move the data into a database and have the record server query that instead of the cached file, but frankly, it wouldn't give a huge speed increase, and wouldn't make the functionality much different. > I don't know much internals about Freevo but according to mailing list it > seems like Freevo is getting quite complicated system (that's probably > opposite of its mission) because more and more options are added that are > probably more on data fetching than GUI part of it... I don't think it's getting more complex; more functionality have been moved into plugins, which is more of a statement about the simplicity of the core. > Somewhere in the way is probably also need for mouse support. If Freevo will > be adopted by users on TV, then they will probably want to use it also in > normal PC... If we cooperate with more general GUI now, that (and any other > problem) would not be a potential problem anymore. That's a big request, and would require major work to the gui components. I don't have Freevo on a PC (why would I?) so I can't commit to the time to add that kind of stuff to it. Freevo isn't meant to be a 'file launcher' because it has limited functions compared to say, something like iTunes or GNOME for that matter. Aubin ------------------------------------------------------- This SF.net email is sponsored by: The SF.net Donation Program. Do you like what SourceForge.net is doing for the Open Source Community? Make a contribution, and help us add new features and functionality. Click here: http://sourceforge.net/donate/ _______________________________________________ Freevo-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freevo-devel
