[maemo-developers] [maemo-developers] RFC: Qtopia Nokia N770 (maemo) porting layer
From: Kalle Vahlman kalle.vahlman at gmail.comDate: Wed Nov 9 11:13:54 EET 2005
- Previous message: [maemo-developers] RFC: Qtopia Nokia N770 (maemo) porting layer
- Next message: [maemo-developers] pressure information
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
2005/11/9, Clemens Eisserer <linuxhippy at gmail.com>: > I am looking foreward when Maemo will migrate to 2.8 and the whole > cairo overhead will be there (since cairo has an FP api and Maemo > doesn't use anything which canno't be done accerlated which is now > done in software). It probably won't unless magic happens with Cairo. I've run some tests and it's out-of-the-question without any special tricks at least. Although my tests didn't exclusively prove that it's the FP api that kills it (it crawled in an area that should not have anything to do with FP AFAIK). I don't think it's feasible for Maemo to start requiring a FPU either, the non-FPU ARMs are too popular in embedded systems. OTOH, nothing prevents replacing the Gtk+ for systems that have an FPU (barring incompatible patches, but those are being migrated where possible). > > Same goes for TextView too. > Right, thats why I installed the xterminal on my 770 of course. > But that would make a difference for the user, using fox (or whatever) > won't - the user would only notice that scolling / redrawing is faster > ;-) User would notice that Fox looks butt-ugly :) It's easy to say "or whatever", but you'd really need to prove the "or whatever" to be worth it. Gtk+ seems to do well enough on the machine, without major drawbacks (if there were, it wouldn't be used, right?). It's not like Gtk+ was chosen on a whim (I hope ;). -- Kalle Vahlman, zuh at iki.fi Powered by http://movial.fi
- Previous message: [maemo-developers] RFC: Qtopia Nokia N770 (maemo) porting layer
- Next message: [maemo-developers] pressure information
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]