Thank you, Simon<br><br>MythCollection is not only good for your own browsing needs. I find it rather helpfull when organising a video night with friends. They can access my list online and then we decide.<br>I am already thinking of some kind of voting feature for the future.
<br><br>Now about your question.<br>MythCollection gets triggerd by mythburn.py and uses mytharchivehelper but is otherwise independent of the mythfrontend. I am sure a marketing department would call this an Integration but it is nothing you can see in the interface.
<br>With MythWeb there is even less Integration it is an independent Web Implementation based on the rails framework. It even brings its own webserver so no need to mess with apache configuration files. While this has many advantages for developers, when you place a link in MythWeb you will hardly notice there are indpendent apps at work. For me it is more important to have a solution that intgrates well with the workflow of the archiving process.
<br>Actualy with my friends visiting MythCollection i would not want them to be able to start recordings or delete movies. Therefore i think the fact that MythCollection is not integrated with MythWeb is an advantage. But this is open to discussion.
<br><br>I can put some Screenshots of MythCollection online if you are interested. At the moment i am working on MythCover after that i have to have another go at the html design. And then i will probably work on the webburn part of MythCollection unless a mythwebburn based on MythWeb will show up.
<br><br>I hope this answered your question.<br><br>regards tom <br><br><br><div><span class="gmail_quote">On 15/11/06, <b class="gmail_sendername">Simon Dyson</b> <<a href="mailto:sdyson@themaelstrom.co.uk">sdyson@themaelstrom.co.uk
</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">I think Tom has a great idea here. At the moment I'm keeping my burnt<br>
DVDs in a large flight case which saves a lot of space but isn't<br>anywhere near as easy to browse as a load of DVDs cases on the shelf so<br>it would be good to browse the collection via MythTV.<br><br>Tom, it sounds like what you've done integrates with MythWeb but not
<br>with MythFrontend - is that right?<br><br>Simon<br><br>tom roth wrote:<br>> Now that MythArchive is so successfull (Congratulations to Paul) i<br>> recently experienced a spark of interest in my MythArchive Extension
<br>> MythCollection.<br>> The Goal of MythCollection is to help you keep track on the movies you<br>> have archived. It also supports you on the generation of a nice<br>> CD-Cover and there is a (rudimentary) webfrontend for mythburn. Now
<br>> before you all get excited, while this works rather well for me, this<br>> is pre-alpha software. It consists of:<br>> - mythcollect.py a python script that gets called by mythburn.py,<br>> looks at the jobfile and writes title and description of the archived
<br>> files into the mythcollection table. Of course this is optional and<br>> can be configured with an option in mydata.xml.<br>> - mythcover.py, another python script that gets (optionaly) called by<br>> mythcollect.py
and creates a cd-cover using a screenshot of the movie.<br>> - MythCollection, just another moviedatabase integrated with the<br>> mythtv database. MythCollection does the following:<br>> - - Enrich the movie information by an IMDB lookup.
<br>> - - Provides a browse and a search interface (using ajax)<br>> - - Manual Editing<br>> - - Shelf organisation with index markers<br>> - - CD-Cover generation. Here mythcover.py is called again, but this<br>
> time there a more options to influence the generation process.<br>><br>> I use MythCollection to keep track of all my Movie including the DVDs<br>> i bought. I also set up a rudimentary webinterface to call mythburn from.
<br>><br>> If this is of any interest to you i could send you the code and help<br>> you setting it all up until a installation routine is written.<br>> At this stage it would be best if you knew how to write bugreports and
<br>> a little python and/or ruby would be helpfull.<br>> MythCollection is a ruby on rails application. Now why did i do this ?<br>> There are several reasons:<br>><br>> - I looked at mythweb and found the code quite complicated to
<br>> integrate another module. This is by all means no complaint against<br>> mythweb, which i like and use often.<br>> - My first Announcement of MythCollection met with little interest so<br>> i choose a route more convenient for me.
<br>> - I wanted a granular Authentication schema which allows me to put my<br>> collection online for my friends to see, but restrict the editing part.<br>> - Configuring apache is rather complicated and i do not want to
<br>> support that.<br>> - I think with webapplications you can do seamless integrations on the<br>> frontendview even with diffrent backends.<br>> - Rails is fun ;-)<br>><br>> regards tom<br>> ------------------------------------------------------------------------
<br>><br>> _______________________________________________<br>> mythtv-users mailing list<br>> <a href="mailto:mythtv-users@mythtv.org">mythtv-users@mythtv.org</a><br>> <a href="http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users">
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users</a><br>><br>_______________________________________________<br>mythtv-users mailing list<br><a href="mailto:mythtv-users@mythtv.org">mythtv-users@mythtv.org</a><br>
<a href="http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users">http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users</a><br></blockquote></div><br>