Difference between revisions of "Features/Revised Browse default-bookmarks.html"

From Sugar Labs
Jump to navigation Jump to search
 
(52 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 
<noinclude>
 
<noinclude>
[[Category:Feature Page Incomplete]]
+
[[Category:FeatureLanded|Revised Browse default bookmarks]]
[[Category:Feature|<Feature Name>]]
 
  
 
<!-- You can add categories to tie features back to real deployments/schools requesting them, for example  
 
<!-- You can add categories to tie features back to real deployments/schools requesting them, for example  
 
[[Category:Features requested by School Xyz|<Feature Name>]] (the |Feature Name option sorts the entry on the category page under the first letter of <Feature Name>). -->
 
[[Category:Features requested by School Xyz|<Feature Name>]] (the |Feature Name option sorts the entry on the category page under the first letter of <Feature Name>). -->
 
</noinclude>
 
</noinclude>
 
'''Comments and Explanations:'''
 
 
 
  
  
Line 19: Line 14:
 
== Summary ==
 
== Summary ==
 
What I am trying to Achieve:
 
What I am trying to Achieve:
: '''An enhanced "start new" screen for sugar.browse.''' It should have added customizable links and Graphic Elements Suitable for '''Soas-v4 -Mangolassi'''  
+
: '''An enhanced "start new" screen for sugar.browse in the fedora.spin-soas v4.''' It should have a added customizable link and possibly Graphic Elements Suitable for '''SoaS v4 Mango Lassi'''  
  
 
===Ideas from Soas #sugar-meeting: 06/14/2010===
 
===Ideas from Soas #sugar-meeting: 06/14/2010===
*Idea Crystalization credits to mchua:, mtd and others.
+
*Idea Crystallization credits to mchua:, mtd and others.
 +
* This is the second idea we discussed
  
Case 1) improve the default browse page with a few well documented links that upstream agrees with
+
'''Proposed custom default page for SoaS v4 Mango Lassi'''
  
* suggested links:
+
:: '''Summary: add new link 'Introduction:-Mango Lassi' inserted to the left of the existing 5 links.'''
+
:::The Use of a customized introduction page on the wiki is a part of this proposal.
: Use exiting 4 links
+
'''List of proposed links (left to right)'''
:: Home
+
# '''Introduction:-Mango Lassi'''
::Wiki
+
::Link to Custom wiki page
::Bugs
+
::Special page on wiki with Needed Materials for using Soas-v4-Mango Lassi
::Activites
+
:::This is a way for teachers and users to access information from the wiki and other pertinent web sites.
:: Link to Live DVD page -  
+
::: Uses this link: http://wiki.sugarlabs.org/go/Talk:Sugar_Creation_Kit#Introduction_to_Soas-v3_Mirabelle - This will change for v-4 '''THIS IS A SAMPLE ONLY'''
:::This is a separate way for teachers and users to access information from the wiki and other pertinent web sites. It consists all of the links and the same Structure as the SugarCreationKit DVD
+
# '''Home'''
:: existing Google search
+
# '''Wiki'''
 +
# '''Bugs'''
 +
# '''Activities'''
 +
# '''Google search'''
  
Case 2) we do a custom default page that accomplishes the same but specifically for SoaS-v4 -Mangolassi
 
: Custom Artwork
 
: Custom links added later
 
  
 +
======'''NOTES:'''======
 +
*06/21/2010 soas meeting:
 +
* Make ASLOxo a separate Proposal
 +
* pbrobinson likes destination page now for Intro to Mirabelle
 +
* Must go into GIT for testing
 +
* In Git: http://git.sugarlabs.org/projects/browse/repos/satellits_clone_browse_homepage/logs/master
 +
* Accepted in #sugar-meeting 07/05/2010
 +
:http://me.etin.gs/sugar-meeting/sugar-meeting.log.20100705_1502.html
 +
--------------------------
  
3-) Maybe we should consider BOTH  solutions as features
+
======older Comments======
: Soas-v4 -Mangolassi Only
 
: Sugar f14 as distributed from the fedora repositories
 
 
 
NOTES:
 
 
 
 
* mtd: a customizable start page exists.
 
* mtd: a customizable start page exists.
  
Line 69: Line 69:
 
== Current status ==
 
== Current status ==
 
* Targeted release: SoaS_v4_Feature
 
* Targeted release: SoaS_v4_Feature
* Last updated: (06/12/2010)
+
* Last updated: (07/05/2010)
* Percentage of completion: 90%
+
* Percentage of completion: 100%
 
+
: Need to make git account and do edits so a diff can be created (mchua 06/16/2010)
* http://wiki.sugarlabs.org/go/Sugar_Creation_Kit#AN_ON-LINE_VERSION_OF_THE_DVD_: added links in anticipation of conversion to bookmarks.html write (06/11/2010)
+
* DONE: In Git http://git.sugarlabs.org/projects/browse/repos/satellits_clone_browse_homepage/logs/master (satellit 06/24/2010)
 
+
* Meeting Log 07/05/2010:
'''History of TESTING'''
+
  [15:29:57] <mchua> #agreed Browse start page feature accepted - mchua is the feature sponsor
* Tested on sugar-emulator in f12 (file locations and names may be different in Soas)
+
  [15:30:17]
* copied file:///usr/share/bookmarks/default-bookmarks.html to desktop,
+
  [15:30:40] <mchua> #info Implementation: genericize patch, push to upstream Browse, edit wiki pages it links to - use this as an example of the feature process, as it's simple but an obvious change
* opened and edited with OooWriter
+
[15:30:51]
* added hyperlinks and saved
+
  [15:31:01] <mchua> hm, "clearly visible and easily to understand" is probably better than "obvious" but anyway...
* renamed index.html
+
[15:31:24] <mchua> satellit__: so go ahead and move it to the "accepted" section of the features list, and let me know when you're going to be in Portland and we'll sit down and work on it then.
* opened terminal
 
su
 
gedit
 
*opened modified file
 
*saved as file:///usr/share/sugar/activities/Browse.activity/data/index.html
 
*Started "sugar-emulator" and Browse as "Start new"
 
*took this screenshot:
 
 
 
 
 
http://people.sugarlabs.org/Tgillard/Modified-default-bookmark.png
 
 
 
 
 
==='''Change-Browse.activity index.html-to-use-Modified-Browse-html in a live USB'''===
 
 
 
*In booted USB-soas-i386-20100611.15.iso:
 
 
 
*In Sugar Terminal;
 
su
 
yum install wget
 
wget http://people.sugarlabs.org/Tgillard/Modified-Browse.html
 
cd /home/liveuser
 
chmod 777 Modified-Browse.html
 
cp /home/liveuser/Modified-Browse.html /usr/share/sugar/activities/Browse.activity/data/index.html                                                                                               
 
  [root@localhost ~]# cp /home/liveuser/Modified-Browse.html /usr/share/sugar/activities/Browse.activity/data/index.html
 
  cp: overwrite `/usr/share/sugar/activities/Browse.activity/data/index.html'? y
 
  [root@localhost ~]#
 
 
 
'''It worked after this. Browse has a new "Start-New" screen. SUCCESS  (06/12/2010)'''
 
 
 
*'''Note: One step farther:'''
 
  su
 
mkdir /usr/share/library-common
 
cp /usr/share/sugar/activities/Browse.activity/data/index.html usr/share/library-common/index.html
 
* Sets up Firefox v 6 .xo (experimental on ASLO) to use the same index.html as Browse uses.
 
*On live USB Stick (06/13/2010)
 
  
 
== Detailed Description ==
 
== Detailed Description ==
'''In a discussion with Peter Robinson, I discovered that a custom bookmark Browse.rpm can be downloaded from the fedora repository. I propose we use this fact to create a custom set of bookmarks and artwork for Soas with links to: e-books; Floss Manuals; wiki.sugarlabs.org, all of the  links to files in the SugarCreationKit DVD + The Normal Browse Google Screen'''
+
'''In a discussion with Peter Robinson, I discovered that a custom bookmark Browse.rpm can be downloaded from the fedora repository.
 +
* I propose we use this fact to add a link on the startup page to a Customized Introductory page on the wiki for Soas with links to:
 +
# Instructions
 +
# Compatable Activities
 +
# Installation Methods
 +
# Floss Manuals
 +
# Pertinent links to pages on wiki.sugarlabs.org
 +
# Artwork -DVD/CD Covers etc
 +
# e-books (?)
 +
# Other sources of information (blogs/web sites etc)?
  
 
*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.  
 
*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.  
Line 125: Line 99:
 
Bernie has such a revised startup screen in his os240py software for the XO-1
 
Bernie has such a revised startup screen in his os240py software for the XO-1
  
===A simple '''test''' example (see screen-shot above) works well===
 
 
*'''It Contains the normal Browse links:'''
 
*Home
 
*Wiki
 
*Bugs
 
*Activites
 
*'''plus'''
 
*MENU- which points to an On line Version of the SugarCreationKit DVD, (with all of the links to the sources.)
 
# CLICK THIS LINK TO TEST: http://wiki.sugarlabs.org/go/Sugar_Creation_Kit#INDEX_OF_Soas_Features
 
*'''AND'''
 
*The fedora '''Personal Toolbar Folder''' with all of it's links
 
  
==='''Sugestions on just what content should be included on This screen must be determined from discussions on the lists.'''===
+
===This is the Proposed start screen===
 +
* Use the existing Browse start screen and just insert one Custom Link '''Introduction:Soas_Mango_Lassi'''
 +
::CLICK THIS LINK TO TEST:  http://people.sugarlabs.org/Tgillard/index14.html
 +
:: This example will be changed when Mango Lassi becomes available
 +
* This looks like the most acceptable Idea
 +
* '''Discussion with mchua 06/16/2010 on #Sugar-meeting'''
 +
# I need to start a Git account
 +
# Make proposed changes in Git to file http://git.sugarlabs.org/projects/browse/repos/mainline/blobs/master/data/index.html
 +
 
 +
'''Suggestions on just what content should be included on this screen must be determined from discussions on the lists.'''
  
The changes in content on the Browse index-html can be updated via a .rpm file dowloaded from the repositories plus it will be used for the build of the Browse.appliance in the v4 Soas-spin.
+
* The Customized Browse index-html will be used for the build of the Browse.appliance in the v4 Soas-spin.
  
 
== Benefit to Sugar ==
 
== Benefit to Sugar ==
Line 148: Line 119:
  
 
== Scope ==
 
== Scope ==
* Edit the Browse activity to point to default-bookmarks.html or some other file specified by fedora
+
# Revise the browse start new screen for Soas
 +
#(optionally) Edit the Browse activity to point to default-bookmarks.html or some other file specified by fedora
  
 
==UI Design==
 
==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.''
 
''Does the feature have a direct impact on the work flow, or does it need a UI? Link here mockups, or add detailed descriptions.''
Original Idea: Now depreciated:
+
*Prototype start-page:http://people.sugarlabs.org/Tgillard/index14.html '''REVISED''' 06/19/2010
  
*Point Sugar.Browse default "start new" screen to:
+
== How To Test ==
file:///usr/share/bookmarks/default-bookmarks.html
 
* "We'll use something slightly different so we don't conflict." pbrobinson
 
  
 +
Prototype start-page:http://people.sugarlabs.org/Tgillard/index14.html '''REVISED''' 06/19/2010
  
*instead of sugars's default:
 
file:///usr/share/sugar/activities/Browse.activity/data/index.html
 
 
Comments:
 
:This is the first thing a SoaS user will see when the Sugar web browser is launched.  This is a critically important page.  I don't think we should accept anything util these groups have looked at it:
 
 
* Existing SoaS deployments
 
* Other sugar deployments
 
* SL Marketing
 
* Fedora Marketing (not sure if this is applicable)
 
 
At least as much thought should go into changing the page as went into creating it in the first place.
 
 
[[User:MartinDengler|MartinDengler]] 15:06, 14 June 2010 (EDT)
 
 
== How To Test ==
 
{{:{{PAGENAME}}/Testing}}
 
 
== 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.''
 
''If this feature is noticeable by its target audience, how will their experiences change as a result?  Describe what they will see or notice.''
Line 188: Line 142:
  
 
== Contingency Plan ==
 
== Contingency Plan ==
'''Alternate path: edit /usr/share/sugar/activities/Browse.activity/data/index.html. This would allow sugarlabs to maintain the list.'''
+
 
* the Browse index.html on will need to be changed. (Edited)
+
'''Alternate path:'''
 +
* edit /usr/share/sugar/activities/Browse.activity/data/index.html
 +
 
 +
* Duplicate with SugarClone, locally,for small number of customized sticks
  
 
== Documentation ==
 
== 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.''
 
''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.''
 
* Discussed with pbrobinson initially and mchua today 06/12/2010 on #sugar-meeting
 
* Discussed with pbrobinson initially and mchua today 06/12/2010 on #sugar-meeting
* Soas Meeting 06/13/2010
+
* Soas Meeting 06/13/2010 http://me.etin.gs/sugar-meeting/sugar-meeting.minutes.20100614_1502.html
  
 
== Release Notes ==
 
== Release Notes ==

Latest revision as of 14:51, 5 November 2013




Summary

What I am trying to Achieve:

An enhanced "start new" screen for sugar.browse in the fedora.spin-soas v4. It should have a added customizable link and possibly Graphic Elements Suitable for SoaS v4 Mango Lassi

Ideas from Soas #sugar-meeting: 06/14/2010

  • Idea Crystallization credits to mchua:, mtd and others.
  • This is the second idea we discussed

Proposed custom default page for SoaS v4 Mango Lassi

Summary: add new link 'Introduction:-Mango Lassi' inserted to the left of the existing 5 links.
The Use of a customized introduction page on the wiki is a part of this proposal.

List of proposed links (left to right)

  1. Introduction:-Mango Lassi
Link to Custom wiki page
Special page on wiki with Needed Materials for using Soas-v4-Mango Lassi
This is a way for teachers and users to access information from the wiki and other pertinent web sites.
Uses this link: http://wiki.sugarlabs.org/go/Talk:Sugar_Creation_Kit#Introduction_to_Soas-v3_Mirabelle - This will change for v-4 THIS IS A SAMPLE ONLY
  1. Home
  2. Wiki
  3. Bugs
  4. Activities
  5. Google search


NOTES:
http://me.etin.gs/sugar-meeting/sugar-meeting.log.20100705_1502.html

older Comments
  • mtd: a customizable start page exists.
  • This is the first thing a SoaS user will see when the Sugar web browser is launched. This is a critically important page. I don't think we should accept anything until these groups have looked at it:
Existing SoaS deployments
Other sugar deployments
SL Marketing
Fedora Marketing (not sure if this is applicable)

At least as much thought should go into changing the page as went into creating it in the first place.

MartinDengler 15:06, 14 June 2010 (EDT)

Owner

  • Email: satellit@bendbroadband.com

Current status

  • Targeted release: SoaS_v4_Feature
  • Last updated: (07/05/2010)
  • Percentage of completion: 100%
Need to make git account and do edits so a diff can be created (mchua 06/16/2010)
[15:29:57] <mchua> #agreed Browse start page feature accepted - mchua is the feature sponsor
[15:30:17]
[15:30:40] <mchua> #info Implementation: genericize patch, push to upstream Browse, edit wiki pages it links to - use this as an example of the feature process, as it's simple but an obvious change
[15:30:51]
[15:31:01] <mchua> hm, "clearly visible and easily to understand" is probably better than "obvious" but anyway...
[15:31:24] <mchua> satellit__: so go ahead and move it to the "accepted" section of the features list, and let me know when you're going to be in Portland and we'll sit down and work on it then.

Detailed Description

In a discussion with Peter Robinson, I discovered that a custom bookmark Browse.rpm can be downloaded from the fedora repository.

  • I propose we use this fact to add a link on the startup page to a Customized Introductory page on the wiki for Soas with links to:
  1. Instructions
  2. Compatable Activities
  3. Installation Methods
  4. Floss Manuals
  5. Pertinent links to pages on wiki.sugarlabs.org
  6. Artwork -DVD/CD Covers etc
  7. e-books (?)
  8. Other sources of information (blogs/web sites etc)?
  • 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.

This allows a number of custom startup screens depending on the deployment or a schools requirements for Soas v4

Bernie has such a revised startup screen in his os240py software for the XO-1


This is the Proposed start screen

  • Use the existing Browse start screen and just insert one Custom Link Introduction:Soas_Mango_Lassi
CLICK THIS LINK TO TEST: http://people.sugarlabs.org/Tgillard/index14.html
This example will be changed when Mango Lassi becomes available
  • This looks like the most acceptable Idea
  • Discussion with mchua 06/16/2010 on #Sugar-meeting
  1. I need to start a Git account
  2. Make proposed changes in Git to file http://git.sugarlabs.org/projects/browse/repos/mainline/blobs/master/data/index.html

Suggestions on just what content should be included on this screen must be determined from discussions on the lists.

  • The Customized Browse index-html will be used for the build of the Browse.appliance in the v4 Soas-spin.

Benefit to Sugar

A simple enhancement to sugar.browse

MartinDengler 13:51, 14 June 2010 (EDT) In fact this is not an enhancement, it's a hack. The browse homepage should be made configurable (perhaps via gconf) and have a sensible default. In fact, you should do some research before you hack an app to pieces: this customisation is already possible and designed-for...see http://cgit.sugarlabs.org/browse/mainline/tree/webactivity.py#n354 and http://cgit.sugarlabs.org/browse/mainline/tree/webactivity.py#n162. The desired homepage should go in /usr/share/library-common/index.html . Please can we do some research before we flail about doing stuff. Sorry about the language but I don't have time to say this more nicely.

Scope

  1. Revise the browse start new screen for Soas
  2. (optionally) Edit the Browse activity to point to default-bookmarks.html or some other file specified by fedora

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

Prototype start-page:http://people.sugarlabs.org/Tgillard/index14.html REVISED 06/19/2010

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.

  • When Browse is started with Start new or for first time, this page will open. Custom content with links to web pages will be displayed.

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?

  • The advantage is that the Modified default-bookmarks file is updated from fedora in a normal way to Soas and is part of the build of v4
  • Fedora requires a .rpm packaging
  • Original Index.html is customizable.

Contingency Plan

Alternate path:

  • edit /usr/share/sugar/activities/Browse.activity/data/index.html
  • Duplicate with SugarClone, locally,for small number of customized sticks

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.

  • not a release in normal sense

Comments and Discussion