Changes

Jump to navigation Jump to search
1,432 bytes removed ,  21:09, 28 July 2009
Line 17: Line 17:  
* export for offline viewing (Web page - HTML only, Web page - Complete)
 
* 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))
 
* 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
 
* 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
  −
** [[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) ===
 
=== More Accelerators (short cuts) ===
Line 105: Line 97:  
** Status: Complete
 
** 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 [[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 ===
 
=== Version support for datastore ===
 
See [[Version_support_for_datastore/Proposal]].
 
See [[Version_support_for_datastore/Proposal]].
 
* Owner/Coordinator: Silbe
 
* 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).
  −
  −
<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 ===
 
=== Security ===
Line 156: Line 120:  
* See [http://lists.sugarlabs.org/archive/sugar-devel/2009-April/013665.html]
 
* See [http://lists.sugarlabs.org/archive/sugar-devel/2009-April/013665.html]
   −
==== Bundles ====
+
=== misc requests ===
* [[Unified Bundles]] merge .xol bundles to .xo
+
 
 +
:'''<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."
 +
:'''<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

Navigation menu