View Single Post
Posts: 3,319 | Thanked: 5,610 times | Joined on Aug 2008 @ Finland
#94
Originally Posted by shvedsky View Post
So the proposal to improve shepherd should look as good as possible in the eyes of mentors.
Well, likely I'd be that mentor (already talked about it with vdvsx, our GSoC coordinator).

[*]A nice, non-geeky GUI in Qt - GUI currently is very basic
Technically, there *is* no GUI currently 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
More like stabilization to be interesting to 3rd party developers (not much fun in developing for a moving API).

[*]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
Correct (except for the buttons, we don't have those yet , 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

Last edited by attila77; 2010-04-09 at 10:58.
 

The Following 2 Users Say Thank You to attila77 For This Useful Post: