![]() |
Re: [User feedback request] Shepherd
Canola is a made-up word that was formed from words meaning "Canadian Oil". Why? Well, "rape seed oil" just doesn't have a good sound for marketing.
Why someone chose the word for rape seed oil for their media player is less clear, however. |
Re: [User feedback request] Shepherd
feature idea: location and/or time defining what profile gets activated (normal, silent, OUTDOORS, meeting, etc).
i can think of lots of places where i'd love to have my (soon-to-be-in-my-hands) n900 automatically switch to silent :) |
Re: [User feedback request] Shepherd
Hi, filled an enhancement request in bugzilla for the the automatic updates thing discussed earlier in the thread.
If you feel like, please give it a vote. |
Re: [User feedback request] Shepherd
Have you seen GlovePIE?
I once envisioned a language based on GlovePIE's "declarative"/"eternal while true loop" idea managing from input mapping to a load of events. The syntax was kinda like: Code:
on (Script.started) { Unfortunately I only got to the parser before wandering off and pushing it to the bottom of my TODO pile, but if you're looking for ideas.... (even though this one is a geekish). You can use a Python VM too, or just the GUI option and be done with it, but I usually find them lacking unless they're really, really complex, in which case it usually defeats the purpose. |
Re: [User feedback request] Shepherd
Quote:
|
Re: [User feedback request] Shepherd
For the automatic update stuff... This is handled by AlarmD, so it's actually rediculously easy to disable/enable; just remove the event from the alarmD queue, and in its place add a new event that will check against the type of connectivity and only run the updater if wifi is active. Really has nothing to do with shepherd at all, unless you wanted to use shepherd to set a nice flag in gconf/temp file somewhere to indicate when you were on wifi vs anything else?...
i.e. From the alarmD queue right now (/var/lib/alarmd/alarm_queue.xml): Code:
<object type="AlarmdEventRecurring"> Code:
<object type="AlarmdEventRecurring"> -Rob |
Re: [User feedback request] Shepherd
@javispedro: have not seen it, thanks for the tip, will take a look
@iKneaDough: it is already a two-component software. The 'daemon' part runs in the background and is controlled by config files. The WiP GUI part is just a front-end for user friendly editing these config files and signaling reload/start/stop to the daemon. @jolouis: I agree shepherd is not necessary to change how you deal with updates. That said, the lure of using shepherd for such a task is to be able to *easily* combine the action with any vector provided - particular provider, location, etc. |
Re: [User feedback request] Shepherd
Great idea! :)
|
Re: [User feedback request] Shepherd
Just ran accross this headset thingie... You know where this is going (apart from the end of the already longish todo :) ) - make the headset button perform different tasks depending on shepherd parameters :)
|
Re: [User feedback request] Shepherd
Quote:
http://geekandpoke.typepad.com/.a/6a...599062a970c-pi |
All times are GMT. The time now is 17:49. |
vBulletin® Version 3.8.8