Features/Revised Browse default-bookmarks.html

From Sugar Labs
< Features
Revision as of 04:35, 9 June 2010 by Satellit (talk | contribs) (Features/Revised Browse default-bookmarks.html (e-books/Floss/SugarCreationKit links))
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Comments and Explanations:

  • Point Sugar.Browse default "start new" screen to:
  • instead of sugars's default:


Point the "start new" default Browse start-up page to the page that is downloaded from fedora repository.fedora-bookmarks-13-1.noarch.rpm 5.4 kB


  • Email: satellit@bendbroadband.com

Current status

  • Targeted release: V4
  • Last updated: (06/09/2010)
  • Percentage of completion: 0%

Detailed Description

Expand on the summary, if appropriate. A couple of sentences suffices to explain the goal, but the more details you can provide the better.

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?

Make sure to note here as well if this feature has been requested by a specific deployment, or if it has emerged from a bug report.


What work do the developers have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?

UI Design

Does the feature have a direct impact on the work flow, or does it need a UI? Link here mockups, or add detailed descriptions.

How To Test

In a terminal (the Terminal Activity works):

Move to the folder with the file for the default Browse homepage.

cd /usr/share/sugar/activities/Browse.activity/data

Back up your current Browse start page by renaming it to index.html.bak.

mv index.html index.html.bak

Download the sample index.html file from http://people.sugarlabs.org/Tgillard/Modified-Browse.html

wget http://url/to/index.html

Start the Browse Activity. It should open to a page of custom links, rather than the normal Browse start page. Try clicking on a few links. If they go to the webpages indicated, the feature is working.

To undo your testing and restore the previous Browse default start page, change the filenames back so that the old file is once again named index.html.

mv index.html modified-bookmarks.html
mv index.html.bak index.html

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.


What other packages (RPMs) depend on this package? Are there changes outside the developers' control on which completion of this feature depends? In other words, does your feature depend on completion of another feature owned by someone else or that you would need to coordinate, which might cause you to be unable to finish on time? Other upstream projects like Python?

Contingency Plan

If you cannot complete your feature by the final development freeze, what is the backup plan? This might be as simple as "None necessary, revert to previous release behaviour." Or it might not. If your feature is not completed in time, we want to assure others that other parts of Sugar will not be in jeopardy.


Is there upstream documentation on this feature, or notes you have written yourself? Has this topic been discussed in the mailing list or during a meeting? 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