"Sounds like we need someone with a bit of Gimp skill to gloss up some
nice pictures. The User guide has some images, and the Keyboard wiki
article, for instance, has some useful bits to pull together.
"<br><br>put a request on <a href="http://wiki.laptop.org/go/Art_Wanted">http://wiki.laptop.org/go/Art_Wanted</a> and i'll make sure and poke artists [seems that not everyone has put that page on their watchlist :/]. anyway, if you need artwork [or graphics, or anything visual, really], that's generally a good place to start.
<br><br>-nikki<br><br><div class="gmail_quote">On Dec 25, 2007 1:03 AM, Michael Burns <<a href="mailto:maburns@gmail.com">maburns@gmail.com</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br><br><div class="gmail_quote"><div class="Ih2E3d">On Dec 24, 2007 7:01 AM, gnome <<a href="mailto:gnome@greenglim.com" target="_blank">gnome@greenglim.com</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
1) Include a printed "map" of the keyboard, ports, and external features<br>*with the machine when it arrives*! This might be a good idea<br>everywhere. Kids will figure it out by playing around, that's true, but
<br>they may also try plugging in that old cell phone charger that's lying<br>around with perhaps not-so-good consequences.<br></blockquote></div><div><br>Sounds like we need someone with a bit of Gimp skill to gloss up some nice pictures. The User guide has some images, and the Keyboard wiki article, for instance, has some useful bits to pull together.
<br><br>We should gather some pictures (<a href="http://flickr.com" target="_blank">flickr.com</a> has thousands of XO images released under creative commons by now) and throw something together on the wiki. If it gets quality, we can export a pdf version of it.
<br><br><a href="http://wiki.laptop.org/go/Keyboard" target="_blank">http://wiki.laptop.org/go/Keyboard</a><br> </div><div class="Ih2E3d"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>Also include a *printer friendly* version on the web site. The current<br>mouseover pages have all the info and look great, but you should see<br>what my scribbled reference printout looks like.</blockquote></div><div>
<br>
Part of what we include with each laptop is the Library and Content. A series of documents, links and resources to using and accessing free material. For instance, public domain book texts (essentially, early 1900s or before) from Project Gutenberg might be included on a future XO.
<br><br>We could expand that, potentially, to include the User Guide translated to the local language. Or just keep a copy on the School Servers much more expansive content Library.<br><br></div><div class="Ih2E3d"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
2) Include, in bold type, in the flyer that ships with the machine, the<br>URL of the wiki basic manual.</blockquote></div><div><br>I would like to work to make the default homepage for Browse more powerful. Possibly with a link to various documents, like Support.
<br> </div><div class="Ih2E3d"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> Maybe it's there somewhere, but I, for<br>one, was way too excited to see it, and only found the wiki later,
<br>almost by accident. That's also why I didn't realize that it was<br>intended to be the main manual, rather than just one of many possible<br>attempts.</blockquote></div><div><br>Yup, the Manual and Getting Started pages are getting worked on by the hour. I imagine the look of it a month from now will be much more refined. More prominent advertisement of them will go a long way in getting feedback for further improvements.
<br><br> </div><div class="Ih2E3d"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> (See above about many choices being confusing ... ;-) ) (The
<br>big problem with a purely web-based manual is that you have to get on
<br>the web first. So that info should *also* be included in the printed<br>materials with the machine ... including the instructions for<br>WPA-secured wireless until a newer build solves that problem.)</blockquote></div>
<div>
<br>Good point!<br><br>This is why some developer utilities may be included when they otherwise wouldn't: connectivity. It makes sense to have tcpdump (a command line program used to inspect each network packet that is sent to the laptop) installed to help troubleshoot network problems, but it doesn't neccesarily make the same sense to include ltrace*, a library call tracker. Such a utility is easily installed with yum and would be taking up valuable space on the flash drive on the vast majority of machines.
<br></div></div><br>*chosen arbitrarily<br clear="all"><font color="#888888"><br>-- <br>Michael Burns * Student<br>Open Source {Education} Lab
</font><br>_______________________________________________<br>Olpc-open mailing list<br><a href="mailto:Olpc-open@lists.laptop.org">Olpc-open@lists.laptop.org</a><br><a href="http://lists.laptop.org/listinfo/olpc-open" target="_blank">
http://lists.laptop.org/listinfo/olpc-open</a><br><br></blockquote></div><br>