The second thing is basic UI usability. The pop-around menu border makes the
UI
thoroughly unusable with the trackpad
http://dev.laptop.org/ticket/4910 covers this issue and more.
___
Devel mailing list
Devel@lists.laptop.org
On Fri, Mar 21, 2008 at 12:50 PM, Mitch Bradley [EMAIL PROTECTED] wrote:
I think that Update.2 should be about 3 things:
3) Performance
2) Performance
1) Performance
Mechanisms to achieve those performance goals are worthy candidates for a talk!
--scott
--
( http://cscott.net/ )
I sense that this is gonna be a looong thread
C. Scott Ananian wrote:
On Fri, Mar 21, 2008 at 12:50 PM, Mitch Bradley [EMAIL PROTECTED] wrote:
I think that Update.2 should be about 3 things:
3) Performance
2) Performance
1) Performance
Mechanisms to achieve those
Is still the plan for Update.2 to be about the most urgent needs from
the deployments?
Tomeu
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel
On Fri, Mar 21, 2008 at 12:55 PM, Tomeu Vizoso [EMAIL PROTECTED] wrote:
Is still the plan for Update.2 to be about the most urgent needs from
the deployments?
Perhaps I wrote the call for papers too narrowly. Certainly every
stable release will continue to include fixes for pressing
Could somebody answer these questions?
1. What is the status of zlib - lzo transition in jffs2?
2. What is the status of the new X architecture? (The name is DRM but I
am not sure.)
3. What is the status of the shared page python stuff? Will the
reference count problem will be solved in Python
On Fri, Mar 21, 2008 at 6:50 PM, NoiseEHC [EMAIL PROTECTED] wrote:
Could somebody answer these questions?
1. What is the status of zlib - lzo transition in jffs2?
2. What is the status of the new X architecture? (The name is DRM but I
am not sure.)
3. What is the status of the shared page
It is the problem that every page will be modified (and so copied) if it
contains a reference count so the metadata effectively cannot be shared.
http://lists.laptop.org/pipermail/devel/2007-September/006617.html
Also mentioned in (point 9.)
Hmm, yesterday I executed free after launching some activities and got
this results:
http://lists.laptop.org/pipermail/sugar/2008-March/004650.html
Am I very wrong to think that we can save 3.6MB per python activity instance?
Tomeu
On Fri, Mar 21, 2008 at 7:21 PM, NoiseEHC [EMAIL PROTECTED]
Mitch Bradley wrote:
I think that Update.2 should be about 3 things:
3) Performance
2) Performance
1) Performance
I second that. Update.2 should be about optimizing Sugar and its
dependencies, not adding new features. My 2 cents.
--
Bryan W. Berry
Systems Engineer
OLE Nepal,
On Fri, Mar 21, 2008 at 12:55 PM, Tomeu Vizoso [EMAIL PROTECTED] wrote:
Is still the plan for Update.2 to be about the most urgent needs from
the deployments?
Scott -
what's the release naming scheme? What will the bugfix release post
update.1 be called, versus the next feature release?
On 22.03.2008 00:30, John R.Hogerhuis wrote:
I'd agree with Mitch. Performance, or for us, UI responsiveness, the most
visible and painful issue being start up time of applications is paramount. My
4-year old, with no cushy performant computer experience, loses interest in
the
10 seconds+ it
On 22.03.2008 02:09, Martin Langhoff wrote:
On Fri, Mar 21, 2008 at 8:58 PM, Carl-Daniel Hailfinger
[EMAIL PROTECTED] wrote:
if Windows runs faster
...
once somebody has a child-friendly UI for Windows
You are going from if to when with absolutely no support from
On Fri, 21 Mar 2008, John R.Hogerhuis wrote:
I'd agree with Mitch. Performance, or for us, UI responsiveness, the most
visible and painful issue being start up time of applications is paramount. My
4-year old, with no cushy performant computer experience, loses interest in
the
10 seconds+
14 matches
Mail list logo
