04-07-2010 11:48 AM
What is the diff from the first JDE 5.0 release?
I notice the file name for 5.0 is the same as the first pre-release but the current version is dated 3-31-2010
04-07-2010 11:55 AM
I haven't figured out how to use the Hot Swap with the new 5.0 JDE.
In Eclipse on the other hand it works like a charm though. ![]()
I used to always debug with the JDE because I'm on a Windows 7 64bit BUT I can say that it works great with the new plugin (1.1.2) including the hot swap. It might not be supported but it works!
I used the Eclipse updater to update the plugin and component pack.
Excellent job, RIM!
04-07-2010 11:55 AM
> the Release Notes said that you needed to update the pointer to 5.0.0.25 to use the new pack
Ok so at least I did that part correctly ![]()
I have got the simulator to run now (weirdly without any errors at all, not even the missing debug info one). I tried Clean Simulator from the blackberry menu but that doesn't appear to do anything. So I went to \plugins\net.rim.ejde.componentpack5.0.0_5.0.0.25\
04-07-2010 11:58 AM
04-07-2010 12:05 PM
In Eclipse, leave the simulator running, change some code, and then click on the debug button again (or select the debugger setting that you are currently running).
It should show a Packaging Dialog and you will see in the Simulator how the debugger reattaches.
I dont know for sure but I think this is how it works. It only takes seconds though to switch out the build and the simulator is not closed in between.
I hope this helps.
04-07-2010 12:09 PM
04-07-2010 01:06 PM - edited 04-07-2010 01:09 PM
Another noticable and great change is Preprocessor flags that are predefined based on which SDK you pick.
I removed all my flags that indicated which OS version I was targetting and am now using this exclusively and it works great.
The flags are below (flags only applicable if you have each version of the SDK installed):
BlackBerrySDK4.5.0
BlackBerrySDK4.6.0
BlackBerrySDK4.6.1
BlackBerrySDK4.7.0
BlackBerrySDK4.5.0
So no need to go into your XML descriptor to edit your preprocessor flags (or project properties for the 1.0 folks). If you use the above, when you target a new OS, your code will preprocess based on the flags set.
Cool feature that I was hoping would make it in.
04-07-2010 02:52 PM
@austin: In the release notes it also says that if you upgrade the plugin from Eclipse the clean simulator button will not work.
04-07-2010 03:49 PM
i tried plugin with windows 7 but it dont works
.
04-07-2010 05:39 PM