dormant | # 11 | 2009-09-10, 23:09 | Report

• device orientation
• gps status

attila77 | # 12 | 2009-09-10, 23:16 | Report

If the update is an executable or DBUS call it should be doable. I already have custom categories (apart from those dug up from the Maemo launcher), so in that case this could fit nicely (disable updates, and then make it run via shepherd).

Right ! I can already see that vectors will have to be modular/extensible as this has growing potential And since we're on an input frenzy... with a N900 we could also do:

- Light sensor
- Kickstand
- Proxymity sensor

Not sure about the use cases for these, but... that's up to you !

attila77 | # 13 | 2009-09-10, 23:18 | Report

Absolutely ! (That's a new connectivity flag BTW.. new connection, nice, nice)

Saturn | # 14 | 2009-09-10, 23:32 | Report

Could also sent the last known GPS location. Adds also value which later can be used differently. e.g plot in a map your day out.

ColdFusion | # 15 | 2009-09-11, 00:42 | Report

How about a "Dock mode" when the TV out is pluged and external keyboard and mouse are detected? It could start Easy Debian to turn it into a real workstation.

tso | # 16 | 2009-09-11, 02:26 | Report

hmm, i guess one option would be to set the refresh time for the updater to a silly high number, and basically use shepered to run apt-get update at intervals, if wifi is available, but not when phone is.

iKneaDough | # 17 | 2009-09-11, 03:17 | Report

I would like it if it could put the device in silent mode, and disable all audible alerts, when I am in school.

I guess this could be triggered by time (when I am officially in school), and/or location (when GPS detects I am in vicinity of the school, during school hours).

ysss | # 18 | 2009-09-11, 04:18 | Report

Sounds like an awesome project!

But the requests list seems to have grown unnecessarily long already.. I think the features list has to be cut really short to cater to the biggest audience first so the development can go swiftly and focused on the core functions intended..

Then implement the rest as plugins\future developments.

Oh, a more descriptive name would help too

attila77 | # 19 | 2009-09-11, 21:59 | Report

They're all going to be plugins, anyway, so the least I can do is put placeholders there so people can see the ideas, and join in on implementing them. Most of the ideas outlined here were not THAT difficult to implement (CPU/RAM the easiest and location being probably the most complex). In any case, having some ideas how things might develop in the future makes it easier to avoid inadvertently placing nasty dev roadblocks for future development.

It's an established fact that I'm bad at naming projects It started off as something that you know, herds applications out when the weather is nice and there is grass, takes care they don't run away, and such... hence the shepherd association. Thought it would be lame calling it YASA (yet another scheduling app), Puli would probably also mean nothing to most of of the world... But I'm open to suggestions, at least until the stuff enters extras.

PS. For people too lazy to click on the above link:

zerojay | # 20 | 2009-09-11, 22:04 | Report

"Canola" didn't mean anything to the world either, but that didn't stop it.