Re: animated vs static UI (cont.)
 

There is no sense to make 2D only hardware accerelator. Rotating,
scaling and texturing items in 2D or 3D does not technicaly
differ more than small fraction. Most of efects are in practice 2D
but we get speed to them with 3D hw.

Re: animated vs static UI (cont.)
 

i hope someone from nokia answers this:

1. Did you guys test fremantle in both resistive and capacitative touch screen hardware?

2.If yes did you find a great deal of difference between the two? In terms of ui response and a smooth experience?

Re: animated vs static UI (cont.)
 

I never said there's should be keyboard shortcuts only. I do enjoy having a menu for seldom used options and, at the same time, suggesting me the shortcut.
(btw: i never ever tried to learn emacs, for quick text editing over ssh I use joe, while for more demanding tasks I prefer a good gui editor or a full-fledged rad ide like delphi or lazarus)

Translation: there will be no way to turn off animations :mad:

Re: animated vs static UI (cont.)
 

I read over and over through the reviews people don't like resistive screen versus capacitive. I understand resistive is good to write using stylus, but most phones including latest touch phone from Nokia N97 don't have stylus, and stylus is good for chinese charcters and hindi and arabic, not for American and European market.

If American market (and not only) wants capacitive display, why Nokia which has hundreds of devices does not make a capacitive version of N900 and N97?

If the animated transitions make the UI more understood and easy to play, why not include them in Maemo, at the very basic API, so all the aplications benefit of it?

Re: animated vs static UI (cont.)
 

I'd hate this. I don't really care if the screen is capacitive or resistive. I want it to be good.

However, multiple versions of the same device increase costs. Which have to get passed on to the consumer. No thanks!

How do you know they're not? The Fremantle transition of greying and blurring the background on opening transient surfaces is got for "free" as part of the API. Effects as windows open and close are similar. Until the complete and final Maemo 5 UI is unveiled (presumably at the device launch), who knows?

We've also not seen the built-in applications for Fremantle - let alone Harmattan - so don't know how many transitionary effects are in use.

Re: animated vs static UI (cont.)
 

If Nokia makes bunch of phones that are pretty similar like E71x, E71, E61 (not to mention E72) why is not creating a "N901 MTouch" which to have finger only (touch only) display = meaning no stylus anymore and this has to be capacitive.

Nokia also has to have a Multi-touch device - so this "N901 MTouch" to be a capacitive multi-touch finger interface. What do you think about this? :)


Talking about animation I want the whole thing, the whole spices:
* flick change
* kinetic scroll
* animation for applications launching - a window to start growing from the rectangle of the touched icon to grow to fill up the screen
* animation for message boxes pop-up - again a window growing.
* animated zoom - for maps, web-pages, etc
* smooth transitions
* screen rotation animation (aniomate the rotatation of the screen with 20 degrees frames)
* multi-touch gestures to be displayed as a trace on the screen

what else? :D

Re: animated vs static UI (cont.)
 

And I actively want to turn off/kill all of the above.

Re: animated vs static UI (cont.)
 

indeed, no need to fight a fingers natural grip when pressed against a surface.

still, its not perfect when you do not live in a area of the world where gloves are not needed for 1/2 or more of the year...

Re: animated vs static UI (cont.)
 

Can we hire Michael Bay to direct UI visual effects for Mer?)

Re: animated vs static UI (cont.)
 

ugh, battery life would be really really bad...