Sugar TODO: Difference between revisions

From OLPC
Jump to navigation Jump to search
No edit summary
(Old old old old ooooooold page)
 
(38 intermediate revisions by 15 users not shown)
Line 1: Line 1:
{{Deprecated}}
= Frame =


=Sugar=
* Fix the white flashes sometimes appear in the corners (maybe because windows are now overlapping)? (marco)
* Set the frame canvases background to None so that we don't get white flashes. Need to figure out how we want to do this. Patch to hippo-canvas (optional) or tweak the canvas widget or use HippoWindow and tweak or our own Window. (marco)
* Frame animation if the perf is acceptable on the XO (marco)
* Fix positioning of the access point icons tooltips


* Implement object types system.
== Done ==
* Implement palette.
* Fix toolbox style when tabs are turned off.
* Move downloads to the notification area.


=Browser=
* Make sure the frame scale correctly on not 4:3 resolutions (ex 800x440). Once that works we can remove the screen sizing hacks in sugar-emulator.
* Finish up frame menu positioning
* Tooltips for the zoom icons and for the activity icons (just the activity name for now)
* When hovering a frame icon his background should become black (check for the exact color on the mockups)
* Feedback when hovering menu items
* Make Menu looks nice by adding some padding. Is the color right? It seem too light.
* Get rid of the horrible network manager icon, we should have device icon on the homepage and access points on the mesh view
* The overlay button is gone. Sometimes appear in the left-top corner, figure out what's going on.


* Resolve the gtkmozembed mess.
= Journal =
* Split out to his own package.
* Convenient DOM events API (based on pyxpcom).


=Datastore=
* Make the toolbar look nice. There are some strange artifacts on the option menu. We need padding and spacing between items.
* Fix style of the view, the colors are just wrong in particular.
* Buddy list for the detailed view
* Add the activity icon to both views.
* Add the star to both views.


* Basic ops < 0.1 sec
== Done ==
* Run tests from the makefiles


=Shell=
* Switch to detailed view on an entry click.
* Button with a label and an optional icon


* Fix and complete the mesh view layout manager.
= Activities =


=Clipboard=
* Update xbook toolbar

* Preview images in the rollover.

=Journal=

* Entries renaming.
* Startup the journal when clicking on the icon in the donut.
* Fix the toolbars UI mess.
* Filtering and fulltext search.
* Previews.

=Write=

* Autosave also by a timeout (now it saves on focus-out and on close).
* Fix the toolbars UI mess.

= Chat activity =
* Redesign to launch it from the mesh view

= Call activity =
* Redesign to launch it from the mesh view

= Connect 4=
* Clean up to use sugar's API as much as possible (instead of TP API) (smcv)

= Activity sharing =

== PS & Sugar ==

* write an easy API for tubes (smcv: in progress)
* make the PS use salut
* allow inviting without sharing (currently the PS only creates a MUC when you share)
* implement group sharing

== Gabble ==

* review tubes branches (Robot101)
* implement p2p tubes ([http://www.xmpp.org/extensions/xep-0066.html OOB] ?) (Cassidy)
* implement stream tubes (Cassidy)

== Salut ==
* sort out the authentication of our JIDs on the server with OLPC keys
* sign/verify salut presence adverts
* implement org.laptop.Telepathy.ActivityProperties
* implement tubes
* implement jingle calls

== Server side ==
* fix XMPP scalability issues with a server component
** keep a registry of activities so we can get the activity id and name from a central place
** revisit activity enumeration, so we can do "find me activities of type $foo", or "get me some activities to fill up the mesh view"
** revisit buddy enumeration, so we don't need the shared roster hack. it's possible that we should just find random people by finding random activities, and not worry about "get be some buddies to fill up the mesh view".
** provide a solution for mutual groups?


[[Category:Sugar]]
[[Category:Sugar]]

Latest revision as of 11:33, 4 April 2008

Stop hand.png WARNING:
The content of this section is considered
DEPRECATED and OBSOLETE
It is preserved for historical or documenting reasons.

Sugar

  • Implement object types system.
  • Implement palette.
  • Fix toolbox style when tabs are turned off.
  • Move downloads to the notification area.

Browser

  • Resolve the gtkmozembed mess.
  • Split out to his own package.
  • Convenient DOM events API (based on pyxpcom).

Datastore

  • Basic ops < 0.1 sec
  • Run tests from the makefiles

Shell

  • Fix and complete the mesh view layout manager.

Clipboard

  • Preview images in the rollover.

Journal

  • Entries renaming.
  • Startup the journal when clicking on the icon in the donut.
  • Fix the toolbars UI mess.
  • Filtering and fulltext search.
  • Previews.

Write

  • Autosave also by a timeout (now it saves on focus-out and on close).
  • Fix the toolbars UI mess.

Chat activity

  • Redesign to launch it from the mesh view

Call activity

  • Redesign to launch it from the mesh view

Connect 4

  • Clean up to use sugar's API as much as possible (instead of TP API) (smcv)

Activity sharing

PS & Sugar

  • write an easy API for tubes (smcv: in progress)
  • make the PS use salut
  • allow inviting without sharing (currently the PS only creates a MUC when you share)
  • implement group sharing

Gabble

  • review tubes branches (Robot101)
  • implement p2p tubes (OOB ?) (Cassidy)
  • implement stream tubes (Cassidy)

Salut

  • sort out the authentication of our JIDs on the server with OLPC keys
  • sign/verify salut presence adverts
  • implement org.laptop.Telepathy.ActivityProperties
  • implement tubes
  • implement jingle calls

Server side

  • fix XMPP scalability issues with a server component
    • keep a registry of activities so we can get the activity id and name from a central place
    • revisit activity enumeration, so we can do "find me activities of type $foo", or "get me some activities to fill up the mesh view"
    • revisit buddy enumeration, so we don't need the shared roster hack. it's possible that we should just find random people by finding random activities, and not worry about "get be some buddies to fill up the mesh view".
    • provide a solution for mutual groups?