< Attached patch rather than inlining >
I've hacked playlist.py to allow for automatic slideshows - when I play
all files (randomly or not) in a directory freevo will show them as a
slideshow.
This requires a SLIDESHOW_DURATION setting in /etc/freevo/local_conf.py
- but will not crash without it.
I've hacked playlist.py to allow for automatic slideshows - when I play
all files (randomly or not) in a directory freevo will show them as a
slideshow.
This requires a SLIDESHOW_DURATION setting in /etc/freevo/local_conf.py
- but will not crash without it.
Not having SLIDESHOW_DURATION set, or ha
would it not be easier and more efficient to have a separate schedule
from the listings themselves? this way, when scheduling a new
recording, you could check the master schedule and react accordingly.
if there is no conflict, a link could be inserted into the master
schedule. if there was, the
Dan Sully wrote:
* Rob Shortt <[EMAIL PROTECTED]> shaped the electrons to say...
Freevo <-> Data Interface <-> Database Plugin
This must be optional. One of the reasons I switched from MythTV, is that
Freevo doesn't require a database. I don't use Freevo for any TV or
RecordingServer activity, so
* Rob Shortt <[EMAIL PROTECTED]> shaped the electrons to say...
Database Ideas:
---
Freevo could really benefit from the use of a database layer, especially
for
handling program data, which ones we'll record, which episodes we've
recorded.
I think this will also make it easier to impo
Ditto, here are some of mine (WIP/RobShortt/IDEAS):
Here are some of my ideas, my online notebook of sorts.
===
User I/O:
-
Here is my idea for handling support for multiple display types and user
input in Freevo. We could use a layer of
Great ideas!
I hope I have more time to help implement them... until now I'm waiting
for your code! :)
The part I liked most is to split modules and reduce/simplify the
code... sometimes when I try to code something quick in the
presentation layer I spend hours to find out where things are... :
To this, I would add 'TV Collision Detection' which sounds easier than
it is. Basically, we need an efficient algorithm for detecting
conflicts. The most intuitive method of just checking each show
against every other is very intensive, and probably not the way to go.
I can't think of anything off
Hi,
[ notice: this mail is stored in WIP/Dischi/future_ideas in CVS ]
This mail covers some ideas what I want to change in Freevo after 1.5
is out. There have been different discussions on the mailing lists
about new features and cleanups and I also did some thinking on my
own.
Since this list i
