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?
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.
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.)