Talk:Activation and developer keys

The page you get to once a developer key is made directs you to copy and paste a long wget command to the terminal. It is not at all obvious how to do that. I managed to, but only with a great deal of hackery. I suppose you could always write down the string, but that is ugly and error-prone.

28 June 2008

The cut (highlight selection and ctrl-c) works fine in the old builds, however, paste (ctrl-v) does not work with the terminal activity in the old builds. Use alt-tab to switch back and forth beteen browse and terminal activities in order to copy manually with accuracy without having to write down the long command.

Another option is to update the terminal activity first, since the new version supports cut and paste.

The instruction for getting a developer key by starting Browse and clicking the Library link 'other' and then 'about your xo' didn't make sense on my G1G1. There is no 'other' link. Perhaps this is out of date or just unclear. The file:///home/.devkey.html approach does work for me.

28 June 2008

I just updated to build 703. The 'other' link referred to above and below disappears in this build. If you click on the link "Activities" in build 703's browser vertical menu, however, and then click on the sub-menu "find activities", the "apply for developer key" link can be found at the bottom of the page that displays, just as it was found at the bottom of the "about your XO" page in the older builds.

24 June 2008

When you start the browser, it loads an HTML page from the 'disk' (NAND flash memory) showing a google search bar and some quick links to the OLPC web site. To the left of this is a vertical menu listing various headings e.g. 'books', 'media', 'images', etc. The last item in this menu is 'other'. Click on other, and a submenu with the single item 'About your XO' appears. Click on this, and a lengthy file of screen shot images demonstrating XO usage is loaded from 'disk'. So far all this is done offline, and no internet connection is needed. Finally, page to the bottom, and there you will find the link for obtaining a developer key. This loads the .devkey.html file, and when you press 'submit', your keyrequest will be sent out over the internet, assuming you have a connection.

A useful and non-obvious use of the browser activity is as a graphical file browser, which beats the terminal command line any day. When you open the browser and the local disk google HTML page loads, click on the text in the URL bar at the top of the screen. The text will change to show the directory path of the current page. Move the cursor to the end and erase all the characters except the "file:///" and press enter. This will show the root directory, which you can navigate by clicking on entries. When you click on a file entry, e.g. .devkey.html (check the show hidden files box to see this file), the file will be opened and displayed. From there you can click 'submit' as before. A defect of the file browser is there is no right click mechanism for moving, copying, or deleting files.