====================================================================================
Release notes for Series 40 On-Device Debugger 0.2 (Beta) 3 March 2011
====================================================================================
Product Description
===================
The Series 40 On-Device Debugger enables developers to debug Java application
running on a Series 40 device in Eclipse Pulsar and NetBeans IDEs. It provides for
the collection of user level trace with or without an IDE as well.
What's new in the Series 40 On-Device Debugger 0.2 (Beta)
=========================================================
Connection Manager (as implemented in alpha version) has been updated and its
behaviour changed.
Once the device has been connected, the emulator should take care of starting and
stopping the debug session. Please use the IDE's stop button or the device’s red
“end call” key to end an emulator debug session.
Remote attach and Streams are available, as before. Please use End Session in
Connection Manager to stop Streams.
Supported IDEs:
===============
* Eclipse Pulsar for Mobile Java Developers 3.5 or later (http://www.eclipse.org/)
* NetBeans 6.1 or later with the Java ME plug-in (http://www.netbeans.com/).
System Requirements:
====================
Supported Platforms:
* Microsoft™ Windows XP (any version).
* Microsoft™ Windows Vista (any version).
* Microsoft™ Windows 7 (any version).
* Java™ Development Kit 6.0 or later.
Hardware as recommended for the chosen IDE and Series 40 SDKs.
Known problems and limitations in this release
==============================================
1. Comms may be very slow - if possible, use a Class 2 Bluetooth device. This issue
is the next to be fixed.
2. IP over WiFi works, but is too slow to be usable. This is on the to be fixed
list.
3. Some Java Array constructs - Vector Tables and String tables - cannot be opened
in the variable explorer.
This may be from ROMised code only and is under investigation.
4. If you open all the ROMised variables, comms traffic slows down. A suspected
memory issue on devices may be causing GC delays, under investigation.
5. There is no error handling in the Connection Manager - if things go wrong,
Connection Manager will stop working silently. To be fixed in a later release.
Product support and feedback
============================
For product support and feedback, please visit the Series 40 On-Device Debugger
discussion thread at http://discussion.forum.nokia.com/forum/forumdisplay.php?35-
Mobile-Java-Tools-amp-SDKs
Release notes for Series 40 On-Device Debugger 0.2 (Beta) 3 March 2011
====================================================================================
Product Description
===================
The Series 40 On-Device Debugger enables developers to debug Java application
running on a Series 40 device in Eclipse Pulsar and NetBeans IDEs. It provides for
the collection of user level trace with or without an IDE as well.
What's new in the Series 40 On-Device Debugger 0.2 (Beta)
=========================================================
Connection Manager (as implemented in alpha version) has been updated and its
behaviour changed.
Once the device has been connected, the emulator should take care of starting and
stopping the debug session. Please use the IDE's stop button or the device’s red
“end call” key to end an emulator debug session.
Remote attach and Streams are available, as before. Please use End Session in
Connection Manager to stop Streams.
Supported IDEs:
===============
* Eclipse Pulsar for Mobile Java Developers 3.5 or later (http://www.eclipse.org/)
* NetBeans 6.1 or later with the Java ME plug-in (http://www.netbeans.com/).
System Requirements:
====================
Supported Platforms:
* Microsoft™ Windows XP (any version).
* Microsoft™ Windows Vista (any version).
* Microsoft™ Windows 7 (any version).
* Java™ Development Kit 6.0 or later.
Hardware as recommended for the chosen IDE and Series 40 SDKs.
Known problems and limitations in this release
==============================================
1. Comms may be very slow - if possible, use a Class 2 Bluetooth device. This issue
is the next to be fixed.
2. IP over WiFi works, but is too slow to be usable. This is on the to be fixed
list.
3. Some Java Array constructs - Vector Tables and String tables - cannot be opened
in the variable explorer.
This may be from ROMised code only and is under investigation.
4. If you open all the ROMised variables, comms traffic slows down. A suspected
memory issue on devices may be causing GC delays, under investigation.
5. There is no error handling in the Connection Manager - if things go wrong,
Connection Manager will stop working silently. To be fixed in a later release.
Product support and feedback
============================
For product support and feedback, please visit the Series 40 On-Device Debugger
discussion thread at http://discussion.forum.nokia.com/forum/forumdisplay.php?35-
Mobile-Java-Tools-amp-SDKs
No comments:
Post a Comment