Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » DSDP - Mobile Tools for Java (MTJ) » Scenario additions
Scenario additions [message #239] Mon, 24 October 2005 04:48 Go to next message
Eclipse User
Originally posted by: thomas.bailey.sonyericsson.com

I think we are missing some usecases, specifically for Craigs additions:

- Export Ant/Antenna build files
- Manage Available Devices
- Preprocess source code
- Batch Build source code

Minna / Craig are you working on these ? volunteers needed ?

/T
Re: Scenario additions [message #311 is a reply to message #239] Wed, 26 October 2005 05:57 Go to previous messageGo to next message
Mika Hoikkala is currently offline Mika Hoikkala
Messages: 40
Registered: July 2009
Member
FYI

Minna is having vacation.
But when she will come back she will continue to work with the use cases.

mho

Thomas Bailey wrote:
> I think we are missing some usecases, specifically for Craigs additions:
>
> - Export Ant/Antenna build files
> - Manage Available Devices
> - Preprocess source code
> - Batch Build source code
>
> Minna / Craig are you working on these ? volunteers needed ?
>
> /T
>
Re: Scenario additions [message #1337 is a reply to message #239] Wed, 26 October 2005 15:43 Go to previous messageGo to next message
Eclipse User
Originally posted by: csetera.spss.com

I'm collecting some information from the other folks on the EclipseME
team and can put together a skeleton for some of this. I won't get to
it until at least this weekend. Hopefully that won't be a problem.

Thomas Bailey wrote:
> I think we are missing some usecases, specifically for Craigs additions:
>
> - Export Ant/Antenna build files
> - Manage Available Devices
> - Preprocess source code
> - Batch Build source code
>
> Minna / Craig are you working on these ? volunteers needed ?
>
> /T
>
Re: Scenario additions [message #1392 is a reply to message #239] Sun, 30 October 2005 13:36 Go to previous message
Eclipse User
Originally posted by: seterajunk.charter.net

This is a multi-part message in MIME format.
--------------090804010704060503070107
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 7bit

I've attached a first cut at the new scenarios that myself and members
of the EclipseME team think are important for MTJ. These are initial
proposals and meant to inspire discussion on these issues and the
appropriate implementation. I apologize for the length of the document,
but I felt it was important to provide some context for these new scenarios

The types of tools discussed in this document are one of the next major
things that EclipseME is planning to tackle.

Thanks,
Craig

Thomas Bailey wrote:
> I think we are missing some usecases, specifically for Craigs additions:
>
> - Export Ant/Antenna build files
> - Manage Available Devices
> - Preprocess source code
> - Batch Build source code
>
> Minna / Craig are you working on these ? volunteers needed ?
>
> /T
>

--------------090804010704060503070107
Content-Type: text/html; charset=WINDOWS-1252;
name="mtj_multidevice.html"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
filename="mtj_multidevice.html"

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="CONTENT-TYPE" CONTENT="text/html; charset=windows-1252">
<TITLE></TITLE>
<META NAME="GENERATOR" CONTENT="OpenOffice.org 2.0 (Win32)">
<META NAME="AUTHOR" CONTENT="Craig Setera">
<META NAME="CREATED" CONTENT="20051029;13335500">
<META NAME="CHANGEDBY" CONTENT="Craig Setera">
<META NAME="CHANGED" CONTENT="20051030;12273700">
<STYLE>
<!--
@page { size: 8.5in 11in; margin: 0.79in }
P { margin-bottom: 0.08in }
H2 { margin-bottom: 0.08in }
H2.western { font-family: "Arial", sans-serif; font-size: 14pt; font-style: italic }
H2.cjk { font-size: 14pt; font-style: italic }
H2.ctl { font-size: 14pt; font-style: italic }
H3 { margin-bottom: 0.08in }
H3.western { font-family: "Arial", sans-serif }
-->
</STYLE>
</HEAD>
<BODY LANG="en-US" DIR="LTR">
<H2 CLASS="western">Problem Statement</H2>
<P>J2ME or Java ME is ripe with device fragmentation. Add to that
the limited memory available for midlet suites, it is imperative that
developer tools provide developers with the help necessary to develop
midlets for a wide range of devices. A sampling of the areas in
which fragmentation occurs:</P>
<UL>
<LI><P>Available API's</P>
<LI><P>Screen size and color depth</P>
<LI><P>Maximum allowable jar size (64k up to 200k)</P>
<LI><P>Maximum runtime memory (200k up to multiple megabytes)</P>
<LI><P>Processor speed</P>
</UL>
<P>In addition, localization generally needs to be performed at build
time to avoid the memory cost of having multiple copies of the
localizable resources for each language.</P>
<H2 CLASS="western">Necessary Tools</H2>
<P>In order to support developers, there needs to be a number of
tools available which may be involved in the ultimate solution.</P>
<H3 CLASS="western">Device Management</H3>
<P>Device management in this case goes beyond the simple &ldquo;Installed
JREs&rdquo; functionality currently available in the Eclipse JDT.
For one thing, it is much more common for a developer to have a large
number of devices defined than &ldquo;Installed JREs&rdquo;. Each
device brings with it a set of libraries, available security domains
and other device information. In addition, some devices such as the
generic devices provided by the Sun Wireless Toolkit, provide a set
of optional profile libraries that may be enabled and disabled for
that device. Device management needs to include the ability to
import devices, remove defined devices and create derived devices
that include optional libraries.</P>
<H3 CLASS="western">Code Management</H3>
<P>In many cases, it becomes necessary to fill in the blanks between
two disparate devices. For example, building a skeleton
implementation of the MIDP 2.0 CustomItem class for use on a MIDP 1.0
device.
</P>
<P>Due to the disparity between the devices, there will often be a
need for one-off implementations for each project. This type of
disparity can be managed using a combination of conditional
compilation/preprocessing of source files as well as allowing for
alternative source folders which may be switched based on the device.</P>
<P>Over time, an organization will most likely also collect a library
of functionality which may be applied and reapplied to each new
project. These libraries may be managed by allowing for alternative
prerequisite projects which may be switched based on the selected
device.</P>
<P>In summary, code management should include the following
functionality:</P>
<UL>
<LI><P>Multiple prerequisite project references, selectable based on
device.</P>
<LI><P>Multiple source folders, switchable based on device.</P>
<LI><P>Conditional compilation/preprocessing.</P>
</UL>
<H3 CLASS="western">Resource Management</H3>
<P>Resource management is necessary in order to manage localizable
text as well as resources such as images. The ability to have
switchable prerequisite projects and source folders should provide
the necessary support to appropriately manage resources.</P>
<H3 CLASS="western">Configuration Management</H3>
<P>The ability to group all of above tools into a coherent
&ldquo;configuration&rdquo; is an absolute necessity. Managing
devices, prerequisite projects, alternative source folders and
conditional compilation settings one by one would be painful at best.
What is needed is the ability to group together all of these
settings into a higher level configuration that may be applied to a
project. Each configuration should provide the ability to control
the following items:</P>
<UL>
<LI><P>Default device</P>
<LI><P>Default device/emulator parameters (for instance to configure
maximum memory)</P>
<LI><P>Associated source folders</P>
<LI><P>Associated prerequisite projects</P>
<LI><P>Conditional compilation symbol definitions</P>
</UL>
<H3 CLASS="western">Build Support</H3>
<P>In addition to the needs for management of device fragmentation,
many organizations will have build requirements that extend beyond
those currently provided by the development environment.</P>
<P>In many cases, a mobile application is backed by a J2EE server
application. In these cases, it is necessary to allow the build of
the mobile application to be integrated with the build of the server
application. Ant build scripts are the logical choice for allowing
the mobile application build to be integrated into another build.</P>
<P>Each project is likely to be associated with a number of
individual configuration definitions. Building a project must allow
for the ability to build a series of configurations in a single
batch.</P>
<H2 CLASS="western">User Scenarios</H2>
<H3 CLASS="western">Add Devices</H3>
<UL>
<LI><P>User opens Device Management section of workbench preferences</P>
<LI><P>User chooses to add new devices.</P>
<LI><P>User is prompted for a root file system directory in which to
search.</P>
<LI><P>System recursively searches through file system directories
searching for known devices.
</P>
<UL>
<LI><P>(Plug-ins to framework must be given the chance to identify
and &ldquo;own&rdquo; devices)</P>
</UL>
<LI><P>User is prompted with a list of found devices. All devices
found are initially selected.</P>
<LI><P>User deselects devices that they are not interested in having
available.</P>
<LI><P>User presses OK to leave dialog and devices are added to
system.</P>
</UL>
<H3 CLASS="western">Create Mobile Project</H3>
<UL>
<LI><P>Similar to previous project creation use case, except a
device is selected as the basis for the project.</P>
</UL>
<H3 CLASS="western">Select Project Device</H3>
<UL>
<LI><P>User opens project properties.</P>
<LI><P>User selects available device for the project.</P>
<LI><P>User applies changes.</P>
<LI><P>Project is rebuilt based on new settings.</P>
</UL>
<H3 CLASS="western">Remove Devices</H3>
<UL>
<LI><P>User opens Device Management</P>
<LI><P>User selects all devices to remove</P>
<LI><P>User selects &ldquo;Delete&rdquo; key or &ldquo;Remove&rdquo;
button</P>
<LI><P>User is prompted to confirm removal</P>
<LI><P>Devices are removed</P>
<UL>
<LI><P>What happens to projects associated with this device?</P>
</UL>
</UL>
<H3 CLASS="western">Create New Configuration</H3>
<UL>
<LI><P>User opens Configuration Management interface in workbench
preferences</P>
<LI><P>User chooses to create a new Configuration</P>
<LI><P>User specifies a name for the new configuration</P>
<LI><P>User specifies any/all of the following:</P>
<UL>
<LI><P>Default device</P>
<LI><P>Default device/emulator parameters (for instance to
configure maximum memory)</P>
<LI><P>Associated source folders</P>
<LI><P>Associated prerequisite projects</P>
<LI><P>Conditional compilation symbol definitions</P>
</UL>
<LI><P>User applies changes to accept new configuration</P>
</UL>
<H3 CLASS="western">Select Project Configuration</H3>
<UL>
<LI><P>User opens project properties.</P>
<LI><P>User selects available project configuration for the project.</P>
<LI><P>User applies changes.</P>
<LI><P>Project is rebuilt based on new settings.</P>
<UL>
<LI><P>Preprocessing is done to match newly selected symbol
definitions</P>
<LI><P>Project libraries and source folders are set to match newly
selected configuration</P>
<LI><P>Standard JDT Compiler is invoked to build resulting source
code</P>
</UL>
</UL>
<H3 CLASS="western">Edit Configuration</H3>
<UL>
<LI><P>User opens Configuration Management interface in workbench
preferences</P>
<LI><P>User chooses a Configuration to edit</P>
<UL>
<LI><P>Double-click existing configuration or</P>
<LI><P>Select configuration and press &ldquo;Edit..&rdquo; button</P>
</UL>
<LI><P>User edits any/all of the following:</P>
<UL>
<LI><P>Default device</P>
<LI><P>Default device/emulator parameters (for instance to
configure maximum memory)</P>
<LI><P>Associated source folders</P>
<LI><P>Associated prerequisite projects</P>
<LI><P>Conditional compilation symbol definitions</P>
</UL>
<LI><P>User applies changes to accept configuration changes</P>
<LI><P>Projects associated with updated configuration will be
rebuilt</P>
</UL>
<H3 CLASS="western">Remove Configuration</H3>
<UL>
<LI><P>User opens Configuration Management</P>
<LI><P>User selects all configurations to remove</P>
<LI><P>User selects &ldquo;Delete&rdquo; key or &ldquo;Remove&rdquo;
button</P>
<LI><P>User is prompted to confirm removal</P>
<LI><P>Configurations are removed</P>
<UL>
<LI><P>What happens to projects associated with this device?</P>
</UL>
</UL>
<H3 CLASS="western">Add Preprocessor Block to Source Manually</H3>
<UL>
<LI><P>User opens Java source code</P>
<LI><P>User enters appropriate preprocessor begin and end statements</P>
<LI><P>If referenced symbol is inactive/undefined, code between
begin and end are automatically commented out</P>
</UL>
<H3 CLASS="western">Add Preprocessor Block to Source via Menu</H3>
<UL>
<LI><P>User opens Java source code</P>
<LI><P>User selects block of code</P>
<LI><P>User opens context menu and selects Source -&gt; Surround
with #ifdef (or similar)</P>
<UL>
<LI><P>There could be any number of source editor context menu
options to introduce conditional statements into the source</P>
</UL>
<LI><P>Appropriate begin and end statements are added and block
content is commented as appropriate</P>
</UL>
<H3 CLASS="western">Export Ant Build Files</H3>
<UL>
<LI><P>User selects mobile project in Resource Navigator or Package
Explorer</P>
<LI><P>User opens context menu</P>
<LI><P>User selects Mobile Tools -&gt; Export Ant Build Files</P>
<LI><P>Build files are exported</P>
<UL>
<LI><P>Antenna support is one reasonable option here</P>
<LI><P>Another option would be to use the headless antRunner
support within Eclipse and a set of new tasks to tie into the
Eclipse and Mobile Tools support</P>
</UL>
</UL>
<H3 CLASS="western">Execute Batch Build</H3>
<UL>
<LI><P>User selects mobile project in Resource Navigator or Package
Explorer</P>
<LI><P>User opens context menu</P>
<LI><P>User selects Mobile Tools -&gt; Batch Build...</P>
<LI><P>Batch build dialog is displayed showing all available
configurations</P>
<UL>
<LI><P>When first opened, no configurations will be selected</P>
<LI><P>When later opened, previously selected configurations will
be selected</P>
</UL>
<LI><P>User selects configurations to be built</P>
<LI><P>User selects &ldquo;OK&rdquo; button to launch batch build</P>
<LI><P>For each configuration selected:</P>
<UL>
<LI><P>Package will be built using configuration settings</P>
<LI><P>Output will be placed in &lt;project
root&gt;/build/&lt;configuration name&gt;</P>
</UL>
</UL>
<P><BR><BR>
</P>
</BODY>
</HTML>
--------------090804010704060503070107--
Re: Scenario additions [message #560844 is a reply to message #239] Wed, 26 October 2005 05:57 Go to previous message
Mika Hoikkala is currently offline Mika Hoikkala
Messages: 40
Registered: July 2009
Member
FYI

Minna is having vacation.
But when she will come back she will continue to work with the use cases.

mho

Thomas Bailey wrote:
> I think we are missing some usecases, specifically for Craigs additions:
>
> - Export Ant/Antenna build files
> - Manage Available Devices
> - Preprocess source code
> - Batch Build source code
>
> Minna / Craig are you working on these ? volunteers needed ?
>
> /T
>
Re: Scenario additions [message #560923 is a reply to message #239] Wed, 26 October 2005 15:43 Go to previous message
Craig Setera is currently offline Craig Setera
Messages: 54
Registered: July 2009
Member
I'm collecting some information from the other folks on the EclipseME
team and can put together a skeleton for some of this. I won't get to
it until at least this weekend. Hopefully that won't be a problem.

Thomas Bailey wrote:
> I think we are missing some usecases, specifically for Craigs additions:
>
> - Export Ant/Antenna build files
> - Manage Available Devices
> - Preprocess source code
> - Batch Build source code
>
> Minna / Craig are you working on these ? volunteers needed ?
>
> /T
>
Re: Scenario additions [message #561054 is a reply to message #239] Sun, 30 October 2005 13:36 Go to previous message
Craig Setera is currently offline Craig Setera
Messages: 54
Registered: July 2009
Member
This is a multi-part message in MIME format.
--------------090804010704060503070107
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 7bit

I've attached a first cut at the new scenarios that myself and members
of the EclipseME team think are important for MTJ. These are initial
proposals and meant to inspire discussion on these issues and the
appropriate implementation. I apologize for the length of the document,
but I felt it was important to provide some context for these new scenarios

The types of tools discussed in this document are one of the next major
things that EclipseME is planning to tackle.

Thanks,
Craig

Thomas Bailey wrote:
> I think we are missing some usecases, specifically for Craigs additions:
>
> - Export Ant/Antenna build files
> - Manage Available Devices
> - Preprocess source code
> - Batch Build source code
>
> Minna / Craig are you working on these ? volunteers needed ?
>
> /T
>

--------------090804010704060503070107
Content-Type: text/html; charset=WINDOWS-1252;
name="mtj_multidevice.html"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
filename="mtj_multidevice.html"

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="CONTENT-TYPE" CONTENT="text/html; charset=windows-1252">
<TITLE></TITLE>
<META NAME="GENERATOR" CONTENT="OpenOffice.org 2.0 (Win32)">
<META NAME="AUTHOR" CONTENT="Craig Setera">
<META NAME="CREATED" CONTENT="20051029;13335500">
<META NAME="CHANGEDBY" CONTENT="Craig Setera">
<META NAME="CHANGED" CONTENT="20051030;12273700">
<STYLE>
<!--
@page { size: 8.5in 11in; margin: 0.79in }
P { margin-bottom: 0.08in }
H2 { margin-bottom: 0.08in }
H2.western { font-family: "Arial", sans-serif; font-size: 14pt; font-style: italic }
H2.cjk { font-size: 14pt; font-style: italic }
H2.ctl { font-size: 14pt; font-style: italic }
H3 { margin-bottom: 0.08in }
H3.western { font-family: "Arial", sans-serif }
-->
</STYLE>
</HEAD>
<BODY LANG="en-US" DIR="LTR">
<H2 CLASS="western">Problem Statement</H2>
<P>J2ME or Java ME is ripe with device fragmentation. Add to that
the limited memory available for midlet suites, it is imperative that
developer tools provide developers with the help necessary to develop
midlets for a wide range of devices. A sampling of the areas in
which fragmentation occurs:</P>
<UL>
<LI><P>Available API's</P>
<LI><P>Screen size and color depth</P>
<LI><P>Maximum allowable jar size (64k up to 200k)</P>
<LI><P>Maximum runtime memory (200k up to multiple megabytes)</P>
<LI><P>Processor speed</P>
</UL>
<P>In addition, localization generally needs to be performed at build
time to avoid the memory cost of having multiple copies of the
localizable resources for each language.</P>
<H2 CLASS="western">Necessary Tools</H2>
<P>In order to support developers, there needs to be a number of
tools available which may be involved in the ultimate solution.</P>
<H3 CLASS="western">Device Management</H3>
<P>Device management in this case goes beyond the simple &ldquo;Installed
JREs&rdquo; functionality currently available in the Eclipse JDT.
For one thing, it is much more common for a developer to have a large
number of devices defined than &ldquo;Installed JREs&rdquo;. Each
device brings with it a set of libraries, available security domains
and other device information. In addition, some devices such as the
generic devices provided by the Sun Wireless Toolkit, provide a set
of optional profile libraries that may be enabled and disabled for
that device. Device management needs to include the ability to
import devices, remove defined devices and create derived devices
that include optional libraries.</P>
<H3 CLASS="western">Code Management</H3>
<P>In many cases, it becomes necessary to fill in the blanks between
two disparate devices. For example, building a skeleton
implementation of the MIDP 2.0 CustomItem class for use on a MIDP 1.0
device.
</P>
<P>Due to the disparity between the devices, there will often be a
need for one-off implementations for each project. This type of
disparity can be managed using a combination of conditional
compilation/preprocessing of source files as well as allowing for
alternative source folders which may be switched based on the device.</P>
<P>Over time, an organization will most likely also collect a library
of functionality which may be applied and reapplied to each new
project. These libraries may be managed by allowing for alternative
prerequisite projects which may be switched based on the selected
device.</P>
<P>In summary, code management should include the following
functionality:</P>
<UL>
<LI><P>Multiple prerequisite project references, selectable based on
device.</P>
<LI><P>Multiple source folders, switchable based on device.</P>
<LI><P>Conditional compilation/preprocessing.</P>
</UL>
<H3 CLASS="western">Resource Management</H3>
<P>Resource management is necessary in order to manage localizable
text as well as resources such as images. The ability to have
switchable prerequisite projects and source folders should provide
the necessary support to appropriately manage resources.</P>
<H3 CLASS="western">Configuration Management</H3>
<P>The ability to group all of above tools into a coherent
&ldquo;configuration&rdquo; is an absolute necessity. Managing
devices, prerequisite projects, alternative source folders and
conditional compilation settings one by one would be painful at best.
What is needed is the ability to group together all of these
settings into a higher level configuration that may be applied to a
project. Each configuration should provide the ability to control
the following items:</P>
<UL>
<LI><P>Default device</P>
<LI><P>Default device/emulator parameters (for instance to configure
maximum memory)</P>
<LI><P>Associated source folders</P>
<LI><P>Associated prerequisite projects</P>
<LI><P>Conditional compilation symbol definitions</P>
</UL>
<H3 CLASS="western">Build Support</H3>
<P>In addition to the needs for management of device fragmentation,
many organizations will have build requirements that extend beyond
those currently provided by the development environment.</P>
<P>In many cases, a mobile application is backed by a J2EE server
application. In these cases, it is necessary to allow the build of
the mobile application to be integrated with the build of the server
application. Ant build scripts are the logical choice for allowing
the mobile application build to be integrated into another build.</P>
<P>Each project is likely to be associated with a number of
individual configuration definitions. Building a project must allow
for the ability to build a series of configurations in a single
batch.</P>
<H2 CLASS="western">User Scenarios</H2>
<H3 CLASS="western">Add Devices</H3>
<UL>
<LI><P>User opens Device Management section of workbench preferences</P>
<LI><P>User chooses to add new devices.</P>
<LI><P>User is prompted for a root file system directory in which to
search.</P>
<LI><P>System recursively searches through file system directories
searching for known devices.
</P>
<UL>
<LI><P>(Plug-ins to framework must be given the chance to identify
and &ldquo;own&rdquo; devices)</P>
</UL>
<LI><P>User is prompted with a list of found devices. All devices
found are initially selected.</P>
<LI><P>User deselects devices that they are not interested in having
available.</P>
<LI><P>User presses OK to leave dialog and devices are added to
system.</P>
</UL>
<H3 CLASS="western">Create Mobile Project</H3>
<UL>
<LI><P>Similar to previous project creation use case, except a
device is selected as the basis for the project.</P>
</UL>
<H3 CLASS="western">Select Project Device</H3>
<UL>
<LI><P>User opens project properties.</P>
<LI><P>User selects available device for the project.</P>
<LI><P>User applies changes.</P>
<LI><P>Project is rebuilt based on new settings.</P>
</UL>
<H3 CLASS="western">Remove Devices</H3>
<UL>
<LI><P>User opens Device Management</P>
<LI><P>User selects all devices to remove</P>
<LI><P>User selects &ldquo;Delete&rdquo; key or &ldquo;Remove&rdquo;
button</P>
<LI><P>User is prompted to confirm removal</P>
<LI><P>Devices are removed</P>
<UL>
<LI><P>What happens to projects associated with this device?</P>
</UL>
</UL>
<H3 CLASS="western">Create New Configuration</H3>
<UL>
<LI><P>User opens Configuration Management interface in workbench
preferences</P>
<LI><P>User chooses to create a new Configuration</P>
<LI><P>User specifies a name for the new configuration</P>
<LI><P>User specifies any/all of the following:</P>
<UL>
<LI><P>Default device</P>
<LI><P>Default device/emulator parameters (for instance to
configure maximum memory)</P>
<LI><P>Associated source folders</P>
<LI><P>Associated prerequisite projects</P>
<LI><P>Conditional compilation symbol definitions</P>
</UL>
<LI><P>User applies changes to accept new configuration</P>
</UL>
<H3 CLASS="western">Select Project Configuration</H3>
<UL>
<LI><P>User opens project properties.</P>
<LI><P>User selects available project configuration for the project.</P>
<LI><P>User applies changes.</P>
<LI><P>Project is rebuilt based on new settings.</P>
<UL>
<LI><P>Preprocessing is done to match newly selected symbol
definitions</P>
<LI><P>Project libraries and source folders are set to match newly
selected configuration</P>
<LI><P>Standard JDT Compiler is invoked to build resulting source
code</P>
</UL>
</UL>
<H3 CLASS="western">Edit Configuration</H3>
<UL>
<LI><P>User opens Configuration Management interface in workbench
preferences</P>
<LI><P>User chooses a Configuration to edit</P>
<UL>
<LI><P>Double-click existing configuration or</P>
<LI><P>Select configuration and press &ldquo;Edit..&rdquo; button</P>
</UL>
<LI><P>User edits any/all of the following:</P>
<UL>
<LI><P>Default device</P>
<LI><P>Default device/emulator parameters (for instance to
configure maximum memory)</P>
<LI><P>Associated source folders</P>
<LI><P>Associated prerequisite projects</P>
<LI><P>Conditional compilation symbol definitions</P>
</UL>
<LI><P>User applies changes to accept configuration changes</P>
<LI><P>Projects associated with updated configuration will be
rebuilt</P>
</UL>
<H3 CLASS="western">Remove Configuration</H3>
<UL>
<LI><P>User opens Configuration Management</P>
<LI><P>User selects all configurations to remove</P>
<LI><P>User selects &ldquo;Delete&rdquo; key or &ldquo;Remove&rdquo;
button</P>
<LI><P>User is prompted to confirm removal</P>
<LI><P>Configurations are removed</P>
<UL>
<LI><P>What happens to projects associated with this device?</P>
</UL>
</UL>
<H3 CLASS="western">Add Preprocessor Block to Source Manually</H3>
<UL>
<LI><P>User opens Java source code</P>
<LI><P>User enters appropriate preprocessor begin and end statements</P>
<LI><P>If referenced symbol is inactive/undefined, code between
begin and end are automatically commented out</P>
</UL>
<H3 CLASS="western">Add Preprocessor Block to Source via Menu</H3>
<UL>
<LI><P>User opens Java source code</P>
<LI><P>User selects block of code</P>
<LI><P>User opens context menu and selects Source -&gt; Surround
with #ifdef (or similar)</P>
<UL>
<LI><P>There could be any number of source editor context menu
options to introduce conditional statements into the source</P>
</UL>
<LI><P>Appropriate begin and end statements are added and block
content is commented as appropriate</P>
</UL>
<H3 CLASS="western">Export Ant Build Files</H3>
<UL>
<LI><P>User selects mobile project in Resource Navigator or Package
Explorer</P>
<LI><P>User opens context menu</P>
<LI><P>User selects Mobile Tools -&gt; Export Ant Build Files</P>
<LI><P>Build files are exported</P>
<UL>
<LI><P>Antenna support is one reasonable option here</P>
<LI><P>Another option would be to use the headless antRunner
support within Eclipse and a set of new tasks to tie into the
Eclipse and Mobile Tools support</P>
</UL>
</UL>
<H3 CLASS="western">Execute Batch Build</H3>
<UL>
<LI><P>User selects mobile project in Resource Navigator or Package
Explorer</P>
<LI><P>User opens context menu</P>
<LI><P>User selects Mobile Tools -&gt; Batch Build...</P>
<LI><P>Batch build dialog is displayed showing all available
configurations</P>
<UL>
<LI><P>When first opened, no configurations will be selected</P>
<LI><P>When later opened, previously selected configurations will
be selected</P>
</UL>
<LI><P>User selects configurations to be built</P>
<LI><P>User selects &ldquo;OK&rdquo; button to launch batch build</P>
<LI><P>For each configuration selected:</P>
<UL>
<LI><P>Package will be built using configuration settings</P>
<LI><P>Output will be placed in &lt;project
root&gt;/build/&lt;configuration name&gt;</P>
</UL>
</UL>
<P><BR><BR>
</P>
</BODY>
</HTML>
--------------090804010704060503070107--
Previous Topic:we're interested (Apogee, Inc.)
Next Topic:we're interested (Apogee, Inc.)
Goto Forum:
  


Current Time: Sat Aug 30 16:41:14 EDT 2014

Powered by FUDForum. Page generated in 0.02789 seconds