epoch1970;380069 Wrote: 
> Gharris999, that's quite a list of new features you have here; kudos for
> your work.
> I haven't tested the new version of the plugin yet, will do so soon.
> (and update strings.txt as an aside)
> 
> As planned my own SB gear is now down to a single Duet, and SC running
> in a VM on an always-on server... Until I revive another home server
> project for friends or family I was thinking I may be could contribute
> a bit to your plugin ?
> 
> These are areas I think interesting:
> - An OS X power daemon. Runs as root aside SC, and accepts
> SSL-verified connections from the plugin to return its current power
> state assessment and to take reboot/shutdown/sleep actions. I have OS
> X.5 and X.4, could install X.3 (I think), on 2 Intel-based macs.
> (Perhaps this could be generalized to other platforms, to conceal all
> nitty-gritty power management details, and provide a
> platform-independant API -tcp- to the plugin.)
> - Plugin settings web page redesign. With tabs and all; I already did
> a few mock-ups. This needs some thinking and good understanding of
> features dependencies in the plugin. I expect the HTML/TT/JS
> implementation wouldn't be too difficult.
> - Controller scheduled WOL applet. Starting from scratch, for me. 
> - "pimp my playlist": testing a way to add -an internet?- WOL service
> to an existing alarm playlist. Intriguing and should be fun, but I
> don't see how this can be completely packaged with the plugin  if
> someday it works.
> - A power-saving agent that would integrate users behaviour to take
> actions (AI). Seems possible; But if we want the agent to be smarter
> than Clippy, someone knowledgeable in AI would better chime in...
> 
> I don't know how much time I could spend on one of these subjects; I'd
> like to play it light on maintenance once stabilized. Let me know what
> you think.
Epoch1970: I’ve been meaning to add an acknowledgements section to the
plugin's readme file.  I'd like to acknowledge here how much I have
appreciated all your helpful hints and ideas.  All the "wakeup for
alarm" code in the latest release, of course, was inspired by your
example.

I would certainly welcome any contributions you would like to make to
SrvrPowerCtrl.  All of your ideas are good ones and the areas that you
suggest you would be interested in working on are all areas that could
use the work.   

A tabbed settings page would be genuinely helpful.  Also, I think a
link on the settings page to a comprehensive readme will be necessary
if SrvrPowerCtrl is ever to be usefully installable from the "Extension
Downloader" plugin.

Re the Mac / platform independent power management daemon with tcp
interface:  this idea is certainly beyond the ambitions that I’ve had
for the plugin.  I'm not completely sure I see the advantage of trading
flexibility in the execution of various system power control commands by
the plugin to adopting a unified tcp based interface to various services
/ daemons – all of which we would have to write.  As it stands, I have
no idea what it would take to make SrvrPowerCtrl work on Solaris or on
FreeBSD.  But I suspect that there are shutdown/restart/suspend/etc.
commands available on such systems so that SrvrPowerCtrl could be made
to work now without the need to write a discrete daemon for each
platform and each architecture on each platform.  But perhaps I haven’t
really understood your rationale for this sort of setup.

For now, I think the most immediate need is to extend the rtc wake
alarm to OSX.  I haven't even begun to look into this.  Hopefully, all
that would be required would be to add another case statement to your
OSX helper script.  Would you be willing to look into that?


-- 
gharris999
------------------------------------------------------------------------
gharris999's Profile: http://forums.slimdevices.com/member.php?userid=115
View this thread: http://forums.slimdevices.com/showthread.php?t=48521

_______________________________________________
plugins mailing list
[email protected]
http://lists.slimdevices.com/lists/listinfo/plugins

Reply via email to