Hi Tanja! On Thursday 31 March 2005 00:49, you wrote: > Thanks again for all your work! I am very interested in that topic and > appriciate your work, really... > So please, do not see my suggestions a criticism! No, I am thankful for your comments!
> > > I think a good solution would be an integration of your work and > > > Georg's work. My idea is to have > > > 1) a idletimer plugin, which decides when it is time for shutdown. > > > > Why this way and not that which I described in my last postings? > > You suggested to register all jobs to the recordserver, right? Yes and no - I dislike the idea that my Freevo shuts down if I do not use it (the idletimer method). I think the user should always initiate the shutdown. Of course, if he/she shuts down the system, there should not be "active jobs" (which could be recordings, transcodings, CD/DVD ripping, ...). I propose a "waiting for XXX to finish..." dialog in that case, where one can press cancel if one decides that one wants to listen to music again / similar. When Freevo boots up, I would add a check whether this is within a small time window after the programmed bootup, and then directly start that shutdown wait screen. If that happens in the middle of the night, Freevo will just shutdown after the recording, but if you happen to see it and want to use your Freevo box, you could press "Cancel". > I agree totally in this. Will something like that be implemented in > freevo2.0? For the moment I am just looking for a fast and easy solution. I think this wait-dialog shouldn't be much more difficult than the idletimer, but one needs to know the Freevo UI internals (which [un]fortunately changed between 1.3.x and 2.0, so I am not sure if it's worth implementing ATM). > Moreover I understood from your postings that your patches are not able to > shut down freevo automatically after a recording? Right. > The idletimer plugin would solve that problem. ..I'd prefer the word "work around".. ;-)) (Actually, you can find in the archives that I planned to do that, too; there's already a screensaver plugin which would be quite easy to adapt. However, I don't like the idea anymore after I came up with the above.) > > > 2) a shutdown helper, who shedules the wakeup and shuts down the system > > > (this could also be called outside of freevo, instead of "halt" or > > > "shutdown") > > > > Should be trivial to implement on top of my patch. > > I guess so, that is why I am so interested in your patches. > A helper script which is callable from inside and outside freevo, has the > advantage, that you can make it the preferred shutdown methode of your > system. Moreover it is usable for the automatic shutdown and the shutdown > form the menu. You're right; actually that's something I've been thinking about already. (How to cope with external shutdowns.) An even more reliable method would be to call nvram-wakeup from within the recordserver as soon as the program schedule changes; as long as no reboot is needed, this allows even an external halt, even a power outage at any time.) > > > 3) an improved shutdown plugin, which warns if there are > > > recordings in the near future and gives the possibilty to stop the > > > automatic shutdown (idletimer) > > > > Apart from the idletimer stuff, that's contained in my patch. > > Yes, as I said : "A intergration of your solutions and Georgs solutions!" I must admit that I did not have the time to look at his stuff. (And won't before April 16th.) > Thanks again, I hope it is okay for you, if I am messing around with it a > little bit? Of course! Greetings from Hamburg, Hans ------------------------------------------------------- This SF.net email is sponsored by Demarc: A global provider of Threat Management Solutions. Download our HomeAdmin security software for free today! http://www.demarc.com/Info/Sentarus/hamr30 _______________________________________________ Freevo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/freevo-devel
