Talk:0.86/Roadmap: Difference between revisions

(9 intermediate revisions by 4 users not shown)

Line 4:

''these are leftovers from the main page - please use the new feature process [[Features/Policy]] for those as well.''

==== On-disk icon cache ====

=== On-disk icon cache ===

Cache pre-rendered svg icons on disk.

Line 10:

* Owner/Coordinator: Benzea

==== Browse ====

=== Browse ===

* Lucian: SSB (Site specific browsing) - http://wiki.sugarlabs.org/go/Webified

* bookmarks (global bookmarks, at the moment we only have session bookmarks and the auto-completion functionality) - needed by SSB

Line 17:

* export for offline viewing (Web page - HTML only, Web page - Complete)

* creating of web pages (highlighting support in Write, Activity with special HTML based features(can happen outside of the official cycle))

* fix theme (scroll-bars [http://dev.sugarlabs.org/ticket/805 #805], html form widgets - Gary)

* fix theme (scroll-bars [http://dev.sugarlabs.org/ticket/805 #805], [http://dev.sugarlabs.org/ticket/1067 #1067], html form widgets - Gary)

* Owner/Coordinator: Simon

~~==== Journal ====~~

=== More Accelerators (short cuts) ===

* tag auto completion for already existing tags, tag clouds

** its implemented in Library activity as well

* Owner/Coordinator: Kartik Rustagi (widget from the tagging work in the mesh), attach it to Library?

* Mock-ups

** [[Design_Team/Designs/Journal|Previous action/object view Journal mock-ups]] from Eben

** [[Design_Team/Proposals/Journal|Journal toolbar & palette change mock-ups]] for discussion from Gary

==== More Accelerators (short cuts) ====

* make sure we use the standard accelerator UI where possible for existing bindings, get discussion about which modifiers might be worth changing/adding/removing

* [[Design_Team/Proposals/Keyboard_Action]]

* Owner/Coordinator: Homunq?

==== Printing support ====

=== Printing support ===

* [http://wiki.sugarlabs.org/go/Print_Support Google summer of code project]

* Owner/Coordinator: IwikiwI

==== Search in home view ====

=== Search in home view ===

* The search is recently builds disabled

* Owner/Coordinator: ?

==== Collaboration ====

=== Collaboration ===

* Scalable presence service - Integrate gadget in the Sugar UI [http://dev.laptop.org/ticket/7711 #7711]

* Make collaboration more stable

* Owner/Coordinator: Tomeu/Simon

==== Groups ====

=== Groups ===

* Tagging buddies to build up relations, tagging can happen by a teacher tagging a class or the learner can tag himself

* Owner/Coordinator: Kartik Rustagi

* [[Tagging_Proposal|Proposal]]

==== Bindings ====

=== Bindings ===

* [http://live.gnome.org/Vala/Bindings Vala bindings] for the toolkit

** (?) we could write [[#Decoupling of Sucrose]]/'''bridge''' level on vala i.e. use for '''core''' only dbus API and provide bride level in vala binding [[User:Alsroot|Alsroot]] 06:15, 25 May 2009 (UTC)

* Owner/Coordinator: Tomeu

~~==== Keyboard control panel extension ====~~

=== Dictionary support in the shell ===

* (Sayamindu would prefer to keep it as a separate module, since everyone may not choose to go with XKB)

* Owner/Coordinator: Sayamindu

==== Dictionary support in the shell ====

* [http://lists.sugarlabs.org/archive/sugar-devel/2009-May/014217.html Dictionary Proposal]

* Owner/Coordinator: Sayamindu

==== CP - Language in native language ====

=== CP - Language in native language ===

* link to ticket here

* Owner/Coordinator: Sayamindu

==== TA ====

=== TA ===

* de-couple the portfolio from the base TA

* revive TA with Sensors (requires revisiting RPM issues re multiple architectures)

* Owner/Coordinator: Walter

==== Honey ====

=== Honey ===

* repackage Measure

:: Owner/Coordinator: ???

Line 81:

Line 69:

:: Owner/Coordinator: ???

==== Activities external to Sugar ====

=== Activities external to Sugar ===

launch activities outside of Sugar

:: Owner/Coordinator: ???

==== integration with new Collabora code ====

=== integration with new Collabora code ===

==== on-the-fly i18n support ====

=== on-the-fly i18n support ===

Let users translate strings and push them back to Pootle

* as per C Scott's demo from Sugar Camp 2008-11

:: Owner/Coordinator: ???

~~==== Library activity ====~~

* [[Activities/Library | Library Activity Proposal]]

* in honey

* maybe we want a pluggable Views(Home/Journal) to ease the use of such kinds of activities(activities that can browse sugar objects)

** another option - add autostart activities

* Owner/Coordinator: Alsroot

=== Read Activity ===

Line 117:

Line 98:

~~==== API work ====~~

=== Version support for datastore ===

* backwards compability

* (http://wiki.sugarlabs.org/go/Development_Team/sugar-port will take care for the activities needs for a working activity on 0.82 for example) see "Decoupling of Sucrose" section [[User:Alsroot|Alsroot]] 16:16, 21 May 2009 (UTC)

* (?) start moving to pure dbus interface for glucose

** dbus method to resume/open activities(instead of sugar-toolkit API)

*** something simple like dbus_object.activate(uid) or

** etc.

* Owner/Coordinator: Aleksey

==== Version support for datastore ====

See [[Version_support_for_datastore/Proposal]].

* Owner/Coordinator: Silbe

~~==== Datastore features that could benefit Library ====~~

=== Security ===

These features can benefit [[Activities/Library]] activity. At present(for 0.82/0.84) Library uses "rich" datastore client which fetches all Journal objects to make short list of objects(by collapsing all versions to one item), moreover it has to unzip .xo bundles to get ''bundle_id'' value. So its not good.

With all these features implemented Library can use "thin" datastore client and not fetch all objects, just make proper request for datasotre.find() to get sorted and collapsed objects by portions (by using offset/limit find() arguments).

~~find() returns only last versions of journal objects~~

~~So, all objects should be grouped by "object_id" which could be:~~

* ''activity_id'' for objects that were generated by activities

* ''bundle_id'' for .xo bundles in the Journal

* ''uid'' for other objecets

~~Sort find()'s resultset~~

~~Let datastore clients sort objects by any field(not only predefined like uid, activity_id etc).~~

* Sort by buddies count

* Owner/Coordinator: ?

==== Security ====

[http://dev.sugarlabs.org/ticket/593 Add support] for the current version of [http://wiki.laptop.org/go/Rainbow Rainbow] so

# security flaws in Browse (which are the norm rather than the exception) don't allow an attacker to take over the machine and

Line 155:

Line 108:

* Owner/Coordinator: ?

==== Testing ====

=== Testing ===

Add some automated testing to catch bugs earlier and ease integration work:

* [http://dev.sugarlabs.org/ticket/594 SugarBot] (activity-level testing)

Line 161:

Line 114:

* [http://dev.sugarlabs.org/ticket/595 regression tests]

* Owner/Coordinator: ?

~~==== Activities updates ====~~

~~Let users update theirs activities.~~

~~There could be several options:~~

* Use XO's mechanism to have update item in control panel(pretty common choice)

** we will have specific option - update only activities

* Follow [[Unified Objects]] paradigm, one of implementation of this idea is [[Activities/Library]], so give user more freedom in upgrading procedure(i.e. w/o ceilings) - incorporate updating procedure into browsing tool(like Journal, Library), so users get one unified method to browse and update(sync) theirs objects(not only activities).

** in case of [[Activities/Library]] we could have 0.82+ upgrading tool

~~Owner/Coordinator: ?~~

=== Old items ===

Line 179:

Line 120:

* See [http://lists.sugarlabs.org/archive/sugar-devel/2009-April/013665.html]

==== ~~Bundles~~ ====

=== misc requests ===

* [[Unified Bundles]] merge .xol bundles to .xo

~~== Proposed modules ==~~

:'''<m_stone>''' walterbender: anyway, the consistent feedback was "more games, don't lose our files, let us find our files even when we have lots of them, make USB sticks easier to work with, and pick protocols that don't melt the network."

''~~nothing proposed yet~~''

:'''<m_stone>''' followed quickly by "give us a good way to distribute books to laptops, HTML+Javascript activities, easier translation, easier build customization [specifically RPM installation]"

:'''<m_stone>''' oh, the other necessary component is that installing the update should not require touching every machinel

@@ Line 4: / Line 4: @@
 ''these are leftovers from the main page - please use the new feature process [[Features/Policy]] for those as well.''
-==== On-disk icon cache ====
+=== On-disk icon cache ===
 Cache pre-rendered svg icons on disk.
@@ Line 10: / Line 10: @@
 * Owner/Coordinator: Benzea
-==== Browse ====
+=== Browse ===
 * Lucian: SSB (Site specific browsing) - http://wiki.sugarlabs.org/go/Webified
 * bookmarks (global bookmarks, at the moment we only have session bookmarks and the auto-completion functionality) - needed by SSB
@@ Line 17: / Line 17: @@
 * export for offline viewing (Web page - HTML only, Web page - Complete)
 * creating of web pages (highlighting support in Write, Activity with special HTML based features(can happen outside of the official cycle))
-* fix theme (scroll-bars [http://dev.sugarlabs.org/ticket/805 #805], html form widgets - Gary)
+* fix theme (scroll-bars [http://dev.sugarlabs.org/ticket/805 #805], [http://dev.sugarlabs.org/ticket/1067 #1067], html form widgets - Gary)
 * Owner/Coordinator: Simon
-==== Journal ====
+=== More Accelerators (short cuts) ===
-* tag auto completion for already existing tags, tag clouds
-** its implemented in Library activity as well
-* Owner/Coordinator: Kartik Rustagi (widget from the tagging work in the mesh), attach it to Library?
-* Mock-ups
-** [[Design_Team/Designs/Journal|Previous action/object view Journal mock-ups]] from Eben
-** [[Design_Team/Proposals/Journal|Journal toolbar & palette change mock-ups]] for discussion from Gary
-==== More Accelerators (short cuts) ====
 * make sure we use the standard accelerator UI where possible for existing bindings, get discussion about which modifiers might be worth changing/adding/removing
 * [[Design_Team/Proposals/Keyboard_Action]]
 * Owner/Coordinator: Homunq?
-==== Printing support ====
+=== Printing support ===
 * [http://wiki.sugarlabs.org/go/Print_Support Google summer of code project]
 * Owner/Coordinator: IwikiwI
-==== Search in home view ====
+=== Search in home view ===
 * The search is recently builds disabled
 * Owner/Coordinator: ?
-==== Collaboration ====
+=== Collaboration ===
 * Scalable presence service - Integrate gadget in the Sugar UI [http://dev.laptop.org/ticket/7711 #7711]
 * Make collaboration more stable
 * Owner/Coordinator: Tomeu/Simon
-==== Groups ====
+=== Groups ===
 * Tagging buddies to build up relations, tagging can happen by a teacher tagging a class or the learner can tag himself
 * Owner/Coordinator: Kartik Rustagi
 * [[Tagging_Proposal|Proposal]]
-==== Bindings ====
+=== Bindings ===
 * [http://live.gnome.org/Vala/Bindings Vala bindings] for the toolkit
 ** (?) we could write [[#Decoupling of Sucrose]]/'''bridge''' level on vala i.e. use for '''core''' only dbus API and provide bride level in vala binding [[User:Alsroot|Alsroot]] 06:15, 25 May 2009 (UTC)
 * Owner/Coordinator: Tomeu
-==== Keyboard control panel extension ====
+=== Dictionary support in the shell ===
-* (Sayamindu would prefer to keep it as a separate module, since everyone may not choose to go with XKB)
-* Owner/Coordinator: Sayamindu
-==== Dictionary support in the shell ====
 * [http://lists.sugarlabs.org/archive/sugar-devel/2009-May/014217.html Dictionary Proposal]
 * Owner/Coordinator: Sayamindu
-==== CP - Language in native language ====
+=== CP - Language in native language ===
 * link to ticket here
 * Owner/Coordinator: Sayamindu
-==== TA ====
+=== TA ===
 * de-couple the portfolio from the base TA
 * revive TA with Sensors (requires revisiting RPM issues re multiple architectures)
 * Owner/Coordinator: Walter
-==== Honey ====
+=== Honey ===
 * repackage Measure
 :: Owner/Coordinator: ???
@@ Line 81: / Line 69: @@
 :: Owner/Coordinator: ???
-==== Activities external to Sugar ====
+=== Activities external to Sugar ===
 launch activities outside of Sugar
 :: Owner/Coordinator: ???
-==== integration with new Collabora code ====
+=== integration with new Collabora code ===
-==== on-the-fly i18n support ====
+=== on-the-fly i18n support ===
 Let users translate strings and push them back to Pootle
 * as per C Scott's demo from Sugar Camp 2008-11
 :: Owner/Coordinator: ???
-==== Library activity ====
-* [[Activities/Library | Library Activity Proposal]]
-* in honey
-* maybe we want a pluggable Views(Home/Journal) to ease the use of such kinds of activities(activities that can browse sugar objects)
-** another option - add autostart activities
-* Owner/Coordinator: Alsroot
 === Read Activity ===
@@ Line 117: / Line 98: @@
-==== API work ====
+=== Version support for datastore ===
-* backwards compability
-* (http://wiki.sugarlabs.org/go/Development_Team/sugar-port will take care for the activities needs for a working activity on 0.82 for example) see "Decoupling of Sucrose" section [[User:Alsroot|Alsroot]] 16:16, 21 May 2009 (UTC)
-* (?) start moving to pure dbus interface for glucose
-** dbus method to resume/open activities(instead of sugar-toolkit API)
-*** something simple like dbus_object.activate(uid) or
-** etc.
-* Owner/Coordinator: Aleksey
-==== Version support for datastore ====
 See [[Version_support_for_datastore/Proposal]].
 * Owner/Coordinator: Silbe
-==== Datastore features that could benefit Library ====
+=== Security ===
-These features can benefit [[Activities/Library]] activity. At present(for 0.82/0.84) Library uses "rich" datastore client which fetches all Journal objects to make short list of objects(by collapsing all versions to one item), moreover it has to unzip .xo bundles to get ''bundle_id'' value. So its not good.
-With all these features implemented Library can use "thin" datastore client and not fetch all objects, just make proper request for datasotre.find() to get sorted and collapsed objects by portions (by using offset/limit find() arguments).
-<strong>find() returns only last versions of journal objects</strong>
-So, all objects should be grouped by "object_id" which could be:
-* ''activity_id'' for objects that were generated by activities
-* ''bundle_id'' for .xo bundles in the Journal
-* ''uid'' for other objecets
-<strong>Sort find()'s resultset</strong>
-Let datastore clients sort objects by any field(not only predefined like uid, activity_id etc).
-* Sort by buddies count</strong>
-* Owner/Coordinator: ?
-==== Security ====
 [http://dev.sugarlabs.org/ticket/593 Add support] for the current version of [http://wiki.laptop.org/go/Rainbow Rainbow] so
 # security flaws in Browse (which are the norm rather than the exception) don't allow an attacker to take over the machine and
@@ Line 155: / Line 108: @@
 * Owner/Coordinator: ?
-==== Testing ====
+=== Testing ===
 Add some automated testing to catch bugs earlier and ease integration work:
 * [http://dev.sugarlabs.org/ticket/594 SugarBot] (activity-level testing)
@@ Line 161: / Line 114: @@
 * [http://dev.sugarlabs.org/ticket/595 regression tests]
 * Owner/Coordinator: ?
-==== Activities updates ====
-Let users update theirs activities.
-There could be several options:
-* Use XO's mechanism to have update item in control panel(pretty common choice)
-** we will have specific option - update only activities
-* Follow [[Unified Objects]] paradigm, one of implementation of this idea is [[Activities/Library]], so give user more freedom in upgrading procedure(i.e. w/o ceilings) - incorporate updating procedure into browsing tool(like Journal, Library), so users get one unified method to browse and update(sync) theirs objects(not only activities).
-** in case of [[Activities/Library]] we could have 0.82+ upgrading tool
-Owner/Coordinator: ?
 === Old items ===
@@ Line 179: / Line 120: @@
 * See [http://lists.sugarlabs.org/archive/sugar-devel/2009-April/013665.html]
-==== Bundles ====
+=== misc requests ===
-* [[Unified Bundles]] merge .xol bundles to .xo
-== Proposed modules ==
+:'''<m_stone>'''	walterbender: anyway, the consistent feedback was "more games, don't lose our files, let us find our files even when we have lots of them, make USB sticks easier to work with, and pick protocols that don't melt the network."
-''nothing proposed yet''
+:'''<m_stone>'''	followed quickly by "give us a good way to distribute books to laptops, HTML+Javascript activities, easier translation, easier build customization [specifically RPM installation]"
+:'''<m_stone>'''	oh, the other necessary component is that installing the update should not require touching every machinel