BlackBerry JDE4.7의 개발?

Question

Rim은 BlackBerry Storm을 출시 한 후 새로운 BlackBerry JDE4.7을 출시했습니다. BlackBerry Storm이 이전 버전을 사용하여 작성된 프로그램을 지원합니까? 나는이 버전에 비해이 버전에 많은 변화가 있다고 들었습니다. 그리고 많은 버그가있는 폭풍에 대한 불만이있었습니다.

4.7을 사용하거나 이전 JDE를 계속 사용해야합니까?

감사.

Answer 1

Depends what you want to do. You'll actually get the rotation for free if you've designed your application's layout to be fairly resolution independent. When the device is rotated your layout and sublayout methods will be called again (or if you've just used built-in fields and managers, it's all automatic).

The big things you'll need the 4.7 JDE to do include:

• Responding to specific touch events (events which result in e.g. focus going to a Field, or scrolling, are automatically mapped to the older APIs)
• Detecting device orientation (though again, layout is already taken care of - this is more if you want to use the accelerometer at a low level to e.g. control a game or something)

Bottom line: backwards compatibility is in general very good, RIM has mapped the new touch interface to older APIs in a sensible way, and since the Storm hasn't quite taken off as the iPhone has (most people believe that the Bold and Curve are still better devices), stick with an older SDK unless you're doing a very Storm-specific application.

Answer 2

The Blackberry Storm should support programs created using the previous versions. Occasionally, though, programs will break, whether because of a bug in the new version or a now-fixed bug in the old version.

There had to be a lot of changes in the 4.7 API to support the Storm's new features.

Really, though, you should develop with the lowest JDE you can get away with, to avoid forcing people who might otherwise try your program to update first. On the other hand, of course, if you want to do a rotating interface, you're going to need the 4.7 JDE and the Storm.

Answer 3

Developing with 4.7 does have some issues if you've made any changes whatsoever to the way input is handled. If you've made any custom fields, you'll need to update them and have a different build for 4.7 vs < 4.7. There are more methods on fields, for example moveFocus(int x, int y).

If there's any text input anywhere, you're going to have to ensure that the virtual keyboard doesn't cover up or remove from view anything you need to be visible.

The autorotation of views is also sometimes an issue if you've done something manually on a screen and you don't want that to change during runtime, in which case there is a way to force the application into a particular orientation.

I've also noticed some issues with the simulator at least, when using GaugeField objects, that is, if you focus on a GaugeField, the focus cannot be removed. Not sure if this issue has since been fixed or what, but at least that's the way it is with my simulator.