I wrote down a while back that I had some ideas for the TV side of Freevo and then I completely failed to send the email with what I was thinking :-P.
So here's the ideas that have been floating around for a while, some already exist in Freevo 1 and I think must be incorporated into Freevo 2, others are new. 1. The new TV server/manager should allow plugins and make extensive use of signals (or less likely events). The main reason behind this is that its much easier to compartmentalise new features in this way that will hopefully prevent them from breaking existing code. The hope is that once we have a nice shiny new tv server someone will come along with a good way of using the different signals to allow new features that we haven't thought about (and some that we may have like for example auto-recording based upon what has been recorded and watched etc). 2. The TV server/manager should manage all aspects of the TV viewing/recording use cases. By this I mean that it should deal with the recording side (by allocating devices to use for recording) and the viewing side (by also allocating devices for live viewing and keeping track of what recordings have been viewed). It this respect I am envisaging the Freevo 1 Recording Manager (that collapses series recordings into a single 'directory' entry automatically and also allows a recording to be marked for keeping or as watched) to be integrated into the new server. 3. On the API side, when making an event/program based bookings lets use the unique id from the kaa database to do the booking. ie Only passing this integer to the server rather than passing an object containing the start/end times, title and description etc. This has a couple of advantages, first is the reduction in network traffic and second and more important is if that event is updated after a schedule update the recording also gets the updated information rather than the snapshot when the booking was made. 4. The TV server should provided conflicting programs information. This is very definitely a WAF killer if its not available. Freevo 1 provides this already and the code I've been working on also does although I'm not convinced I've got the display/resolution side of things 'right' yet as it currently shows the recordings based on what tuners they are currently assigned to. What I think we want to do here is provide a list of conflicting programs and then allow the use to deselect those they don't want and 'try' the scheduling operation again. As I've mentioned/alluded to above I've got some of this working already and I need to get what I have got up onto github, hopefully I do that this week. Thoughts people? Cheers Adam ------------------------------------------------------------------------------ Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb _______________________________________________ Freevo-devel mailing list Freevo-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freevo-devel
