P.S. Random Paint related question. Are you still in the process of tidying
up the toolbar and paint tools? I'm thinking of spending some time there
with the main intention of designing and implementing support for the new
Sugar toolbars. I didn't want to duplicate our effort if you're
[cc += sugar-devel, tch]
El Sat, 07-08-2010 a las 11:27 +0200, Tomeu Vizoso escribió:
Btw, have read that some notifications about available memory have
landed in cgroups in recent kernels. The Sugar shell could listen to
those and give a chance to background activities to save their state
On Sat, Aug 7, 2010 at 18:11, Bernie Innocenti ber...@codewiz.org wrote:
[cc += sugar-devel, tch]
El Sat, 07-08-2010 a las 11:27 +0200, Tomeu Vizoso escribió:
Btw, have read that some notifications about available memory have
landed in cgroups in recent kernels. The Sugar shell could listen
On Sat, Aug 7, 2010 at 12:01 PM, Tomeu Vizoso to...@tomeuvizoso.net wrote:
Just wanted to share a link to this book, check out the gitcasts!
http://www.gitcasts.com/
http://www.gitcasts.com/
http://book.git-scm.com/
Regards,
Tomeu
___
El Sat, 07-08-2010 a las 18:14 +0200, Tomeu Vizoso escribió:
So we would have a periodic wakeup? The test would be the amount of
free memory plus buffers and caches?
A polled design is clearly inferior to a proper notification system, but
it has the advantage of being simple and not requiring
On Sat, Aug 7, 2010 at 19:31, Bernie Innocenti ber...@codewiz.org wrote:
El Sat, 07-08-2010 a las 18:14 +0200, Tomeu Vizoso escribió:
So we would have a periodic wakeup? The test would be the amount of
free memory plus buffers and caches?
A polled design is clearly inferior to a proper
On Sat, Aug 7, 2010 at 19:33, Tomeu Vizoso to...@sugarlabs.org wrote:
On Sat, Aug 7, 2010 at 19:31, Bernie Innocenti ber...@codewiz.org wrote:
El Sat, 07-08-2010 a las 18:14 +0200, Tomeu Vizoso escribió:
So we would have a periodic wakeup? The test would be the amount of
free memory plus
El Sat, 07-08-2010 a las 19:33 +0200, Tomeu Vizoso escribió:
BTW, looking at top, it seems that Sugar and other processes wake up
quite frequently when the system is supposed to be completely idle. It
may be background checks for updates, NetworkManager updates or the
presence service.
El Sat, 07-08-2010 a las 19:36 +0200, Tomeu Vizoso escribió:
On a second thought, Sugar should probably only listen to events
relevants to what is being currently displayed. This would display
outdated data for a short while and would mean significant rework but
may be a worthy goal for the
On Fri, Aug 6, 2010 at 9:10 AM, Paul Fox p...@laptop.org wrote:
walter -- currently we try at boot time and set the touchpad to
whichever mode the user last requested. moving this
initialization to sugar was one of the last changes you made to
the sugar code, i think.
but when you were in
We already readjust the network neighborhood layout on the fly when we
switch view. It's funny to see the access points slide around :-)
Haven't bothered to keep track of the appearance/disappearance of XO and
AP icons in Neighborhood View - it's hard to figure out whether their
presence on
Hi Mikus,
On 7 Aug 2010, at 20:01, Mikus Grinbergs mi...@bga.com wrote:
We already readjust the network neighborhood layout on the fly when we
switch view. It's funny to see the access points slide around :-)
Haven't bothered to keep track of the appearance/disappearance of XO and
AP
invitation icons seem to persist long after all invitors/invitees are gone.
is this as 'simple' as removing the notification when the activity id is no
longer being
shared? Or would you like the UI to still indicate that you had missed the
event/s?
I imagine if someone clicks on an
On Sat, Aug 7, 2010 at 1:31 PM, Bernie Innocenti ber...@codewiz.org wrote:
El Sat, 07-08-2010 a las 18:14 +0200, Tomeu Vizoso escribió:
So we would have a periodic wakeup? The test would be the amount of
free memory plus buffers and caches?
A polled design is clearly inferior to a proper
Is there interest in pushing an updated sugarbot to git.sl.o?
I have spent some time over the last three days getting Sugarbot to run in
sugar-jhbuild. After a few code changes, and lots of reading, I have been
successful.
Some changes that needed to be made from the 0.1 release:
- a few syntax
On 6 Aug 2010, at 13:35, Tomeu Vizoso to...@sugarlabs.org wrote:
I was just throwing in the idea here. I will bother you further only
once I have a realistic plan in mind (and confidence in the ability to
execute it with our limited resources) :)
Sorry if I sounded harsh, I wanted to
On 7 Aug 2010, at 21:08, Tiago Marques tiago...@gmail.com wrote:
Just killing a random activity is a terrible idea becayse you don't want your
product behaving like it's defective; the pop up idea is way more
acceptable(and a lot better than having the system randomly behaving like
it's
17 matches
Mail list logo
