Sugar TODO

Clipboard

• 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.

Done

• 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).

Journal activity

• Entries renaming.
• Startup the journal when clicking on the icon in the donut.

Shell

• Let activities rename their journal entry title by an entry in the activity rollover

Abiword

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

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

• 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
• 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 ?)
• implement stream tubes

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?