Search results

Jump to navigation Jump to search
  • Read the [[Platform_Team/Sweets/Glossary|Sweets Glossary]] to understand the bas After getting any unpredictable Sweets behaviour, read the following notes.
    7 KB (982 words) - 13:13, 6 December 2011
  • {{anchor|Who Should Read This Document}} {{anchor|How to Read This Document}}
    7 KB (1,126 words) - 20:28, 7 July 2009
  • ...se utilizan estas traducciones en Browse, Colors, ImageViewer, Labyrinth, Read y Write||Gonzalo Odiard - gonzalo at laptop dot org|| 17/5/2011||
    3 KB (468 words) - 10:54, 7 July 2011
  • * Read
    3 KB (492 words) - 03:30, 8 February 2010
  • Calling ioctl() to re-read partition table.
    4 KB (522 words) - 19:47, 4 March 2012
  • read and comment on them, and return them. <br>
    9 KB (1,510 words) - 18:44, 1 November 2009
  • :'''READ THESE FIRST!''' *Read the Docs :http://readthedocs.org/ hosts documentation
    19 KB (2,733 words) - 22:17, 15 May 2016
  • Read: ImportError: No module named evince
    12 KB (1,525 words) - 08:33, 16 July 2012
  • ...more authoritative description of how Sugar is structured, you should also read other pages on this wiki, including [[Taxonomy]] and others. Hopefully you've read the [[Taxonomy]] page and all of this will make sense to you already. If y
    14 KB (2,246 words) - 15:09, 29 August 2012
  • :'''<cjb>''' of course, whoever proposes a new decision on the topic should read the DP's work first ...so we shouldn't just take it as gospel or anything. it's just something to read and help educate us.
    28 KB (5,081 words) - 23:24, 1 March 2011
  • ...that cannot run should be removed or fixed: jigsaw, sliderpuzzle, browse, read, flipsticks. * 623726 '''read''' fails to start--Starts now, but does not open file.
    7 KB (1,131 words) - 10:08, 30 May 2011
  • ...ity. If you want to know how the tube is set up from start to finish, then read the section on [[#How do I setup a D-Bus Tube? | setting up a D-Bus tube]]. ...corporated in to an example activity called "Annotate". In activities like Read or Annotate, the goal is to set up a one way communication between the "sha
    28 KB (3,937 words) - 21:32, 23 February 2010
  • ...|yes ||&nbsp; ||yes '''OK@''' ||yes || ||A simple Activity to learn how to read and tell the time ...icket/1900 [http://activities.sugarlabs.org/en-US/sugar/addon/4028]*[sugar-read-79-1.fc14.noarch requires gnome-python2-evince] **(yes pdf/no txt clipping
    26 KB (3,678 words) - 13:42, 20 December 2011
  • ...|yes ||&nbsp; ||yes '''OK@''' ||yes || ||A simple Activity to learn how to read and tell the time ...icket/1900 [http://activities.sugarlabs.org/en-US/sugar/addon/4028]*[sugar-read-79-1.fc14.noarch requires gnome-python2-evince] **(yes pdf/no txt clipping
    26 KB (3,678 words) - 11:18, 4 January 2012
  • ...young learners). Among the Activities, Browse, Write, Calculate, Terminal, Read, ImageViewer, and Turtle Art have already been ported to use the new Toolba === Read ===
    18 KB (2,591 words) - 03:29, 4 October 2010
  • ...|yes ||&nbsp; ||yes '''OK@''' ||yes || ||A simple Activity to learn how to read and tell the time ...icket/1900 [http://activities.sugarlabs.org/en-US/sugar/addon/4028]*[sugar-read-79-1.fc14.noarch requires gnome-python2-evince] **(yes pdf/no txt clipping
    25 KB (3,641 words) - 17:14, 29 December 2015
  • Read v.92 -
    18 KB (2,461 words) - 13:48, 15 July 2012
  • ...t://...", you can't push. the git:// protocol is unauthenticated and hence read-only ...''' copying my bad history into mainline makes mainline history harder to read.
    36 KB (5,917 words) - 13:12, 3 September 2011
  • ..., so when you're done hit the back button to get back to this page. Please read the prototype notes as it explains what each screen is for. Once you're don
    6 KB (923 words) - 18:44, 6 September 2010
  • |<-- FranXOphonie has left freenode (Read error: 145 (Connection timed out)) ...aving trouble working out whether that would actually happen.. I'll try to read over the archives and think some more
    24 KB (4,258 words) - 23:30, 1 March 2011

View (previous 20 | next 20) (20 | 50 | 100 | 250 | 500)