These guys are going to be at the GNOME summit...
http://www.wine-doors.org/screens/wizbit.ogg
http://git.codethink.co.uk/?p=wizbit;a=summary
From #gnome-hackers:
aantn Jc2k: wizbit?
Jc2k imagine git as a library and throw in syncing that makes sense
for the user.
Company to me he said we made
= New requests =
Read icon appears in home view
http://dev.laptop.org/ticket/8726
___
Sugar mailing list
Sugar@lists.laptop.org
http://lists.laptop.org/listinfo/sugar
Hi Guys,
This is a great discussion and very helpful design interaction!
Just sampling a few items on this thread I have two high level comments:
1 - The primary requirement for the Journal is to never lose data. I
think there are some known issues with the datastore but I'm not sure
where
Hello,
we skip this week - you might want to join in for eben's wonderful
design meeting at 15.30 UTC though.
Best,
Simon
___
Sugar mailing list
Sugar@lists.laptop.org
http://lists.laptop.org/listinfo/sugar
Michel Dänzer wrote:
As a result of ee7c684f21d, the PutImage hook in ShmFuncs is no longer
being used. Shall I commit a cleanup?
ShmPutImage is still accelerated though (also, that commit is only in
1.5, not 1.4). What kind of cleanup do you have in mind?
Remove the unused PutImage hook
On Thu, Oct 2, 2008 at 1:46 PM, Marco Pesenti Gritti [EMAIL PROTECTED] wrote:
aantn pippin: my point was that we should add commits on top of that
for notable editions that the user wants to be able to revert back to
notable editions are what I called interesting entries.
I need to read and
On Thu, Oct 2, 2008 at 3:55 PM, Greg Smith [EMAIL PROTECTED] wrote:
Hi Guys,
This is a great discussion and very helpful design interaction!
Just sampling a few items on this thread I have two high level comments:
1 - The primary requirement for the Journal is to never lose data. I
think
1 - The primary requirement for the Journal is to never lose data. I
Say what? Maybe one could argue that this is the primary requirement
for the datastore, but the Journal is there primarily as a place of
reflection. The fact that the datastore has been problematic and that
the Journal is so
On Thu, Oct 2, 2008 at 12:57 PM, Walter Bender [EMAIL PROTECTED] wrote:
1 - The primary requirement for the Journal is to never lose data. I
Say what? Maybe one could argue that this is the primary requirement
for the datastore, but the Journal is there primarily as a place of
reflection. The
9 matches
Mail list logo
