-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sebastian Silva wrote:
Clearly, the provider should not be on the laptop. That would defeat
the entire purpose of having an Identity Provider.
You misunderstand our purpose. The immediate technical goal is to
authenticate that a given connection
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martin Langhoff wrote:
- A backchannel call using SSH
- A challenge-response call using the fact that the XS knows the
public SSH key of the XO.
You really like SSH!
I'm less sure, though. I'd prefer a standard system. One interesting
option
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Gary C Martin wrote:
Just a nit pick, SciPy is much replaced by Numpy though SciPy still
overlaps enough the documentation seems pretty useful.
This is a typo. You mean that Numeric and Numarray are replaced by NumPy.
SciPy is NumPy's sister
Marco Pesenti Gritti wrote:
On Fri, Nov 7, 2008 at 2:21 PM, Martin Langhoff
[EMAIL PROTECTED] wrote:
Well, our journal use model says that the document is picked before
the app is called, so if we support
$ sugar-wrapper Write.xo mydocument.rtf
then we're done. (Again, I might be
Marco Pesenti Gritti wrote:
On Sat, Nov 8, 2008 at 6:45 PM, Benjamin M. Schwartz
[EMAIL PROTECTED] wrote:
Marco Pesenti Gritti wrote:
On Fri, Nov 7, 2008 at 2:21 PM, Martin Langhoff
[EMAIL PROTECTED] wrote:
Well, our journal use model says that the document is picked before
the app
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Marco Pesenti Gritti wrote:
On Sat, Nov 8, 2008 at 10:56 PM, Benjamin M. Schwartz
[EMAIL PROTECTED] wrote:
There are two issues here:
1. I don't know how the inner workings are designed, but as a Python
activity author I never have to write
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tomeu Vizoso wrote:
And see xattrs for a design that
avoids this mess.
xattr values are also just bytes with no type, and so will have exactly
the same problem. Their behavior would be equivalent to D-Bus's a{ayay}.
Python's behavior in this
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Erik Garrison wrote:
It seems from my reading of mailing lists, IRC logs, and listening to
conversations with people that we are trying to resolve all of these
issues by implementing more code to get around difficulties imposed by
our current data
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tomeu Vizoso wrote:
I have stopped work on the DS and Journal because OLPC is apparently
funding the development of a replacement for them
Really?
We could easily hack the DS in 0.83 to return D-Bus strings for
standard properties that are known
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
C. Scott Ananian wrote:
I expect Sayamindu can probably give a better talk than me on this.
But I'm willing to give a short talk on translation things I'd like
to see in 9.1:
* multiple languages, multiple places: translation system
should
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
As some of you may know, Chandler [1] is a project to build a
PIM/Messaging/Calendaring application. After many years of development,
the development team has released Chandler, now at version 1.0.2.
Like Sugar, Chandler is a free software project,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
It seems to me that the points of controversy at Scott's datastore talk
primarily concerned the way data is stored. In particular, the Journal
requires the storage of a certain amount of metadata about each file, and
the way we store this metadata
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Eben Eliason wrote:
| Proposal (off the cuff, please poke holes in this): We might beef up
| the HIG in the area of tagging, and even suggest a set of canonical
| tags for various types of content. (Localized, of course.) Combining
| this with
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Eben Eliason wrote:
| On Mon, Oct 13, 2008 at 6:53 AM, Carlo Falciola [EMAIL PROTECTED] wrote:
| Carlo : nowhere in the default GUI there is a clock, even if, in the
control panel there is a panel to configure it. I think that personal
watches are
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tomeu Vizoso wrote:
| Crazy idea: put in the frame a widget that only updates (and displays)
| itself 20 seconds after the mouse has been over it. If it was an
| analog clock, the arms could dissolve when it stops updating, if a
| digital clock, it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tomeu Vizoso wrote:
| On Sun, Oct 5, 2008 at 3:51 AM, Benjamin M. Schwartz
| [EMAIL PROTECTED] wrote:
| I have written up an algorithm for quasi-optimal placement of items in the
| Mesh View.
...
| I am not sure whether this algorithm is of use
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
elana langer wrote:
| a) In response to the question about the Mesh - there are a whole
| bunch of issues that come up. -- to use acoustic measure only two
| computers can be on at a time so it makes the tool almost impossible
| to use in a class or
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Bryan Berry wrote:
| There is something I would like to add. Folks from rich countries (like
| myself) underestimate the importance of narratives b/c we are surrounded
| by libraries, online tutorials in our native language, extensive
| versions of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I have written up an algorithm for quasi-optimal placement of items in the
Mesh View. It involves linear algebra. I have actually implemented it,
in less than 100 lines of python. It is described here:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I very much like Tomeu's version model, but I am also unsure whether I
have interpreted it correctly.
My feeling is that each object in the Journal is associated with a tree of
versions. The tree has one node with no ancestors: the root node, which
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Walter Bender wrote:
| Anyone know much about U3 flash drives? Would this be the simplest
| (for the end user) way of booting a LiveUSB image of Sugar? (I worry
| about asking people to change their BIOS to enable USB boot as being
| too off-putting.)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Erik Garrison wrote:
| Hello all,
|
| On tabbing we are currently auto-toggling the frame. Are we sure that
| this is necessary? Could we include a configuration option to change
| this?
|
Another option, which I would prefer, is to show only the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Congratulations are in order, I think, for the Telepathy developers. Gnome
2.24 was just released, and from
http://library.gnome.org/misc/release-notes/2.24/
GNOME 2.24 announces the inclusion of an instant messaging client based
off the Telepathy
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Some people have mentioned that they would like to see bugs of general
interest advertised on the mailing lists.
As such, if you are interested in the subject line, you may enjoy a
proposal at http://dev.laptop.org/ticket/8611
- --Ben
-BEGIN PGP
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tomeu Vizoso wrote:
| 2.- all metadata properties are just strings.
I think this is a good decision (especially since by strings you mean
byte arrays). However, it's not quite true. Your design actually has
two classes of metadata properties:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
C. Scott Ananian wrote:
| On Tue, Sep 23, 2008 at 2:13 PM, Benjamin M. Schwartz
| [EMAIL PROTECTED] wrote:
| -BEGIN PGP SIGNED MESSAGE-
| Hash: SHA1
|
| C. Scott Ananian wrote:
| | A hand-drawn proposal for what a Journal supporting directory
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Walter Bender wrote:
| (I run SKYPE in Bert's X Activity
| without a problem.)
The principle goal of this discussion is to make the X Activity
unnecessary by moving that functionality into Sugar's window management.
Possible motivations for this
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Marco Pesenti Gritti wrote:
| On Fri, Sep 19, 2008 at 12:13 AM, Benjamin M. Schwartz
| [EMAIL PROTECTED] wrote:
| Let's keep thinking about this. For example, I wonder what Metacity does
| to a window that is both _NET_WM_STATE_FULLSCREEN
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
We are talking about replacing Matchbox with Metacity in the XO build of
Sugar.
C. Scott Ananian wrote:
| When I run
| sugar under metacity, I don't *want* my activities to be full screen.
I think you mean When I run Sugar inside a standard desktop
Sayamindu Dasgupta wrote:
The simplest way to do this is mentioned in the draft, namely, to have
a new _NET_WM_WINDOW_TYPE hint, called _NET_WM_WINDOW_TYPE_NETBOOK_APP
(feel free to suggest a better name :-P).
I do not understand at all why _NET_WM_WINDOW_TYPE_FULLSCREEN is
insufficient.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Benjamin M. Schwartz wrote:
| ... _NET_WM_WINDOW_TYPE_FULLSCREEN ...
That should be _NET_WM_STATE_FULLSCREEN.
Oops,
Ben
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Marco Pesenti Gritti wrote:
| However, though we do not always show frames (or panels), there are
| some environments which show at least a single panel all the time (eg:
| Ubuntu Netbook Remix). In those cases, fullscreen might mean that
| frame may
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Marco Pesenti Gritti wrote:
| On Thu, Sep 18, 2008 at 11:34 PM, Benjamin M. Schwartz
| [EMAIL PROTECTED] wrote:
| In summary, I believe we can safely move to a lightly patched Metacity
| while tagging our windows purely according to the EWMH
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Christoph Derndorfer wrote:
| Sweet, I totally missed that!
|
| Is anyone actively working on integrating that functionality into 'record'
| or making it available as a seperate activity?
|
| Christoph
|
See
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mikus Grinbergs wrote:
| The easiest way to present logs, especially failure logs, is to make them
| available through the standard Journal/Datastore interface. For example,
| we have some agreement that when an Activity fails to launch, the failure
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jameson Chema Quinn wrote:
| For when we actually have bitfrost permissions in the interface, I propose
| another simple bitfrost permission: P_READ_LOGS.
I agree that reading logs is a valuable capability for Sugar to provide.
I don't see why any
Quoting Martin Langhoff [EMAIL PROTECTED]:
There is probably a bug in the mplayer wrapper (are you using an
mplayer 'activity' wrapper?) in that it's not getting rid of the
overlay setup when it loses focus or is minimized.
This is not a bug, at least in the case of losing focus. Color-keyed
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jerry Williams wrote:
| Seems like this problem for linux was solved with RPM.
| With rpm if something is missing for something you want to install, it
| complains and won't let you install it.
That's not really the problem we're discussing. We're
(Foreword: I originally intended to send this e-mail after the release of
8.2.0,
but I have been convinced to send it earlier in order to prompt discussion)
Dear OLPC developers,
Congratulations on your work so far towards 8.2.0, with its new UI, new
underpinnings, and thousands of individual
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mikus Grinbergs wrote:
| I'm not familiar with the details of the Rainbow implementation, but
| I question this claim:
|
| Sugar, as it currently stands, is among the least secure operating systems
| ever, far less secure than any modern Linux or
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Bert Freudenberg wrote:
| Am 24.07.2008 um 14:25 schrieb Benjamin M. Schwartz:
|
| 1. The datastore
| 2. OS Updates
| 3. File Sharing
| 4. Activity Modification
| 5. Bitfrost
| 6. Power management
|
| Note that half of these items have nothing to do
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Kimberley Quirk wrote:
| I think many people will agree with much of what you have identified
| in your rant; and we have been working on making the most progress we
| can given the constraints of the 'real' world:
Kim:
Though I was obviously trying
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Polychronis Ypodimatopoulos wrote:
| At any rate, I will add (I filed a ticket) a sufficiently large (255
| chars?) name field for activities, although I would much prefer
| designing this mechanism properly (any suggestions by Sugar(ed)
|
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Michael Stone wrote:
| 5) Sugar is built on technologies that incentivize its developers to
| recompute prior results which could be cached across boots.
Sugar was intended to write to disk absolutely as little as possible, and
also to reboot as
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Shikhar wrote:
| What am I missing?
Where's the code?
The Distance activity uses threads, gtk, and dbus without any problem, so
that may be a good reference code.
- --Ben
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.9 (GNU/Linux)
Comment:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Greg Smith wrote:
| The new Home View in 8.2.0 will have three available styles.
Really? The home view top bar will show three buttons, for three
different views? This is news to me, though not bad news.
| Vote for your favorite as default first
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chris Ball wrote:
| Another useful feature would be for
| Write to have unique background colors for collaborators, as Gobby does.
| I wonder if that would be a small enough task for someone to take on.
See also #7447. Currently, Write doesn't
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martin Sevior wrote:
| Hi Folks,
| Just so you know. The only reason for #7447 is because we
| haven't put the UI in to enable it.
I would like an additional control for background color. Eben, what do
you think?
| I'm not sure different
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martin Langhoff wrote:
| After
| all, if an activity writer wants to use Klingon characters for
| versioning, hey, let them go wild!
This is actually the key point. Currently, the versioning system is
embedded into the Glucose code itself, and our
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jameson Chema Quinn wrote:
| It is desirable for Sugar to be able to compare versions and
| guess which one is newer.
Newer means more recent. If this capability is important to you, then
we may simply include a datestamp in each bundle, separate
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Eben Eliason wrote:
| I guess the point here is that performing intelligent string comparisons on
| several of these schemes requires parsing the string. ;)
I would be happy to whip up a universal approximate ordering for version
strings in a few
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
C. Scott Ananian wrote:
| On Tue, Jul 8, 2008 at 1:32 PM, Tomeu Vizoso [EMAIL PROTECTED] wrote:
| We could add many more of the missing features to Browse if all the
| developers weren't so busy with the rest of Sugar. Also, although most
| of the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I have a proposal for how to manage objects in the datastore, to resolve
the various issues we have discussed. I call it the Objects and
Translators model. The fundamental idea is this: the datastore is a
flat, non-hierarchical listing of objects
On Wed, 2008-06-11 at 12:11 -0400, Michael Stone wrote:
On Wed, Jun 11, 2008 at 11:37:13AM -0400, Benjamin M. Schwartz wrote:
Cute. Incidental thought: is performing a translation an action?
Thank you. No, I don't see it as an action, especially because I
imagine that the translation
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jim Gettys wrote:
| 3) The decision panel mechanism seems cumbersome, and fraught with
| political danger; if people don't believe the oversight board is being
| fair, they should get rid of the oversight board. There is the
| (possible) issue of how
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Wade Brainerd wrote:
| Too bad the new Google Earth API is much too high level for these purposes,
| it would be great if Google would open up the data.
Check out openaerialmap.org
It's fantastic.
- --Ben
-BEGIN PGP SIGNATURE-
Version:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sayamindu Dasgupta wrote:
| Hi,
|
| On Mon, May 19, 2008 at 5:14 PM, Marco Pesenti Gritti
| [EMAIL PROTECTED] wrote:
| On Mon, May 19, 2008 at 11:41 AM, Marco Pesenti Gritti
| [EMAIL PROTECTED] wrote:
| Maximize + undecorated might work. It has to be
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martin Dengler wrote:
| On Fri, May 30, 2008 at 09:38:39PM -0400, Benjamin M. Schwartz wrote:
|
| Does anyone know how to capture all mouse events?
|
| In trying to do this with pygtk, we both have run into gtk bug
| #156948[1] - for the record
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martin Dengler wrote:
| On Thu, May 29, 2008 at 04:53:03PM -0400, Benjamin M. Schwartz wrote:
| I do not know anywhere near enough about X to make this happen. I hope
| you will respond with advice about what to do, or perhaps volunteer if you
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I think Sugar has a naming problem. There are a lot of different digital
objects being produced by this project, and referring to all of them as
Sugar is becoming increasingly confusing. For example, the discussion
about Sugar on Windows has been
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Marco Pesenti Gritti wrote:
| Blessing a browser is not going to remove competition.
|
| In practice, GNOME blesses a browser and despite most of the
| distributor/users are using another one, with no interoperability
| issues.
This is the key
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jameson Chema Quinn wrote:
| One low-hanging fruit for faster activity start is having activity install
| compile .pyc files, with (tiny) extra points if the .pyc gets hints to not
| use jffs2 compression. This is on my gameplan with the bundle format
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tomeu Vizoso wrote:
| I agree that limiting the number of components released as a whole
| brings important benefits. I think that the idea of releasing some
| activities as part of Sugar is because they provide services that
| are considered a basic
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Walter Bender wrote:
| In general, it'd be great to be able to share like this for most
| activities. Another way of thinking about sharing would be to share
| resources of multiple laptops to get a bigger workspace, e.g., some
| times it is useful to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martin Dengler wrote:
| 'F12': 'volume_up',
| 'ctrlF11' : 'volume_min',
| 'ctrlF12' : 'volume_max',
Given our ctrl/alt/shift distinction, it seems to me that these should be
shiftF11 and
shiftF12
This is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Joshua N Pritikin wrote:
| On Mon, Apr 28, 2008 at 07:39:13PM -0500, Dennis Gilmore wrote:
| On Monday 28 April 2008, Joshua N Pritikin wrote:
| Do we really want to encourage HTML email? :-P
| We should add the option, but i would prefer plaintext
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Reports from the field, especially from Carla and Bryan, have indicated
that the datastore can get into a corrupted state from which it cannot
recover. The corruption persists over a reboot. After corruption,
subsequent datastore calls usually raise
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
John Gilmore wrote:
| The presence implementation only works on access points and on meshes --
| but not on non-meshed, ad-hoc 802.11. The vast majority of computers
| with 802.11 don't have mesh, but they would benefit from being able to
| see
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
John Gilmore wrote:
| The IETF ZeroConf protocols provide for self-assignment of IP
| addresses in such a case. (The same thing happens if you plug two
| laptops together with a short Ethernet cable and no DHCP server.)
|
| Does the OLPC Presence
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Suppose that I am participating in 3 shared activity sessions, all public.
~ I am switching back and forth between them, perhaps copying things from
one to another, and occasionally checking in on the third. The current
mesh view design shows my XO
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Patrick Dubroy wrote:
| On Sun, Apr 13, 2008 at 2:44 PM, Tomeu Vizoso [EMAIL PROTECTED] wrote:
|Another option would be to create a version of Sugar that appeals to
|programmers. But I can't imagine creating such a version that wouldn't
|
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Benjamin M. Schwartz wrote:
| In order for it to run, you must first add 'org.winehq.WineConsole' to the
| list of RAINBOW_CONSTANT_UID activities in
| /usr/lib/python2.5/site-packages/sugar/activity/activityfactory.py
I have now posted
http
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I am trying to make Wine work as a Sugar activity. One of the most
serious problems is that the Wine desktop window appears as a dialog. It
appears in front of the frame, with decorations. I presume this is
because it is non-resizable. However, it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Eben Eliason wrote:
|3. Need easy way to group links to activities, such as in a lesson
|plan.
|
|Use Case:
|Kid reads through geometry tutorial and clicks on first activity which
|opens up Dr. Geo. After finishing w/ Dr. Geo he
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Eben Eliason wrote:
| On Fri, Apr 11, 2008 at 11:15 AM, Bert Freudenberg
[EMAIL PROTECTED] wrote:
| I personally find addressing this scenario not worth the awkwardness
| we currently have, clicking a URL in any activity should open a
| browser on
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Eben Eliason wrote:
| In fact, this exploit could happen even without a launcher service.
| Any activity that wants to could write the users private data to the
| disk in a URL format, as an object, and give it a fun preview image.
| When the later
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Eben Eliason wrote
I prefer option (1) because it's the behavior I would want as a user. With
option (1), it's more obvious that new activity bundles have been
installed. It's also more straightforward to implement.
| Option (2) is somewhat more
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Alexander Larsson wrote:
| On Mon, 2008-03-24 at 15:34 -0400, Benjamin M. Schwartz wrote:
| Dear Mr. Larsson,
| My name is Ben Schwartz, and I am a volunteer with OLPC. As you may be
| aware, the OLPC design calls for a centralized versioning
On Tue, 2008-03-25 at 13:46 -0400, Eben Eliason wrote:
Naturally, there are some security concerns, but those could be easily
addressed, I believe, with the usual signing mechanisms. Updates to
activities would only be transparent if the update was signed, etc.
I agree. For a first
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
In order to run a python program (.py), the python interpreter must first
compile it to bytecode. The bytecode is stored in a .pyc file, when
possible. In the case of installed packages, like NumPy or Sugar, the
.pyc files are generated during
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martin Langhoff wrote:
| On Sun, Mar 23, 2008 at 7:02 PM, Benjamin M. Schwartz
| [EMAIL PROTECTED] wrote:
| # time python -c import compileall;
| compileall.compile_dir('/usr/share/activities/TamTamEdit.activity/',
| force=True, quiet=True)
| real
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
| A low-cost, low-power laptop with a built-in webcam and a somewhat
| iconic interface offers some interesting possibilities for folks whose
| primary means of communication is via sign language.
|
| I'm beginning to generate some interest on campus
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Kent Loobey wrote:
| On Wednesday 12 March 2008 10:51:15 pm Benjamin M. Schwartz wrote:
| The
| question is: do users need to know how memory is being used, and if so,
| what sort of indicator is appropriate?
|
| As a rule of thumb you shouldn't
On Thu, 2008-03-13 at 16:03 -0400, Michael Stone wrote:
Also, it would be easy for Rainbow to enforce a pre-set hard limit on
memory usage for each Activity separately.
I've thought about it before, but I don't think it leads to a good UI at
the moment. The problem is that I don't think
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The original inspiration for the Activity Ring was that the Ring could
serve both to indicate which activities were running and how much memory
they were using. This was considered important in order to provide
feedback to prevent users from
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tomeu Vizoso wrote:
| On Sat, Mar 8, 2008 at 11:17 PM, Benjamin M. Schwartz
| [EMAIL PROTECTED] wrote:
| According to this page:
http://wiki.laptop.org/go/Journal_entry_bundles ...
|
| Each journal entry has a unique uid. This 'uid' is listed
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Long story short:
http://dev.laptop.org/~bemasc/Distribute-1.xo
Story:
Currently, the only way to move data from one XO to another in the UI is
by opening that data from the Journal with the program that edits it,
sharing the editing session, and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to this page: http://wiki.laptop.org/go/Journal_entry_bundles ...
Each journal entry has a unique uid. This 'uid' is listed in its
metadata, and a conforming Journal Entry Bundle uses the uid calue to name
various components of the bundle.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
When I call datastore.write(jobject), my program dies, producing the
appended logfile. The error is
~ File /usr/lib/python2.5/site-packages/olpc/datastore/datastore.py,
line 177, in _resolveMountpoint
~mp = self.mountpoints[mountpoint]
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Benjamin M. Schwartz wrote:
| ~ File /usr/lib/python2.5/site-packages/olpc/datastore/datastore.py,
| line 177, in _resolveMountpoint
| ~mp = self.mountpoints[mountpoint]
| KeyError: dbus.String(u'1285c87a-1b13-4463-9e19-87f0ad8e1828
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tomeu Vizoso wrote:
| On Sat, Mar 1, 2008 at 6:44 AM, Benjamin M. Schwartz
| [EMAIL PROTECTED] wrote:
| I have read all the documents I could find, and also the Sugar source, and
| I am still confused:
|
| How can an activity get an object
On Thu, 2008-02-28 at 17:20 +0100, Tomeu Vizoso wrote:
Right, I think there's some discussion going on about which view
should be the default.
As changing that will be rather trivial code-wise, I guess we can
defer that decision.
I have a proposal that might be relevant, based on a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Arjun Sarwal wrote:
| I need to turn OFF the AGC of the camera on the XO within my Activity.
I recommend that you simply process the input in Bayer mode, which
automatically disables AGC, white-balancing, gamma correction, and other
image
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tomeu Vizoso wrote:
| On Mon, 2008-02-18 at 22:37 -0500, Benjamin M. Schwartz wrote:
| In light of the many requests for a way to distribute arbitrary Journal
entries,
| I am writing an activity tentatively named Distribute. This activity is
| little
On Tue, 2008-02-19 at 13:08 -0500, Chris Ball wrote:
* Encryption/privacy probably isn't desirable here -- we're dealing with
objects that the user has chosen to have backed up.
The Bitfrost spec refers to this as a primary backup. It is
inevitable, since in the case of hardware failure, any
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I use monospace fonts to render numeric fields in each of my activities. For
example, at one point to set the font for a label I use:
valuefont = pango.FontDescription()
valuefont.set_family(monospace)
valuefont.set_absolute_size(300*pango.SCALE)
On Tue, 2008-02-05 at 13:51 -0500, Erik Blankinship wrote:
Can someone suggest how to take a screenshot from within a sugar
activity?
Alt+1 , I believe
--Ben.
___
Sugar mailing list
Sugar@lists.laptop.org
http://lists.laptop.org/listinfo/sugar
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
John (J5) Palmieri wrote:
Perhaps you are going about it the wrong way.
Indeed.
First of all decorators
are executed when the method is parsed, way before the class is
instantiated so you will get an error there.
True.
Also by sending
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I would like to create a simple D-Bus signal of the form
@dbus.service.signal(dbus_interface=self.IFACE)
def send(self, message):
return
However, I do not know the type signature of message ahead of time. I also do
not know whether
On Fri, 2008-01-04 at 13:40 -0500, Jim Gettys wrote:
Sample 1: OLPC Trial School in Arahuay, Peru:
Needs printing: but not for the kids (too expensive) for any routine
printing. The teachers need to be able to use an XO for preparing
tests
and handouts for the kids, as conventional
1 - 100 of 114 matches
Mail list logo
