[maemo-developers] [maemo-developers] non-maemo apps in toolbar

From: Frederic Crozat fred at crozat.net
Date: Wed Jan 11 11:12:52 EET 2006
Le mardi 10 janvier 2006 à 23:00 -0200, Gustavo Sverzut Barbieri a
écrit :
> On 1/10/06, Eero Tamminen <eero.tamminen at movial.fi> wrote:
> > On Mon, Jan 09, 2006 at 09:37:25AM -0200, Gustavo Sverzut Barbieri wrote:
> > > > > To make an input window work in maemo env ( this is different to
> > > > > defualt mb input win handling ) you need to have it set its transiency
> > > > > to the window its entering data for.
> > > >
> > > > I think this would be undesirable as then the application window
> > > > would be resized.  This discussion was mostly about stuff like
> > > > SDL games which don't handle window resizes.  Therefore the
> > > > input method should be above the "application" window, not
> > > > make it to resize.
> > >
> > > seconded.
> > >
> > > Also, if I am right, this could avoid CPU usage in complex programs
> > > like web browser.
> >
> > Battery is affected more how often CPU is used than the "height"
> > of CPU usage spike.  As input method comes & resizes application
> > window only on user input, it's not significant from the battery
> > usage point of view.
> 
> I'm not taking battery in account, just the perceived slowness to
> resize/re-render the whole screen. I still don't have the device, but
> from what I've read, it takes some time to open the vkb for the first
> time due Opera's slow -rendering... or I misunderstood?

This bug was not present in the initial firmware (2005.40-2 IIRC), it
was introduced in the first firmware update and was not fixed since.

The desktop slow rendering at initial startup was also not present in
the initial firmware.

-- 
Frederic Crozat <fred at crozat.net>


More information about the maemo-developers mailing list