| Feedback on MTJ proposal [message #173] |
Mon, 17 October 2005 06:15  |
Eclipse User |
|
|
|
Originally posted by: arto.laurila.nomail.nokia.com
Device & Emulator Framework
Debugging
Deployment Framework
|
|
|
| Re: Feedback on MTJ proposal [message #185 is a reply to message #173] |
Mon, 17 October 2005 07:05  |
| Eclipse User |
|
|
|
Originally posted by: arto.laurila.nomail.nokia.com
Sorry about the partial mail, here is the whole message.
I'll list some MTJ projects basic level of goals here.
.."Device & Emulator Framework"
As traditional runtimes are managed in Eclipse as a JRE, in the mobile
segment the runtime environments are device emulators or real devices. MTJ
looks to provide features to manage mobile runtimes and provide frameworks
for device vendors to add those runtimes to the development environment.
.."Debugging"
The goal of this item is to enhance the current JDT Debugging environment
so that it is possible to use mobile runtimes, either emulator or a real
device. This task extends to launching the JVM and applications on the local
emulator or on the device itself, and allowing the developer to attach to
that application under test. In the mobile space, this is tightly integrated
with the Device and Emulator framework, and will need to provide a robust
framework for device and platform makers to extend to their devices'
specific connectivity. MTJ also intends for mobile debugging to extend the
debug frameworks of Eclipse.
This is related to Device & Emulator Framework .
.."Deployment Framework"
This makes it as easy as possible for developers to be able to test their
mobile deployments on real devices, developers must have methods to transfer
mobile applications to handheld devices using local methods (e.g. Bluetooth,
USB, IrDA). MTJ intends to develop a framework that provides an API for
vendor specific plug-ins, which then do the actual deployment. The
Deployment frw have to support that some existing deployments may be done
with native components, and possible new java based approaches.
.."Generic and Customizable "Build" Process for Mobile Application
development"
MTJ intends to enhance normal build process with mobile extensions like JAR
and JAD file generation. With the varying configurations and profiles of
mobile Java, this is critical to enabling developers to manage code
production. Another requirement is to provide ways to add additional tasks
to the build process e.g. signing. This work should extend the builder
frameworks of Eclipse.
.."Wizards for Mobile Apps Creation"
MTJ intends to enhance the existing wizards by providing Eclipse
mobile-specific wizards. As several kind of wizards are available for
general Eclipse development, they do not exist for mobile projects. These
mobile wizards will be tied to the differing configurations and profiles of
mobile Java, to relieve mobile developers of the need to worry about the
boilerplate code for each of the application configuration/profile types.
.."UI Design Tools"
The MTJ also wants to provide mobile developers with tools to improve
efficiency (easy drag and drop without coding) and also decrease the entry
barrier for newcomers.
As today, Eclipse's visual designers do not have specific mobile extensions
to enable e.g. different resolutions, screen sizes, different vendor
specific look and feel, etc.
The idea is to create a framework that enables development for different
kinds of mobile UI implementations by utilizing Eclipse Visual Editor
Project by extending it with device screen engines from different vendors.
.."Screen Flow Designer Tool"
MTJ wants to provide Eclipse developers with a better flow design tool,
which would provide ways to develop application logic easily. The tool would
provide easy drag and drop functionality to add different kind of screens
and transitions between them.
Br. Art
"Arto Laurila" <arto.laurila@nomail.nokia.com> wrote in message
news:divfic$cfk$1@news.eclipse.org...
>
> Device & Emulator Framework
>
> Debugging
>
> Deployment Framework
>
>
|
|
|
| Re: Feedback on MTJ proposal [message #560727 is a reply to message #173] |
Mon, 17 October 2005 07:05 |
 Arto Laurila
Messages: 32
Registered: July 2009 |
Member |
|
|
Sorry about the partial mail, here is the whole message.
I'll list some MTJ projects basic level of goals here.
.."Device & Emulator Framework"
As traditional runtimes are managed in Eclipse as a JRE, in the mobile
segment the runtime environments are device emulators or real devices. MTJ
looks to provide features to manage mobile runtimes and provide frameworks
for device vendors to add those runtimes to the development environment.
.."Debugging"
The goal of this item is to enhance the current JDT Debugging environment
so that it is possible to use mobile runtimes, either emulator or a real
device. This task extends to launching the JVM and applications on the local
emulator or on the device itself, and allowing the developer to attach to
that application under test. In the mobile space, this is tightly integrated
with the Device and Emulator framework, and will need to provide a robust
framework for device and platform makers to extend to their devices'
specific connectivity. MTJ also intends for mobile debugging to extend the
debug frameworks of Eclipse.
This is related to Device & Emulator Framework .
.."Deployment Framework"
This makes it as easy as possible for developers to be able to test their
mobile deployments on real devices, developers must have methods to transfer
mobile applications to handheld devices using local methods (e.g. Bluetooth,
USB, IrDA). MTJ intends to develop a framework that provides an API for
vendor specific plug-ins, which then do the actual deployment. The
Deployment frw have to support that some existing deployments may be done
with native components, and possible new java based approaches.
.."Generic and Customizable "Build" Process for Mobile Application
development"
MTJ intends to enhance normal build process with mobile extensions like JAR
and JAD file generation. With the varying configurations and profiles of
mobile Java, this is critical to enabling developers to manage code
production. Another requirement is to provide ways to add additional tasks
to the build process e.g. signing. This work should extend the builder
frameworks of Eclipse.
.."Wizards for Mobile Apps Creation"
MTJ intends to enhance the existing wizards by providing Eclipse
mobile-specific wizards. As several kind of wizards are available for
general Eclipse development, they do not exist for mobile projects. These
mobile wizards will be tied to the differing configurations and profiles of
mobile Java, to relieve mobile developers of the need to worry about the
boilerplate code for each of the application configuration/profile types.
.."UI Design Tools"
The MTJ also wants to provide mobile developers with tools to improve
efficiency (easy drag and drop without coding) and also decrease the entry
barrier for newcomers.
As today, Eclipse's visual designers do not have specific mobile extensions
to enable e.g. different resolutions, screen sizes, different vendor
specific look and feel, etc.
The idea is to create a framework that enables development for different
kinds of mobile UI implementations by utilizing Eclipse Visual Editor
Project by extending it with device screen engines from different vendors.
.."Screen Flow Designer Tool"
MTJ wants to provide Eclipse developers with a better flow design tool,
which would provide ways to develop application logic easily. The tool would
provide easy drag and drop functionality to add different kind of screens
and transitions between them.
Br. Art
"Arto Laurila" <arto.laurila@nomail.nokia.com> wrote in message
news:divfic$cfk$1@news.eclipse.org...
>
> Device & Emulator Framework
>
> Debugging
>
> Deployment Framework
>
>
|
|
|
|
Powered by
FUDForum. Page generated in 0.03613 seconds
] 
Search
Help
Register
Login
Home
