Talk:0.86/Roadmap
Ideas
these are leftovers from the main page - please use the new feature process Features/Policy for those as well.
On-disk icon cache
Cache pre-rendered svg icons on disk.
- Owner/Coordinator: Benzea
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
- better naming of files to be uploaded #901(change temp name to something based on the title)
- uploading (above) is also dependent on filenames being preserved on download #899
- 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 #805, html form widgets - Gary)
- Owner/Coordinator: Simon
Journal
- 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
- Previous action/object view Journal mock-ups from Eben
- 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
- Google summer of code project
- Owner/Coordinator: IwikiwI
Search in home view
- The search is recently builds disabled
- Owner/Coordinator: ?
Collaboration
- Scalable presence service - Integrate gadget in the Sugar UI #7711
- Make collaboration more stable
- Owner/Coordinator: Tomeu/Simon
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
- Proposal
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 Alsroot 06:15, 25 May 2009 (UTC)
- Owner/Coordinator: Tomeu
Dictionary support in the shell
- Dictionary Proposal
- Owner/Coordinator: Sayamindu
CP - Language in native language
- link to ticket here
- Owner/Coordinator: Sayamindu
TA
- de-couple the portfolio from the base TA
- revive TA with Sensors (requires revisiting RPM issues re multiple architectures)
- Owner/Coordinator: Walter
Honey
- repackage Measure
- Owner/Coordinator: ???
- add Open Office for Children
- Owner/Coordinator: ???
- add a video editing activity
- Owner/Coordinator: ???
Activities external to Sugar
launch activities outside of Sugar
- Owner/Coordinator: ???
integration with new Collabora code
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
- 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
- Bookmarks support
- Owner: Sayamindu
- Status: 75% complete (bookmarks work - support adding notes to them is pending)
- Epub Support
- Owner: Sayamindu
- Status: 80% complete (Epub files are fully viewable. Changes to webkit needs to be upstreamed)
- Long keypress support
- Owner: Sayamindu
- Status: 50% complete (proof of concept code ready, needs integration into Read codebase, and one patch for Xlib needs to go upstream)
ImageViewer Activity
- Image sharing support (as in Read)
- Owner: Sayamindu
- Status: Complete
API work
- 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 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.
- dbus method to resume/open activities(instead of sugar-toolkit API)
- Owner/Coordinator: Aleksey
Version support for datastore
See Version_support_for_datastore/Proposal.
- Owner/Coordinator: Silbe
Datastore features that could benefit Library
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
Add support for the current version of 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
- programming mistakes cannot affect other activities (like deleting all Journal contents).
- Owner/Coordinator: ?
Testing
Add some automated testing to catch bugs earlier and ease integration work:
- SugarBot (activity-level testing)
- some system-level tests (e.g. verify datastore works correctly)
- 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
Accessibility
- See [1]
Bundles
- Unified Bundles merge .xol bundles to .xo