Added detail in the comments of X-Term and Web in the 1st party applications for the portrait compatibility wiki.

Anyway, back to this: if forcedrotation is only meant to be a tool, you'll still leave it in as a usable option, right? Or will it eventually be pulled out? Personally, I think the eventual end result on the N900 will end up being, for a lot of users, that we have system-wide portrait support anyway - and this, while it might be intended as a tool, basically does most of the task already - actually, I really feel that at this point, creating a user tweakable blacklist of "don't rotate" apps would be far better, in my opinion. But I suppose that's not really CSSU business as of yet.

*Shrug*

My opinion is though, your last two CSSU updates both made portrait functionality, whether that was the intent, and have presented a rather good view of how Hildon would feel if this Ctrl-Shift-R mess was deprecated and autorotation became the norm. It should be possible for apps to still have user configurable options to lock them to either portrait or landscape, but I don't see why the above can't be the 'norm'. Just make it still possible for the Ctrl+Shift+R combo to have a toggle effect, but beyond that, I don't see why it can't be made the norm.

The fact that apps that were built before portrait auto-rotation was common and thus don't support it, in my mind, isn't a good reason to throw out the newer and better model, or to hold back portrait support when at the end of the day, there's no reason most of those apps didn't have portrait support to begin with other than the fact that portrait mode wasn't an option at first.

I guess the point of this sleep deprived rant is that it sounds like the future plan is something of a reversion to a default-rotation-off-unless-pre-programmed-that-way-with-an-auto-rotate-on-flag-in-the-code approach. And I just don't see a good reason for that. It is far more effective, I think, to make non-auto-rotation a conscious choice for developers if they wish to hard-code non-auto-rotation into the program, and barring that, let things auto rotate, and give users some built-in 'lock' system built in to Hildon Desktop itself to force specific apps into one orientation or the other only if they so chose.

A, it puts the control back into the user, and B, it's more future proof. As I said, you're making strides in making Hildon functionally portrait capable, and just because some of the older apps still suck at portrait, doesn't mean the norm should be not-auto-rotate.

- Edit -

Seems that my changes were in the wiki page originally made, not the one Jaffa placed under development. Personally, I think it should've been outside there, but linked to from CSSU development, actually, because whether or not an app works well in portrait seems to me to be a more general thing, than just the CSSU specifically. (Though they obviously are significantly linked.)

- Edit 2 -

Oh it's two slightly different pages; one specifically built-into-CSSU, the other still being the in-general one. NVM.