## What's New in 1.0.1 (MTJ)

This document contains descriptions of some of the more interesting or significant changes made to MTJ for the 1.0.1 release. This release focus mainly in bug fixes and enhancements on the documentation. Besides that, there were three main features added that are listed below: They are grouped into:

- Editors
- Dialogs
- Property pages
- Preference pages

Editors
Display errors on Package Explorer | Errors on the Application Descriptor file are also being displayed in the Package Explorer.
Validation on "MIDlet Jar URL" field | Field validation of "MIDlet Jar URL" on the Application Descriptor Editor was included.
New Optional tab | The Application Descriptor editor now offers a new Optional tab that is used to manage MIDlet suite properties that are defined in the Java ME specification, but which are not required, MIDlets that you want to register on device's push registry and MIDlet suite properties that are related to Over the Air provisioning.
Set the Default locale | The Localization Data editor added the ability to specify a Locale to be used as the default one.
New Entries Table tab | The Localization Data editor now offers a new tab where the user can edit the key values for each locale element. The lines of the table contain the name of the keys followed by the respective values for each locale element.
See errors directly on source | The Localization Data editor can display errors on the source tab.
Dialogs
Add to Working Set | The New MIDlet Project wizard now provides the option to add the newly create project to a working set.
Enhancements on the New MIDlet Project Wizard | The New MIDlet Project wizard received a new page where the user can specify more information for the MIDlet Project.
Localize Strings Wizard | The New Localize Strings Wizard to help the user externalize the application Strings into the Localization Data file. In the Package Explorer view, right click the Project folder and select the Source > Localize Strings... option. All externalizable Strings are displayed in the wizard.
Match runtime SDKs and devices against installed ones | When opening or importing an existing project who's runtime configurations specifies SDKs or devices that are not installed in the current workspace, the user in now able to match them against the installed SDKs and devices in case there are relevant matches. These matches are cached so that it happens automatically with subsequent imports.
Property pages
Preverification Property Page | On the the project's Preverification property page the developer is now able to select 3 types of preverifiers.
Preference pages
Proguard Configuration | The Proguard configuration is now made on the Java ME Preference Page.
Proguard Preverifier Support | The Proguard Preverifier can now supported and can be set on the Preverification Preference Page.