Active Topics
-
Firefox with Leste (10)
to Maemo 7 / Leste by teroyk - 4 days, 3 hrs ago - more...
| The Following User Says Thank You to shvedsky For This Useful Post: | ||
|
2010-04-09
, 06:48
|
|
Posts: 3,319 |
Thanked: 5,610 times |
Joined on Aug 2008
@ Finland
|
#92
|
Originally Posted by shvedsky
More helping hands are always welcome ! We already have a GSoC application (and one submitted student proposal which is concentrating on the API and verious plugins mentioned in this thread), but that does not mean you can’t make your own proposal ! As for the thinnest of all areas, that must be the Qt GUI, and our current proposal is also more plugin oriented.
Shepherd is an application a lot of users would like to see done, with a rich set of actions and with integration into desktop. As a student, who is eligible for the Google Summer of Code program, I can help with getting this done and doing all the menial work it takes to develop an app of good quality.
First, is such collaboration possible? And if it is, what is still unimplemented amongst the desired features?
Also, regardless of GSoC I’d like to see some contributors/volunteers ! The reason the code/app is not in extras-devel is that it’s all too easy to brick yourself with incorrect power management or network settings, but if you’re a developer, it’s not that much of an issue and a lot of stuff *can* be done even on desktops (Qt FTW) so join in to make the project ready for Extras !
__________________
Blogging about mobile linux - The Penguin Moves!
Maintainer of PyQt (see introduction and docs), AppWatch, QuickBrownFox, etc
Blogging about mobile linux - The Penguin Moves!
Maintainer of PyQt (see introduction and docs), AppWatch, QuickBrownFox, etc
| The Following 3 Users Say Thank You to attila77 For This Useful Post: | ||
|
|
2010-04-09
, 10:39
|
|
Posts: 3 |
Thanked: 3 times |
Joined on Feb 2010
@ Moscow, Russia
|
#93
|
Originally Posted by attila77
The thing is that making up a succesful proposal (with high chance to be accepted) requires outlining the schedule of what will be done. Maemo has a lot of project ideas, and competition will be high. So the proposal to improve shepherd should look as good as possible in the eyes of mentors. And as usual it should be done "by yesterday" so it's only several hours left to deadline (but that's totally my fault).
More helping hands are always welcome ! We already have a GSoC application (and one submitted student proposal which is concentrating on the API and verious plugins mentioned in this thread), but that does not mean you can’t make your own proposal ! As for the thinnest of all areas, that must be the Qt GUI, and our current proposal is also more plugin oriented.
I couldn't find source code of shepherd anywhere, so I'll try to outline what tasks there are in the project and what progress is made. It's just my guesses, and sorry if I offend you with underestimation. :-) I'll rely on the following guesses in my proposal, but if you correct something, I can fix my proposal as well.
- A nice, non-geeky GUI in Qt - GUI currently is very basic, and the Qt features used suffer from platform bugs
- API for plugins - works, but needs improvement
- Plugins (both conditions and actions) - several basic ones are ready, creating more plugins is necessary
- Scheduling functionality - completed and very powerful
- Integration with the OS (in plugins) - needs improvement, so that user just clicks buttons and doesn't input scary numbers :-)
- integration with a mapping application for location-based conditions - not done
Did I miss or underestimated completion of something?
Last edited by shvedsky; 2010-04-09 at 10:51.
|
|
2010-04-09
, 10:55
|
|
Posts: 3,319 |
Thanked: 5,610 times |
Joined on Aug 2008
@ Finland
|
#94
|
Originally Posted by shvedsky
Well, likely I'd be that mentor (already talked about it with vdvsx, our GSoC coordinator).
So the proposal to improve shepherd should look as good as possible in the eyes of mentors.
[*]A nice, non-geeky GUI in Qt - GUI currently is very basic
The core uses Qt, but is set/communicated with via config files (which we would need the GUI for, to make it useable to end users).[*]API for plugins - works, but needs improvement
[*]Plugins (both conditions and actions) - several basic ones are ready, creating more plugins is necessary[*]Scheduling functionality - completed and very powerful[*]Integration with the OS (in plugins) - needs improvement, so that user just clicks buttons and doesn't input scary numbers :-)[*]integration with a mapping application for location-based conditions - not done
, and the mapping application - location stuff is supported by system libs). So, as said, the thinnest segment is the GUI, but based on the feedback from this thread there is no such thing as too many possible triggers or actions
I will try to make some introductory docs (Shepherd from 10.000 ft) and a code drop. I'm sorry that I did not think about it earlier myself. Until I got the GSoC request just a couple of days ago, I just waited for the PR1.2 mess to resolve and to have some safeguards in place, but now I realize I should have had at least something at the ready (yes, release early, release often, duh
).
__________________
Blogging about mobile linux - The Penguin Moves!
Maintainer of PyQt (see introduction and docs), AppWatch, QuickBrownFox, etc
Blogging about mobile linux - The Penguin Moves!
Maintainer of PyQt (see introduction and docs), AppWatch, QuickBrownFox, etc
Last edited by attila77; 2010-04-09 at 10:58.
|
|
2010-04-09
, 12:02
|
|
Posts: 3 |
Thanked: 3 times |
Joined on Feb 2010
@ Moscow, Russia
|
#95
|
Originally Posted by attila77
That's good news! But as far as I'm aware of the proposal selection process, the more mentors consider the application cool, the more chances to be accepted it has.
Well, likely I'd be that mentor (already talked about it with vdvsx, our GSoC coordinator).
More like stabilization to be interesting to 3rd party developers (not much fun in developing for a moving API).
Correct (except for the buttons, we don't have those yet
About location: locations can be processed without mapping application, that's true. But it would be very cool for user to actually see on the map the locations of interest, set them manually, adjust radius, etc. Check the Android Locale screenshots.
It will increase the user base of Shepherd dramatically: people love bells and whistles. And it will increase the user base of the application Shepherd would be integrated with, so I don't think its maintainers would be unfriendly.
So, as said, the thinnest segment is the GUI, but based on the feedback from this thread there is no such thing as too many possible triggers or actions
|
|
2010-04-20
, 18:57
|
|
Posts: 258 |
Thanked: 138 times |
Joined on Oct 2009
@ St. Louis, MO, USA
|
#96
|
Ok, so I'm going crazy waiting for PR1.2's release mostly so I can play with this app and start going script crazy.
In the meantime I'll ask some questions about the app's current and planned capabilities.
Predicates that I'd like to see:
* location (position, allowed radius, accurazy, speed)
* time of day / day of week (cron style or whatever)
* time interval
* internet connection (cell connection vs wifi--including ESSID)
Actions that I'd like to see:
* run an app (determine if it's running--if not, start it up)
* close an app
* set profile (ringer, volume, etc)
* toggle FM transmitter
* run general script, which can totally open up opportunities
Addition desired features
* Easy way to share new predicates and actions (single, self-contained file or folder for each one? Maybe some sort of hosted repository of them?)
How else are people hoping to leverage this app? Kill time with me.
In the meantime I'll ask some questions about the app's current and planned capabilities.
Predicates that I'd like to see:
* location (position, allowed radius, accurazy, speed)
* time of day / day of week (cron style or whatever)
* time interval
* internet connection (cell connection vs wifi--including ESSID)
Actions that I'd like to see:
* run an app (determine if it's running--if not, start it up)
* close an app
* set profile (ringer, volume, etc)
* toggle FM transmitter
* run general script, which can totally open up opportunities
Addition desired features
* Easy way to share new predicates and actions (single, self-contained file or folder for each one? Maybe some sort of hosted repository of them?)
How else are people hoping to leverage this app? Kill time with me.
 |
|
2010-04-20
, 19:19
|
|
Posts: 246 |
Thanked: 204 times |
Joined on Jun 2007
@ Potsdam (Germany)
|
#97
|
Originally Posted by twoboxen
I would add:
Predicates that I'd like to see:
* location (position, allowed radius, accurazy, speed)
* time of day / day of week (cron style or whatever)
* time interval
* internet connection (cell connection vs wifi--including ESSID)
* Connected Bluetooth devices
* battery level
And of course a mix out of more than one predicate.
Actions that I'd like to see:
* run an app (determine if it's running--if not, start it up)
* close an app
* set profile (ringer, volume, etc)
* toggle FM transmitter
* run general script, which can totally open up opportunities
* Switch status of IM Accounts
* Get emails for specific accounts
* Trigger sharing services (e.g. Upload new photos to flickr)
* Do software upgrades in background
* Syncronize (e.g. Syncevolution)
Are there already any mock-ups or thoughts about a user interface?
Ciao jukey
__________________
| The Following User Says Thank You to jukey For This Useful Post: | ||
|
|
2010-04-20
, 19:28
|
|
Posts: 258 |
Thanked: 138 times |
Joined on Oct 2009
@ St. Louis, MO, USA
|
#98
|
Originally Posted by jukey
I would assume this would be built into some sort of grammar ... where and/or/not can be combined with predicates to create complex rules.
And of course a mix out of more than one predicate.
Also, the rules should be able to be prioritized, I think.
Good additions, though.
|
|
2010-04-20
, 19:59
|
|
Posts: 246 |
Thanked: 204 times |
Joined on Jun 2007
@ Potsdam (Germany)
|
#99
|
I made a little wiki page to collect the most relevant informations from this thread: http://wiki.maemo.org/Shepherd
At the moment there are included not the most relevant stuff but the latest stuff from this thread.
At the moment there are included not the most relevant stuff but the latest stuff from this thread.
__________________
|
|
2010-04-21
, 07:56
|
|
Posts: 3,319 |
Thanked: 5,610 times |
Joined on Aug 2008
@ Finland
|
#100
|
As for grammar, there is a very crude and/or/() mechanism, but the idea is to borrow a parser from Qt (XML or QtScript, haven't decided yet) so we can make more complex expressions without investing too much in writing our own parser.
__________________
Blogging about mobile linux - The Penguin Moves!
Maintainer of PyQt (see introduction and docs), AppWatch, QuickBrownFox, etc
Blogging about mobile linux - The Penguin Moves!
Maintainer of PyQt (see introduction and docs), AppWatch, QuickBrownFox, etc
| The Following User Says Thank You to attila77 For This Useful Post: | ||
 |
| Tags |
| cron, power save, scheduling, shepherd |
«
Previous Thread
|
Next Thread
»
|
All times are GMT. The time now is 16:07.
First, is such collaboration possible? And if it is, what is still unimplemented amongst the desired features?
Thanks.
Last edited by shvedsky; 2010-04-08 at 07:09.