Browse

  This page is monitored by the OLPC team.

Web Browser File:Web.png This activity was core sources in web-activity TST Browse Tickets all - active - new Pootle — POT Marco, Erikos... mime ogg, html see more templates or propose new

See also sugar:Activities/Browse

Description & Goals

Browse activity

  For the general public

Summary

The Browse activity uses the HulaHop library to embed a web browser. The library provides Python access to the XULRunner core code from Mozilla, and thus uses the same Gecko rendering engine and JavaScript language support as Firefox. However, our browser is simpler than Firefox and is not directly compatible with Firefox add-ons. An alternate, more complex browser for the OLPC is Opera, also Firefox itself.

Browse can

• display web pages
• display several Image file formats such as PNG and SVG files
• access local files, and remote files using the HTTP/HTTPS/FTP protocols
• download files to the Journal
• display the OLPC Library of local content on its home page
• run certain browser plug-ins, depending on configuration
• run much of the latest "HTML 5" web technologies such as the <canvas> tag, interactive SVG, and AJAX JavaScript used on rich web sites.
• provide a place to share browsable information

Collaboration

The web-activity does feature collaboration. To share your session you select the scope in the Activity tab of the web-activity. The icon will be visible in the mesh view and the session can be joined by others. What is shared in the case of the web-activity are links and their information. To share a link you have to hit the 'star button' in the Browse tab right to the entry for the URL. This will generate a link from the currently visited URL, creates a thumbnail of the visible page and add it to a tray at the bottom of the page. The link contains the thumbnail the title of the page and the owner of the link which is displayed in the palette visible when you hover over the link. The same information will be visible to the other members of this shared session. They can then decide whether they want to follow the link (browse to the web-page associated with it) or not.

We decided to implement the friends or trust model. This means that any member of the shared session can add a link. This is different than a possible teachers model, where the owner of the shared activity browse links and the members of the session have to follow these actions. The issue of someone adding garbage or undesired information to the session has been taken care of by displaying information about the creator of a link, so we make this a social problem. The name and the XO colors are displayed with the link in the tray. You can remove a link from your tray as well. This happens locally since we want to avoid someone removing links from all the members in the session.

Since bundle version 42, you can hide and show the tray to not use so much space from the actual canvas. This can be toggled with the ctrl+v keystroke. Since image 581, a button to show and hide the tray of the shared links has been added as well.

With bundle version 47 we are introducing the syncing of the shared links when members leave and rejoin (with possible changes in their set of links). Member A might add links when member B is not around and B might do the same. When both then come together again a syncing of their state needs to be done. When you delete a link from your tray it will not be added when you meet with another member where this link is still present in his tray. Below we describe scenarios which should work by now.

Scenarios

• a)
  • A opens an instance and shares it
  • B joins this instance
  • they share information A<->B
  • B quits
  • A changes his information
  • B resumes from journal (A's mesh view instance is still available)

---> B joins and gets synced

• b)
  • A opens an instance and shares it
  • B joins this instance
  • they share information A<->B
  • B quits
  • B resumes from journal (A's mesh view instance is not available anymore)

---> B will share his instance, C joins and gets synced

• c)
  • A opens an instance and shares it
  • B joins this instance
  • they share information A<->B
  • A quits (modifies his version)
  • B quits (modifies his version)
  • A and B resumes from journal and they get synced

A check based on a hash key generated from the url allows us to deny to add a link twice. This does not include if you have deleted a link from the tray once. This link can be added again.

These screenshots show the sharing feature. When you share a link it will be added to the tray at the bottom of the page. Your shared links are saved to the journal as well. You can resume the shared session and it will be synced with the other members of the session.

share your browser session	join a shared browser session in the mesh view	add a link to to the shared session
select a link and display it in the browser	remove a link from your tray	resume the browser from the journal

Link Sharing

Each browsing session will have a tray at the bottom for shared links. This tray will be shared among all of the participants of the activity, and anything shared through it will automatically appear within their histories. Every bookmark that a child makes (with the star button) will automatically be added to the shared links tray; Children may also share links (with the globe button) )that they don't wish to bookmark.

This simple interaction mechanism will provide an entirely new collaborative browsing experience. It could be useful in a classroom setting, allowing a teacher to simply share the links for the day's lessons instead of writing long and complicated URLs on the board. It can also provide a valuable resource for group projects, where each child researches various aspects of a topic and shares the most relevant links with the group. All of the shared links within a session will be preserved with that session. Essentially, any shared link becomes a bookmark unique to that session.

Maintenance for this particular web browser is easily accessed through its settings. If one wishes to change a certain something, they simply click on the browser's name above the page. They can find the settings for it by clicking on Preferences.

View Source

You can show the HTML source code of the current document in the Browse activity. The source will not be displayed in Browse directly - Write will be used instead. This has the advantage that you can edit the source, save the document with the changes made and use Browse again to interpret the code. This is meant to be a simple introduction to 'programming' and looking under the hood.

Load the page you want to have a look at the source code and press either 'fn+space' or 'ctrl+u'. The source of the currently loaded document is saved to the datastore. The entry of this object in the journal will be displayed. The title of the entry is in the form: "Source: [Title]". You can use Write to resume this entry.

loaded page

journal entry of the source object

resume journal entry with Write

Edit Source

After resuming the source entry in Write you are now able to edit this document. For example an easy to recognize change is the modification of the document's title. Locate the string surrounded by the tags <title> and </title>. Change this string, close Write and resume the entry in Browse. If everything worked out fine you will see now the changes you made. Note that only the source will be saved not the images included in a page. So your modified page will likely look slightly different than the one you see when you load it from the Internet.

the source viewed in Write

resume modified source code with Browse

the modified page interpreted in Browse

Downloads

Download the file

Click on the link that is specified for the download of the file. You will be presented with a dialog, we refer to them as alerts http://wiki.laptop.org/go/Specifications/Dialogs. The first alert will provide you with the information that the download has started. It contains as well the information which file you have chosen to download. The alert has a 'Cancel' and a 'Continue' button. If you select 'Cancel' the download will be stopped. You can continue the download by hitting the 'Continue' button. If you do not choose any of the choices the alert will timeout after 10 seconds and the default choice 'Continue' will be used.

A second alert will be displayed when the download has been completed. The options here are 'Ok' which will dismiss the alert and 'Open' which will display the entry that has been created in the journal. You can choose the activity with which you want to resume the object.

download has been started

download has been completed

resume the downloaded object

Monitor the download progress

You can check how much of the download has been completed in the journal. Note: a quick way to switch to the journal is hitting the search key. The journal entry of the object currently downloading will have a progression bar indicating the completeness.

monitor a download in progress in the journal

Cancel a download

You can cancel an ongoing download as well. Switch to the journal and hit the 'x' at the right of the journal entry you want to stop. This will cancel the download and cleanup the disk space that has been used.

Since the download is bound to the Browse instance, stopping Browse will stop downloads in progress as well. In such a case you will be alerted with a dialog if you really want to quit Browse. Clicking 'Cancel' will dismiss the closing of Browse and will continue the downloads. Hitting 'Stop' will cancel all the downloads in progress and quit Browse.

cancel a download in progress

alert if you try to quit Browse when downloads are in progress

Resuming a download

This has not been implemented yet in the curent version.

Install an activity

Find the activity bundle (a .xo file) you like to install and click on the link that is specified for the download. You can find a detailed description about how to do a download in #Downloads

select the activity bundle to download

download has been started

download has been completed

When the download is completed a journal entry will be created. An object in the datastore will be created as well. In the case of a bundled activity the object will be recognized as being an activity and the activity will be installed. An icon for the activity that has been installed is added to the activity tray in the frame.

journal detail view of downloaded object

start the activity from the journal

start the activity from the home view

You can use the start option in the detailed view of the journal entry or the activity icon in the frame to launch the activity . The entry in the journal for the installed activity will be in the colors black and white. This indicates the template of this activity and helps to differentiate from the instances of the activity that will get created in your colors when using the activity.

newly installed activity is launching

activity launched successfully

activity template entry in the journal

Handheld Mode

Button Mapping

As of build 650, scrolling buttons work, but the sharing link and select link buttons are not implemented.

Button	Press	Hold
LEFT	focus previous link	focus previous link
RIGHT	focus next link	focus next link
UP	page up	scroll up
DOWN	page down	scroll down
NORTH	share link	shared link overlay
SOUTH		panning overlay
EAST	select link	TOC overlay
WEST	back	navigation overlay

LEFT, RIGHT, UP, DOWN are the keypad to the left hand side of the screen.
NORTH, SOUTH, EAST, WEST are the buttons on the right hand side of the screen.

My 656 Build behaves as follows.

The LRUD Rocker works as a 4 direction scroll. The NSEW Buttons act as PgUp PgDn Home and End

No press and hold features seem to be enabled. Specifically, no link or navigation features seem to work at this time

Hold overlay

In the table above, the overlays activated by holding are navigable using the arrow buttons in two different ways. The first button can be held while the option is chosen with the arrow keys; when the first button is released, the option is activated. Alternatively, the first button can be held down until the overlay appears, then released. The arrows are then used to choose an option and any of the NSWE buttons select that option.

Basic Navigation

Basic navigation of a page is supported by the directional buttons in conjunction with the EAST and WEST buttons. UP and DOWN buttons page or scroll the view vertically — the primary direction of scroll — and the RIGHT & LEFT buttons jump to the next and previous links on the page, respectively. Note that the selection focus should remain visible on screen at all times; When the focused link scrolls off of the page, the last or first selectable link in the viewable area should be selected automatically, when scrolling/paging up and down, respectively. The EAST button will follow the currently focused link, while the WEST button will navigate backward. Note that this configuration lacks an explicit forward functionality. In practice, the forward button is used much less than the back button; Here we also make the assumption that a child may navigate forward by selecting the same link again. In order to facilitate this, the scroll position and focused link state will be stored in the navigation stack, such that the link she selected will be auto-focused when she navigates backward. Thus, in effect, the EAST and WEST buttons will function just like forward and back buttons when no intermediate navigational keys are pressed in between.

Panning

Due to the small size of the display, some pages will inevitably require horizontal scrolling. Since the LEFT and RIGHT buttons map to link selection, another means of spatial navigation is required. The SOUTH button, which has no immediate action on press, will activate a panning mode when held. A visual indication of up, down, left and right arrows on the screen will indicate that the child may use these buttons to scroll in each of these directions. When the SOUTH button is pressed momentarily, a short overlay message will appear briefly, informing her that she may hold the button to scroll in all directions.

Advanced Navigation

The EAST and WEST buttons also have overlays when held down. These overlays always act as modifiers for the directional buttons, allowing selections from menus that appear on screen. Since these buttons both serve navigational functions, so too do their overlays. The EAST button, associated with following the selected link, will provide a dynamically generated table of contents (based upon the semantic definitions provided within the HTML) for the active page. Essentially, this will provide a list of anchor links which may or may not actually exist within the page itself, or may exist at the very top, far from the current visible portion of the page. While many pages may not have support for this at all, it will prove invaluable in many instances, such as reading long wikipedia articles. The WEST button, otherwise associated with backward navigation, will provide a navigation overlay. This overlay will operate in two dimensions. Vertically, a list of visited pages in the forward/back queue will appear, with the current page selected at the center. Horizontally, a child may navigate left and right to switch the currently selected tab, allowing them to switch easily between several documents or pages without exiting Handheld Mode.

Link Sharing

Finally, the NORTH button associates with the sharing functionality. Pressing the button will share the link for the currently selected page, effectively bookmarking it within the current Browse session. Since the keyboard is inaccessible in this mode, bookmarks cannot be created. Of course, once shared, any important pages will remain in the shared link bar and can be bookmarked once out of Handheld mode. Holding the NORTH button down will reveal the shared link overlay. This list of all links will indicate visually who posted them and their Title, and allow selection of them at any time during the browsing session.

Explore

A main feature in the OLPC project is the possibility to explore the laptop. For Trial-3 the possibility to show the source of a web page has been added. When the desired page is displayed use the ctrl+u or fn+space shortcut to display the source. This will open a write activity and display the content. This generates an item in the journal as well, which allows use of another activity to display the plain text content. (Added since image 575)

Navigation

There are some shortcuts to facilitate navigation in Browse. Please note that the bookmarks tray will only appear when there are bookmarks to display.

Add a bookmark	ctrl+d
Focus the address entry	ctrl+l
Find in page	ctrl+f
Toggle the visibility of the shared link tray	alt+space (this is a global keystroke that works in other activities as well)
Show the source	ctrl+u or fn+space
View > Fullscreen/Return from Fullscreen	alt+enter
View > Show/Hide bookmarks tray	alt+space

Visual Design

Media

Document	Description
Activity Mockup (216KB) history	Adobe Illustrator file containing mockups for each toolbar

Screenshots

A browsing session	Entering a URL	Navigation
Searching history	Browser alerts	Creating a bookmark
Navigation overlay in Handheld mode

Development

Known Bugs

• google search fails

With build 767, the initial browse activity page suggests a google search or an olpc wiki search. The google search makes a request for google.com instead of www.google.com, resulting in a failed DNS resolution here. Language set to Italian.

• Crash on resizing text

On two or three of occasions I went to the regular BBC news page , and the page loaded properly. Pressing the + icon once caused the text size to increase properly. After waiting briefly for resized page to stabilize, pressing the + icon a second time caused the broswer activity to spontaneously quit. This problem appears to be repeatable on demand.

This problem does not occur when viewing Wikipedia pages, so it may be particular to BBC News, or it may occur in cases where pages have excessive graphical content. I consider this a potentially significant problem since if the font size is too small to be readable, the resulting frustration may discourage reading in general or dampen curiosity to explore.

(Submitted by: G510, not a registered user, but one of the first to order an XO via G1G1)

In Google Docs, the cursor is invisible when using using the word processor.

(The "known bugs" link was broken by the activity name change—I've fixed it.) The bug you describe appears to have been already found and fixed, but thanks for reporting it: Trac ticket 5639. The fix should be present in the big software update coming early next year. —Joe 18:24, 31 December 2007 (EST)

I've had three problems with Browse:

1. When I hit the back button, sometimes Browse spontaneously quits. This error does not happen every time I hit the back button, however.

2. I have also had the browser quit when I tried to resize a page.

3. Sometimes Browse takes almost 5 minutes to start up (most of the time it is much faster).

No alt text when I hover the mouse.

• Browse on Ubuntu

On Ubuntu Hardy, Browse fails due to a problem with hulahop. Recompiling from source will build against a corrected version of xulrunner. Similarly, on Intrepid, recompile sugar-hulahop. (Ubuntu bug 263173)

This page needs clean-up and editing for coherence, clarity, and completeness.

Please improve this article if you can.

RPMs

none available

User-Agent

Browse identifies itself (in the user agent header that it transmits to web sites) as a Mozilla X11 Linux Firefox Gecko browser, using typical conventions to identify the version of each. For example, in release 8.2.1,

For the exact string it transmits in a particular software release, visit a site that echoes the User-Agent header, such as http://www.microsystools.com/serices/http-user-agent/.

Problem Sites

please see Browse/ProblemSites to report any sites with problems

Functional Test

Browse Activity Test Plan

Activity Summary

Icon:	Sugar icon::Image:web.png
Genre:	Activity genre::General Search and Discovery
Activity group:	,|x|Activity group::x}}
Short description:	Short description::A web browser.
Description:	[[Description::Currently, the Web browser is built on Xulrunner and thus uses the same Gecko rendering engine as Firefox. However, our browser is simpler than Firefox and is not directly compatible with Firefox add-ons. Applications can also use xulrunner which includes Javascript capability. An alternate, more complex browser for the OLPC is Opera.]]
Maintainers:	,|x|Contact person::x}}
Repository URL:	Source code::http://dev.laptop.org/git?p=web-activity
Available languages:	,|x|Available languages::x}}
Available languages (codes):	,|x|Language code::x}}
Pootle URL:
Related projects:	Related projects,|x|Related projects::x}}
Contributors:	,|x|Team member::x}}
URL from which to download the latest .xo bundle	Activity bundle::http://dev.laptop.org/~erikos/bundles/0.82.1/Browse-98.xo
Last tested version number:	Activity version::98
The releases with which this version of the activity has been tested.	,|x|Software release::x}}
Development status:	Devel status::4. Beta
Ready for testing (development has progressed to the point where testers should try it out):	,|x|Ready for testing::x}}
smoke tested :
test plan available :
test plan executed :
developer response to testing :