[sugar] sugar roadmap

[Eben Eliason]

>  >  3. Need easy way to group links to activities, such as in a lesson
>  >  plan.
>  >
>  >  Use Case:
>  >  Kid reads through geometry tutorial and clicks on first activity which
>  >  opens up Dr. Geo. After finishing w/ Dr. Geo he does some more reading
>  >  in the tutorial and then clicks on a second link which opens up a
>  >  related GCompris activity.
>  >
>  >  We need a way to launch different activities from within a graphical
>  >  context, e.g. a tutorial. HTML is the most practical way to do this. I
>  >  know there are issues w/ Rainbow and activities calling other activities
>  >  but this is very important to the learning process.
>
>  Interesting, would like to know what Eben thinks about it.

This is an interesting idea, and one I don't really have a direct
solution for, at present.  One potential option, and perhaps the most
interesting, is also a fair bit of work.  It entails adding a bitfrost
permission (does it already have one?) akin to P_EXEC or something
similar, which allows an activity to make a request to the shell to
launch another activity, passing it a URI (could be a file, could be a
URL, etc) and having it ask the user to confirm the action.  With such
an approach, any activity that wanted could embed links to other
activities, or to web sites.  If we build this into the shell, and
offer it as a permission, I don't believe that it will pose any
security problems*.

* I could be very wrong, though.

>  >  7. Need graphical activity manager for removing and adding activities
>
>  Could you detail the requirements for this? Perhaps in the wiki?

This is a good point.  The activity list in Home is intended to take
care of this.  Tomeu, we should probably add little delete buttons at
the right of each entry in the list to make this a simple process.  A
non-modal alert should appear to confirm the deletion, of course.
This should be relatively easy to add.

- Eben