01-05-2009, 07:52 PM
Join Date: Apr 2008
Post Thanks: 0
Thanked 0 Times in 0 Posts
| | Storm Compatibility Mode and other bad stuff
Please Login to Remove!
Why have Compatibility Mode? Shouldn't apps 'just work' without forcing us developers to jump through hoops, download and install JDE 4.7, recompile, offer two separate installs etc? Why doesn't the Storm Simulator run my app in Compatibility Mode so that I can see what my customers are seeing? When the app is in Compatibility Model it us unusable with its smaller screen (blue border), keyboard always visible, etc - so why have one?
Sorry RIM, but it sure seems that your developers screwed up here big time - definitely broke the compatibility, given the iPhone and Windows Mobile another advantage.
Also, how about a white paper discussing what we need to do to 'Storminize' our apps? Is there one? e.g. Must we add CONSUME_CLICK to Buttons? Must we tweak the JAD by adding the two compatibility mode lines? Do we have to compile using JDE 4.7 or can we compile in 4.2 or 4.3 and just tweak the JAD? In non-compatibility mode will buttons work, can lists scroll by dragging etc.
To me, sorry for being blunt, but RIM have dropped the ball in the implementation and in the developer support for the Storm transition. In addition, I have heard of many customers returning their Storms - one reason being that apps don't work well (re: Compatibility Mode) and that their Storm locks up etc (the huge memory leak I reported here earlier with no fix in sight).
What say you RIM?