Implementation: (mods move to appropriate thread if this is the wrong place)

First, assume there is no hardware keyboard, and typing can be done via the touchscreen in both landscape and portrait mode.
(It would be a nice aim to be able to use it as a touchscreen only. Personally I prefer a hardare keyboard but the options are nice. Eg. Watching a movie, SMS comes through and you quickly reply "yes" then back to movie)
This means we need onscreen keyboards.
I assume a landscape OSK is already in place. Perhaps even a T9 landscape keyboard. The latter may not get used much but may help in keeping with the conventions for the portrait mode version.
I would think there would be a button (when the OSK is onscreen only) to switch between T9 and full QWERTY. Eg a button that say T9 hen you are using QWERTY and vice versa so switching between the two is simple. Similar to having a 123 button to switch to numbers/symbols.

- a question: how do you bring up the OSK in landscape mode? If it is pressimg a button in a corner like it is for pullimg up the multi-tasking screen, the same can be implemented in portrait to bring up its OSK.

-Auto-rotation seems to be the thing here, but there should be an option to switch it off (the option is there on my N82). Useful if you like to lie on your side in bed watching youtube videos, for example.

-The application should also be able to override ASR if the designer wants it to. Eg. It wasn't designed for portrait mode or landscape mode. This prevents such a program being a garbled mess when turned to another orientation. On my N82 the only thing that doesn't seem to rotate is the homescreen and camera (I think).

-i'm not sure how a rotation animation should be handled, but perhaps there can be a setting for turning the animation off/on for those who don't care for it.

The accelerometre can send a signal as orientation changes which triggers the ASR (if switched on).
I'm not sure how this would be handled from a software point of view. Will it have to 'keep an eye out' for the signal and does it cause bloat in the code?

My thoughts essentially are:
- Nokia need to provide a portrait keyboard which can be switchable from T9 and QWERTY which is then the choice of the user.
- Nokia need to provide information on accelerometre auto-rotation events (possibly already available from the N810 days?).
- ASR can be handled by each individual program to switch UI from portrait or landscape mode, so the desktop does not hapharzadly get garbled in portrait mode, for example.

Someone like Anidel will know better how all this is handled, having read his posts on his program.

I hope my ramblings make some sort of sense!