blob: 6c9a7bf1043be74beb97ecd374e07d819370b45d [file] [log] [blame]
<?php
require_once($_SERVER['DOCUMENT_ROOT'] . "/eclipse.org-common/system/app.class.php");
require_once($_SERVER['DOCUMENT_ROOT'] . "/eclipse.org-common/system/nav.class.php");
require_once($_SERVER['DOCUMENT_ROOT'] . "/eclipse.org-common/system/menu.class.php");
$App = new App();
$Nav = new Nav();
$Menu = new Menu();
include($App->getProjectCommon());
# All on the same line to unclutter the user's desktop'
#*****************************************************************************
#
# File : newsNoteworthy.php
#
# Author : Diego Madruga Sandin (dmadruga)
# Date : 2009-05-27
#
# Description: Project New & Noteworthy
#
#
#****************************************************************************
# Begin: page-specific settings. Change these.
$pageTitle = "DSDP&nbsp; - &nbsp;Mobile Tools for Java 1.0.1 &nbsp; (MTJ) &nbsp; New & Noteworthy";
$pageKeywords = "MTJ, New & Noteworthy";
$pageAuthor = "Diego Madruga Sandin";
# Paste your HTML content between the EOHTML markers!
$html = <<<EOHTML
<div id="midcolumn">
<h1>$pageTitle</h1>
<p>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:</p>
<ul>
<li><a href="#editors">Editors</a></li>
<li><a href="#dialogs">Dialogs</a></li>
<li><a href="#properties">Property pages</a></li>
<li><a href="#preference">Preference pages</a></li>
</ul>
<br>
<table
cellpadding="10"
cellspacing="0"
width="100%"
summary="New and noteworthy items">
<colgroup>
<col width="15%">
<col width="85%">
</colgroup>
<tbody>
<!-- ************* Application Descriptor Editor ****************** -->
<tr>
<td colspan="2"><a name="editors"></a>
<div style="font-size: 20px; font-weight: bold;"><br>
Editors</div>
</td>
</tr>
<tr>
<td>
<p align="left"><b>Display errors on Package Explorer</b></p>
</td>
<td>
<p>Errors on the Application Descriptor file are also being displayed in the Package
Explorer.</p>
<p><img
src="images/errorspkg.png"
alt="Display errors on Package Explorer" /></p>
</td>
</tr>
<tr>
<td>
<p align="left"><b>Validation on "MIDlet Jar URL" field</b></p>
</td>
<td>
<p>Field validation of "MIDlet Jar URL" on the Application Descriptor Editor was
included.</p>
<p><img
src="images/errorsjar.png"
alt="Validation on MIDlet Jar URL field" /></p>
</td>
</tr>
<tr>
<td>
<p align="left"><b>New Optional tab</b></p>
</td>
<td>
<p>The Application Descriptor editor now offers a new <b>Optional</b> 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.</p>
<p><img
src="images/jad_editor_optional.png"
alt="Optional Tab" /></p>
</tr>
<tr>
<td>
<p align="left"><b>Set the Default locale</b></p>
</td>
<td>
<p>The Localization Data editor added the ability to specify a Locale to be used as
the default one.</p>
<p><img
src="images/localedetails.png"
alt="Default locale" /></p>
</td>
</tr>
<tr>
<td>
<p align="left"><b>New Entries Table tab</b></p>
</td>
<td>
<p>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.</p>
<p><img
src="images/entriestable.png"
alt="Entries Table Tab" /></p>
</tr>
<tr>
<td>
<p align="left"><b>See errors directly on source</b></p>
</td>
<td>
<p>The Localization Data editor can display errors on the source tab.</p>
<p><img
src="images/errorssrc.png"
alt="Default locale" /></p>
</td>
</tr>
<!-- ********************** DIALOGS *********************** -->
<tr>
<td colspan="2"><a name="dialogs"></a>
<div style="font-size: 20px; font-weight: bold;"><br>
Dialogs</div>
</td>
</tr>
<tr>
<td>
<p align="left"><b>Add to Working Set</b></p>
</td>
<td>
<p>The New MIDlet Project wizard now provides the option to add the newly create
project to a working set.</p>
<p><img
src="images/NewProjectWizardPage.png"
alt="Add to Working Set" /></p>
</td>
</tr>
<tr>
<td>
<p align="left"><b>Enhancements on the New MIDlet Project Wizard</b></p>
</td>
<td>
<p>The New MIDlet Project wizard received a new page where the user can specify more
information for the MIDlet Project.</p>
<p><img
src="images/NewProjectWizardContentPage.png"
alt="Enhancements on the New MIDlet Project Wizard" /></p>
</td>
</tr>
<tr>
<td>
<p align="left"><b>Localize Strings Wizard</b></p>
</td>
<td>
<p>The New Localize Strings Wizard to help the user externalize the application
Strings into the Localization Data file.</p>
<p>In the Package Explorer view, right click the Project folder and select the <strong>Source</strong>
&gt; <strong>Localize Strings...</strong> option.</p>
<p><img
src="images/l10n0.png"
alt="Localize Strings Wizard" /></p>
<p>All externalizable Strings are displayed in the wizard.</p>
<p><img
src="images/l10n.png"
alt="Localize Strings Wizard" /></p>
</td>
</tr>
<tr>
<td>
<p align="left"><b>Match runtime SDKs and devices against installed ones</b></p>
</td>
<td>
<p>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.</p>
<p><img
src="images/match.png"
alt="Enhancements on the New MIDlet Project Wizard" /></p>
</td>
</tr>
<!-- ********************** PROPERTIES *********************** -->
<tr>
<td colspan="2"><a name=properties></a>
<div style="font-size: 20px; font-weight: bold;"><br>
Property pages</div>
</td>
</tr>
<tr>
<td>
<p align="left"><b>Preverification Property Page</b></p>
</td>
<td>
<p>On the the project's Preverification property page the developer is now able to
select 3 types of preverifiers.</p>
<p><img
src="images/preverifier.png"
alt="Preverification Property Page" /></p>
</td>
</tr>
<!-- ********************** PREFERENCES *********************** -->
<tr>
<td colspan="2"><a name=preference></a>
<div style="font-size: 20px; font-weight: bold;"><br>
Preference pages</div>
</td>
</tr>
<tr>
<td>
<p align="left"><b>Proguard Configuration</b></p>
</td>
<td>
<p>The Proguard configuration is now made on the Java ME Preference Page.</p>
<p><img
src="images/proguard.png"
alt="Proguard Configuration" /></p>
</td>
</tr>
<tr>
<td>
<p align="left"><b>Proguard Preverifier Support</b></p>
</td>
<td>
<p>The Proguard Preverifier can now supported and can be set on the Preverification
Preference Page.</p>
<p><img
src="images/proguard2.png"
alt="Proguard Preverifier Support" /></p>
</td>
</tr>
</tbody>
</table>
</div>
EOHTML;
# Generate the web page
$App->AddExtraHtmlHeader('<style type="text/css">
td {
border-top: solid thin black;
}
td table tbody tr td {
border-top: none;
} /* no border for nested tables */
tr {
vertical-align: top;
}
ul {
padding-left: 1.2em;
}
</style>' . "\n");
$App->generatePage($theme, $Menu, $Nav, $pageAuthor, $pageKeywords, $pageTitle, $html);
?>