5,705
edits
Changes
Jump to navigation
Jump to search
User:Alsroot/trash/Object Bundles (view source)
Revision as of 23:55, 20 July 2009
, 23:55, 20 July 2009Created page with '<noinclude>{{GoogleTrans-en}}{{TOCright}}</noinclude> <!-- All fields on this form are required to be accepted. We also request that you maintain the same order of sections so …'
<noinclude>{{GoogleTrans-en}}{{TOCright}}</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 ==
Package Journal objects to bundles to preserve all sugar related metada.
== Owner ==
* Name: [[User:alsroot| Aleksey Lim]]
* Email: [[Special:Emailuser/alsroot|send an email]]
== Current status ==
* Targeted release: 0.86
* Last updated: Tue Jul 21 02:18:17 UTC 2009
* Percentage of completion: 0%
== Detailed Description ==
* Fix issues related to name mangling of Journal objects after uploading/downloading
* Keep objects DS metadata while transfering between user-server-user
** we can package DS object to bundles (it relates to [[Unified Bundles]])
== Benefit to Sugar ==
Let users export/import Journal objects.
== Scope ==
* shell code
* use object bundles for input fields in Browse
== How To Test ==
# Create a new TurtleArt activity
# Upload the new entry to the SL wiki using Browse
# Use Browse to download the entry back to Journal
# Resume it from Journal
== 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.''
== Dependencies ==
Fructose dependencies.
== Contingency Plan ==
None necessary, revert to previous release behaviour.
== Documentation ==
''Is there upstream documentation on this feature, or notes you have written yourself? Link to that material here so other interested developers can get involved.''
== Release Notes ==
''The Sugar Release Notes inform end-users about what is new in the release. An Example is [[0.84/Notes]]. The release notes also help users know how to deal with platform changes such as ABIs/APIs, configuration or data file formats, or upgrade concerns. If there are any such changes involved in this feature, indicate them here. You can also link to upstream documentation if it satisfies this need. This information forms the basis of the release notes edited by the release team and shipped with the release.''
== Comments and Discussion ==
* See [[{{TALKPAGENAME}}|discussion tab for this feature]] <!-- This adds a link to the "discussion" tab associated with your page. This provides the ability to have ongoing comments or conversation without bogging down the main feature page -->
[[Category:Feature Page Incomplete]]
[[Category:Feature]]
<!-- 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 ==
Package Journal objects to bundles to preserve all sugar related metada.
== Owner ==
* Name: [[User:alsroot| Aleksey Lim]]
* Email: [[Special:Emailuser/alsroot|send an email]]
== Current status ==
* Targeted release: 0.86
* Last updated: Tue Jul 21 02:18:17 UTC 2009
* Percentage of completion: 0%
== Detailed Description ==
* Fix issues related to name mangling of Journal objects after uploading/downloading
* Keep objects DS metadata while transfering between user-server-user
** we can package DS object to bundles (it relates to [[Unified Bundles]])
== Benefit to Sugar ==
Let users export/import Journal objects.
== Scope ==
* shell code
* use object bundles for input fields in Browse
== How To Test ==
# Create a new TurtleArt activity
# Upload the new entry to the SL wiki using Browse
# Use Browse to download the entry back to Journal
# Resume it from Journal
== 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.''
== Dependencies ==
Fructose dependencies.
== Contingency Plan ==
None necessary, revert to previous release behaviour.
== Documentation ==
''Is there upstream documentation on this feature, or notes you have written yourself? Link to that material here so other interested developers can get involved.''
== Release Notes ==
''The Sugar Release Notes inform end-users about what is new in the release. An Example is [[0.84/Notes]]. The release notes also help users know how to deal with platform changes such as ABIs/APIs, configuration or data file formats, or upgrade concerns. If there are any such changes involved in this feature, indicate them here. You can also link to upstream documentation if it satisfies this need. This information forms the basis of the release notes edited by the release team and shipped with the release.''
== Comments and Discussion ==
* See [[{{TALKPAGENAME}}|discussion tab for this feature]] <!-- This adds a link to the "discussion" tab associated with your page. This provides the ability to have ongoing comments or conversation without bogging down the main feature page -->
[[Category:Feature Page Incomplete]]
[[Category:Feature]]