Sugar TODO: Difference between revisions

From OLPC
Jump to navigation Jump to search
(→‎Server side: stuff the component should do)
(Old old old old ooooooold page)
 
(15 intermediate revisions by 8 users not shown)
Line 1: Line 1:
{{Deprecated}}
=Clipboard=


=Sugar=
* When dragging with the frame hidden you need to move the mouse a bit to be able to paste. Fix this.
* Make drag of images from mozilla work.
* Make drag of images to abi work.
* Preview images in the rollover.
* Copy new files to ~/Journal and name them from their title.
* For objects the data of which is on disk, offer the text/uri-list target.


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


=Browser=
* Briefly pop in and out the frame when a download is initiated or a copy or cut happens.
* Make pasting from the clipboard works as specified (one object is selected at one time, and the user can change it by clicking on another object).


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


=Datastore=
=Journal activity=

* Entries renaming.
* Basic ops < 0.1 sec
* Startup the journal when clicking on the icon in the donut.
* Run tests from the makefiles


=Shell=
=Shell=
* Let activities rename their journal entry title by an entry in the activity rollover


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


=Clipboard=
* Autosave also by a timeout (now it saves on focus-out and on close).
* Undo and Redo.


* Preview images in the rollover.
[[Category:Sugar]]

[[Category:Developers]]
=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 =
= Chat activity =
Line 42: Line 53:
== PS & Sugar ==
== PS & Sugar ==


* write an easy API for tubes (smcv: in progress)
* make PS issue invitations (cassidy)
* make Sugar display invitations (cassidy)
* make call activity work on XO images
* make connect activity work on XO images
* write an easy API for tubes (smcv)
** blocked by design discussion
* make the PS use salut
* make the PS use salut
* allow inviting without sharing (currently the PS only creates a MUC when you share)
* allow inviting without sharing (currently the PS only creates a MUC when you share)
Line 55: Line 61:


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


== Salut ==
== Salut ==
Line 66: Line 72:


== Server side ==
== Server side ==
* fix XMPP scalabity issues (server component?)
* 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
** 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 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".
** 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?
** provide a solution for mutual groups?

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

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?