View Single Post
Posts: 631 | Thanked: 1,123 times | Joined on Sep 2005 @ Helsinki
#23
Originally Posted by Master of Gizmo View Post
This sounds like you are suggesting to stop development around fremantle specifics until we see the final device. I was tempted to work around those limitations, but i'd really be pissed to see that all this effort was a waste of time if the final device comes out and things will actually be resolved by then.

So the precise question here: Should developers work around those limitations now? Or should they stop working on issues related to the help system and the text selection because nokia will come up with updated sdks/apis once the devices are released.
No, I wasn't trying to suggest to stop development. I more like tried to say that don't jump into conclusions about whether something can be done or not based on some properties of some UI component. For instance, just quickly checking the specs there is a specified way to highlight text in the browser.

Looking at the bug https://bugs.maemo.org/show_bug.cgi?id=4619 "Panning and scrollng are mutually exclusive" says exactly that. Comment #5 "I've been told that the pannableareas 'enabled' property can be used to switch between selection/pan mode." I'm no developer, but I read the bug that you can place a button in the UI to switch the property of that component. (Or does somebody read that in some other way?) In many/most cases you don't need to have text selection available, that's part of the reason why it's not universally available.