Search results

• 0.86/Platform Components
  The [[Sugar Platform Stack]] is a set of versioned components on which activity authors can rely when targeting their activities to run on a particular Sug Activity authors can expect to find the following components in a system running Sug
  2 KB (258 words) - 09:09, 7 January 2010
• 0.88/Platform Components
  The [[Sugar Platform Stack]] is a set of versioned components on which activity authors can rely when targeting their activities to run on a particular Sug Activity authors can expect to find the following components in a system running Sug
  2 KB (277 words) - 16:48, 5 April 2010
• 0.84/Platform Components
  The Sugar Platform is a set of versioned components on which activity authors can rely when targeting their activities to run on a particular Sug Activity authors can expect to find the following components in a system running Sug
  2 KB (256 words) - 09:08, 7 January 2010
• 0.94/Platform Components
  The [[Sugar Platform Stack]] is a set of versioned components on which activity authors can rely when targeting their activities to run on a particular Sug Activity authors can expect to find the following components in a system running Sug
  2 KB (296 words) - 05:12, 21 October 2011
• Platform Team/Polyol
  *: Sugar core processes and dbus services. * '''DBus'''
  3 KB (463 words) - 09:16, 2 July 2012
• Documentation Team
  People "remixed" these manuals to form the [[Activities/Help|Help activity]] for the XO laptop; a version of this is on the web at http://laptop.org/m ...ustria's [http://www.olpcaustria.org/mediawiki/index.php/Activity_handbook Activity Handbook]
  5 KB (808 words) - 17:13, 29 April 2020
• Development Team/Collaboration Refactoring
  ...and the PS, implement what is needed inside sugar.presence using the D-Bus API. For activities that still depend on the PS D-Bus API.
  3 KB (436 words) - 12:44, 2 August 2010
• Platform Team/Server Kit/sugar-client
  ...gar Shell, and the {{Code|sugar-client}} utility to get access to the same API from the console. ...d by DBus [[Sugar_Server_Kit/Client_API|API]] sugar-client provides. These DBus services will be accessible right after installing {{Code|sugar-client}} pa
  10 KB (1,309 words) - 08:30, 12 June 2013
• 0.84/Platform
  == Stable activities API == * Figure out a compatibility strategy. We can't just break API because a lot of activities out there are using it. But we also can't stick
  7 KB (1,054 words) - 02:41, 3 July 2009
• 0.102/Feature List
  ...limits to the number of open activities and number of open instances of an activity. || 4 Nov 2013 .../Activity Help|Activity Help]] || Display the help for the activity in the activity itself. || 7 Nov 2013
  3 KB (325 words) - 15:00, 29 December 2015
• Features/Remove Presence Service
  ...But the presence information is of use only to the Shell, and the simpler API can be provided to activities with means of a library, so there's no real n ...ugar.presence package, and it does so without changing the python activity API.
  4 KB (610 words) - 16:05, 5 November 2013
• 0.96/Platform Components
  The [[Sugar Platform Stack]] is a set of versioned components on which activity authors can rely when targeting their activities to run on a particular Sug Activity authors can expect to find the following components in a system running Sug
  3 KB (365 words) - 05:55, 12 November 2011
• Features/Start activity from another activity
  [[Category:FeatureLanded|Start activity from another activity]] Activities are provided with a new API to call other activities. This
  7 KB (1,062 words) - 10:51, 21 July 2015
• Features/Fixing Collab (Tubes)
  ...pplications, but realistically can be used to transfer any text data. Chat activity uses this * DBusTube - a shared dbus thing
  4 KB (606 words) - 04:02, 24 December 2015
• Mono
  ...API]]. This page documents how it is possible to use Mono to write a Sugar activity. With Mono, you can use any underlying language like C# or Boo. To write an OLPC Mono activity, you need to prepare a .xo [[Bundle]] including all required libraries. Thi
  7 KB (1,072 words) - 17:39, 30 August 2009
• Archive/Current Events/2013-11-12
  0.101.4 - 04/01/14 - String, UI, API freeze * a webservice for sending Sugar journal items to the Journal Share activity
  3 KB (548 words) - 19:18, 12 November 2013
• Version support for datastore/Progress
  :submitted API draft for review by [[Development_Team|Development Team]] :current code examined and understood; API, on-disk format and UI design chosen
  13 KB (2,056 words) - 12:28, 30 September 2009
• Summer of Code/2010/Video Audio Conference Activity
  ...alut is an XMPP link-local serverless connection manager which is used for activity sharing and presence. Salut uses avahi which shows a real-time graphical br :** Dbus
  11 KB (1,876 words) - 22:48, 2 April 2010
• Sugar Network/API
  This page describes the API that Sugar Network clients use to interact with a Sugar Network server. See ...velopment version of the API.<br>You can find its implementation on the [[#API servers|node-devel.sugarlabs.org]] server.}}
  21 KB (2,934 words) - 08:56, 27 September 2014
• Archive/Current Events/2008-10-27
  ..._PROFILE=username sugar-emulator' command. This works because we use gconf-dbus in sugar-jhbuild and therefore run one gconf daemon per instance. * wrote a proposal about an API stability policy for Glucose; discussed in the Sugar meeting, approved with
  7 KB (1,109 words) - 09:32, 19 December 2016

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