Xiretal X wrote: > Hi Colin, > > I have to admit that I'm total noob with mailing lists. :D I've no idea > how to reply to mailing list. Should I just post to that > [LIST MAIL ADDR]?
Different lists have different etiquettes but it's quite common to do a "reply all" and just send it. This will include the specific person and the mailing list in the reply - this works if mailing list is configured to allow anonymous posting. Personally I always read the list so just using the list address is fine for me :) (I actually use NNTP and www.gmane.org to read mailing lists rather than subscribing to them per-se but this is another matter!) > Can you describe how your project works? Perhaps refer to VDR/Myth and > make a little comparison? > > > Well, this is at the very beginning of the development still. The high > level architecture uses client-server, so there is a backend and > frontend. All media is cached using SQLite and filesystem changes are > automatically updated to the cache with pyinotify. At the moment I have > image, music, video and feed caches. Movie and TV-series metadata is > downloaded automatically from IMDb. Also album art and song lyrics are > downloaded. Feeds are updated every now and then (interval can be > selected). Cool. One thing I've noticed when dealign with such applications is that projects appear to always reinvent the wheel. Amarok, Myth, etc. etc. all have their database (SQLite, MySQL or whatever) that cache the changes. I wrote about this a long time ago and about the need to standardise on a common framework such that the indexes and caches could be reused in other apps. http://colin.guthr.ie/general/development/metalibrarian.html Since writing that, I think something like Tracker (http://www.gnome.org/projects/tracker/) could provide the necessary backend indexes rather than doign it yourself. The trouble is, there then becomes the problem of KDE Vs Gnome Vs Xfce etc. Tracker was originally meant to be Desktop agnostic, but it doesn't seem to help in terms of KDE stuff. Strigi (http://www.kde-apps.org/content/show.php?content=40889) appears to be the KDE 4 indexer of choice. Where some hope lies is that there now appears to be a FDO standard for querying such indexes: http://freedesktop.org/wiki/XesamAbout I just hope that such a system will work. Perhaps it's worth looking at for your project? Just my thoughts - it may not be practical at this stage (of both your and other projects), but I hope this is where things will go in the future. > The core of backend is a messagebus that connects all the components to > each other. Components communicate with messages. Also other processes > can be binded to this messagebus via busproxy object. So it's easy to > make frontend to communicate with backend components. > > I've actually drawn many UMLs and written some documentation. Maybe I > will put those to the net in near future. > > The aim of the project is to be EASY TO USE and SIMPLE media center. I > also find all Linux media center GUIs... well, not too attractive so > that is of course important part. THis is great. I really, really want someone to create a NICE GUI for a linux media centre. Good separation of client and backend is also important for me. I want to create lightweight frontends that just network boot and do very little processing other than playback. This is how I currently work with Myth although as I stated before it's separation is not perfect. Please keep up the good work. Let me/us know when you get a website for the project together :) I've replied to the list here but marked it as OT as it really is. Didn't feel this should be restricted to a private conversation tho' ;) Col -- To unsubscribe send a mail to [EMAIL PROTECTED]
