Features/Revised Browse default-bookmarks.html
Comments and Explanations:
- Point Sugar.Browse default "start new" screen to:
file:///usr/share/bookmarks/default-bookmarks.html
- "We'll use something slightly different so we don't conflict." pbrobinson
- instead of sugars's default:
file:///usr/share/sugar/activities/Browse.activity/data/index.html
Summary
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
Owner
- Name: Tom Gilliard
- Email: satellit@bendbroadband.com
Current status
- Targeted release: SoaS_v4_Feature
- Last updated: (06/09/2010)
- Percentage of completion: 0%
Detailed Description
In a discussion with Peter Robinson last night I discovered that a custom Browse bookmark can be downloaded from the fedora repository. I propose to use this "Feature" to allow a custom set of bookmarts to be maintained that would have a series of links ie: e-books; Floss Manuals; wiki.sugarlabs.org, (maybe all of the proposed links to files in SugarCreationKit DVD)+ The NormalBrowse Google Screen
- This should be a simple edit in Browse to point to file:///usr/share/bookmarks/default-bookmarks.html instead of file:///usr/share/sugar/activities/Browse.activity/data/index.html.
- Repointing the default-screen allows us to have fedora supply our revised "Start New" screen ( or maybe several depending on the deployment or schools requirements to Soas v4)
Benefit to Sugar
A simple enhancement to sugar.browse
Scope
Edit the Browse activity
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.
Dependencies
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
Alternate path: edit /usr/share/sugar/activities/Browse.activity/data/index.html. This would allow sugarlabs to maintain the list.
- the Browse.xo on ASLO would also need to be changed
- > In this case: the Browse.xo on ASLO would also need to be changed as
> > installed activities seem to be stored in a different location than .xo > > files -(I think)
Nope. This will only be changed in the Browse shipped with SoaS. While ASLO is a resource for SoaS users what resides there is a generic resource used by many.
Documentation
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.