Sugar Labs

User:Alsroot/trash/Activity as a regular Journal Object: Difference between revisions

← Older edit
Godiard (talk | contribs)
628 edits
No edit summary
 
(17 intermediate revisions by 4 users not shown)
Line 1: Line 1:
<noinclude>{{GoogleTrans-en}}{{TOCright}}</noinclude>
<noinclude>{{GoogleTrans-en}}{{TOCright}}
 
[[Category:FeatureObsoleted|Activity as a regular Journal Object]]</noinclude>
<!-- All fields on this form are required to be accepted.
We also request that you maintain the same order of sections so that all of the feature pages are uniform.  -->
 
<!-- The actual name of your feature page should look something like: Features/Your Feature Name.  This keeps all features in the same namespace -->


== Summary ==
== Summary ==
Line 17: Line 13:
== Current status ==
== Current status ==


* Targeted release: ?
* Targeted release: 0.88
* Last updated: Tue Jul 28 04:32:53 UTC 2009
* Last updated: Fri Nov 27 21:28:31 UTC 2009
* Percentage of completion: 0%
* Percentage of completion: 0%


Line 41: Line 37:
== Benefit to Sugar ==
== Benefit to Sugar ==


''What is the benefit to the platform?  If this is a major capability update, what has changed?  If this is a new feature, what capabilities does it bring? Why will Sugar become a better platform or project because of this feature?''
* feature eliminates confusion, e.g. in case of removing activities, when there are activities(in Home view) and .xo bundles in the Journal(that could be absent - .xo deleted, system activity)
* let users, that are not experienced in command line applications, copy existed activity(even system) just by draging Journal(or Home) entry to USB source
* since all activities have Journal representation, keep useful information in entry fields(time of installing activity, additional info in description etc.)
* so, it simplifies situation - user all time has in mind that he is working with the same object(activity) but from different views(Home or Journal)


== Scope ==
== Scope ==


* depends on [[Features/Object Bundles]]
* sugar
* rework activity registry code in sugar
* migrate Home view to Journal code base
* code to auto-load proper activity version(while joining) if it doesn't exist


== UI Design ==
== UI Design ==
Line 67: Line 63:


== User Experience ==
== User Experience ==
''If this feature is noticeable by its target audience, how will their experiences change as a result?  Describe what they will see or notice.''
 
* there is strong linkage between activities in Home view and Journal entries, in fact Home view is just a predefined view [[Features/Journal Plugins|plugin]] to browse activity Journal objects
* user can operate with system activities or activities woth removed .xo bundles(in existed workflow) from Journal, e.g. copy them to USB stick


== Dependencies ==
== Dependencies ==
Line 82: Line 80:
* [[Features/Object Bundles]]
* [[Features/Object Bundles]]
* Email threads
* Email threads
** [http://www.mail-archive.com/sugar-devel@lists.sugarlabs.org/msg10708.html Activity as a regular Journal Object request for inclusion to 0.88]
** [http://www.mail-archive.com/sugar-devel@lists.sugarlabs.org/msg07572.html multiple activity versions installed simultaneously]
** [http://www.mail-archive.com/sugar-devel@lists.sugarlabs.org/msg07572.html multiple activity versions installed simultaneously]
** [http://www.mail-archive.com/sugar-devel@lists.sugarlabs.org/msg06944.html Activity as regular objects proposal]
** [http://www.mail-archive.com/sugar-devel@lists.sugarlabs.org/msg06944.html Activity as regular objects proposal]
Retrieved from "https://wiki.sugarlabs.org/go/User:Alsroot/trash/Activity_as_a_regular_Journal_Object"