Home » Archived » DSDP - Mobile Tools for Java (MTJ) » we're interested (Apogee, Inc.)
| we're interested (Apogee, Inc.) [message #1383] |
Fri, 28 October 2005 22:38  |
Eclipse User |
|
|
|
Originally posted by: stanley.apogee.com
I'll be the primary contact for Apogee, Inc.
Background: we are currently providing ports
of IBM's JVM for various embedded platforms.
I've implemented a plugin (for WSDD) that allows
for (more or less) easy configuration of target
device and corresponding run/debug target.
I would like to move above functionality to current
Eclipse codebase. Please note that I am more
concerned with the actual 'remote device management'
and not 'emulator management'.
I've placed a couple of screenshots of current
configuration on http://apogee.com/stanley/.
thanks,
-- stanley
|
|
|
| Re: we're interested (Apogee, Inc.) [message #1398 is a reply to message #1383] |
Mon, 31 October 2005 08:29  |
| Eclipse User |
|
|
|
Originally posted by: arto.laurila.nomail.nokia.com
Hi Stanley!
Looks great, could you provide some more information about the
plugins and do you have any architecture docs about the "remote
device management".
I have collected some info in our side in the same area and it would
be nice to discuss further.
Br. Arto
------------------
Arto Laurila
Chief Architect
Java and Content Tools, TP Series 60 Platform
NOKIA
------------------------------
"Stanley Gambarin" <stanley@apogee.com> wrote in message
news:dju99h$f7t$1@news.eclipse.org...
> I'll be the primary contact for Apogee, Inc.
>
> Background: we are currently providing ports
> of IBM's JVM for various embedded platforms.
> I've implemented a plugin (for WSDD) that allows
> for (more or less) easy configuration of target
> device and corresponding run/debug target.
>
> I would like to move above functionality to current
> Eclipse codebase. Please note that I am more
> concerned with the actual 'remote device management'
> and not 'emulator management'.
>
> I've placed a couple of screenshots of current
> configuration on http://apogee.com/stanley/.
>
> thanks,
> -- stanley
|
|
| |
| Re: we're interested (Apogee, Inc.) [message #1417 is a reply to message #1403] |
Tue, 01 November 2005 01:53 |
| Eclipse User |
|
|
|
Originally posted by: stanley.apogee.com
Mika,
thanks for the welcome note. To answer your question,
yes, I need to implement similar functionality (already
present in WSDD) in Eclipse. Hence, i'll be participating
in 'mtj' and 'tm' discussions (to the best of my abilities)
and providing code.
-- stanley
Mika Hoikkala wrote:
> Nice to hear about you Stanley,
>
> You are welcome to join MTJ if you see it feasible.
>
> By "moving above functionality to Eclipse" do you mean that you could
> contribute code + resource to make it happen in practise?
>
> mho (=Mika Hoikkala, project lead for MTJ)
>
>
>
> Stanley Gambarin wrote:
>
>> I'll be the primary contact for Apogee, Inc.
>>
>> Background: we are currently providing ports
>> of IBM's JVM for various embedded platforms.
>> I've implemented a plugin (for WSDD) that allows
>> for (more or less) easy configuration of target
>> device and corresponding run/debug target.
>>
>> I would like to move above functionality to current
>> Eclipse codebase. Please note that I am more
>> concerned with the actual 'remote device management'
>> and not 'emulator management'.
>>
>> I've placed a couple of screenshots of current
>> configuration on http://apogee.com/stanley/.
>>
>> thanks,
>> -- stanley
|
|
|
| Re: we're interested (Apogee, Inc.) [message #1421 is a reply to message #1398] |
Tue, 01 November 2005 02:23 |
| Eclipse User |
|
|
|
Originally posted by: stanley.apogee.com
Arto,
i can try to provide as much info as possible. I would
recommend people looking into 'tm' and 'mtj' to check out
the WSDD 5.7.1 (free trial download off ibm.com somewhere).
Essentially, this is how it breaks down (please note that
some information may not be complete/true :)):
- WSDD has a concept of 'Device'. Each device is registered
as a plugin and implements a certain interface. The interface
allows for WSDD to query device properties, e.g. whether it
can run .jar files or only .class files, create a GUI (for
configuration), etc. Each 'Device' also exposes a 'ILaunchable'
class that is used to launch an application on the device.
- Whenever you configure your application's 'Run...' dialog,
you get an option of running your application using one of
'JRE's or a 'Device'. If you select the 'Device' to run your
application, then WSDD will invoke 'ILaunchable' configured from
the device's properties (and that's pretty much it).
Now, what we provide is built on top of the WSDD's infrastructure
and it consists of:
a) a GUI allowing for creation of various devices (the screenshots
that i've sent before). Basically (for us), each device must have
a working TCP/IP stack (needed for JDWP/JVMDI debug, also can be
used to start the VM) and optionally Serial connection
(used to start the VM if we can't do it over TCP/IP for some reason).
The project's files are located on the host system and are
exposed to target's via NFS/Samba. We do not support uploading
files to the target to run them (we found this to be a non-issue in
the development environment). The VM binaries can be placed either
on the host or target file system.
b) 'ILaunchable' interface which is used to launch the VM on the
target 'Device'. After the 'Device' has been configured via above
GUI, it's pretty easy to launch it on the target:
- collect command line that would have been used to execute
the java program on the local machine.
- perform string substitution to change 'local' prefix into 'remote'
prefix (the whole 'NFS mapping' box in the GUI).
- prepend the full location of the VM on the target (specified in GUI)
- prepend the 'external run command' (e.g. ssh, rsh, etc).
Now, the interface is not the most beautiful, but it works quite well
for our purposes (we have close to 20 different platforms that we
support with the above). All 'default' configuration for each device variety
is done via XML, so I only need to distribute single plugin to support above.
Also note that 'Device' interface of WSDD is very generic and provides
support for emulators/simulators (Palm is included), etc. I would like to
have similar functionality in Eclipse so we can provide customers with the
latest and greatest (WSDD is built upon old version of Eclipse, so it has
it's quirks).
-- stanley
Arto Laurila wrote:
> Hi Stanley!
>
> Looks great, could you provide some more information about the
> plugins and do you have any architecture docs about the "remote
> device management".
> I have collected some info in our side in the same area and it would
> be nice to discuss further.
>
> Br. Arto
>
> ------------------
> Arto Laurila
> Chief Architect
> Java and Content Tools, TP Series 60 Platform
> NOKIA
> ------------------------------
>
>
>
>
> "Stanley Gambarin" <stanley@apogee.com> wrote in message
> news:dju99h$f7t$1@news.eclipse.org...
>
>>I'll be the primary contact for Apogee, Inc.
>>
>>Background: we are currently providing ports
>>of IBM's JVM for various embedded platforms.
>>I've implemented a plugin (for WSDD) that allows
>>for (more or less) easy configuration of target
>>device and corresponding run/debug target.
>>
>>I would like to move above functionality to current
>>Eclipse codebase. Please note that I am more
>>concerned with the actual 'remote device management'
>>and not 'emulator management'.
>>
>>I've placed a couple of screenshots of current
>>configuration on http://apogee.com/stanley/.
>>
>>thanks,
>>-- stanley
>
>
>
|
|
| | |
| Re: we're interested (Apogee, Inc.) [message #561134 is a reply to message #1403] |
Tue, 01 November 2005 01:53 |
| Eclipse User |
|
|
|
Originally posted by: stanley.apogee.com
Mika,
thanks for the welcome note. To answer your question,
yes, I need to implement similar functionality (already
present in WSDD) in Eclipse. Hence, i'll be participating
in 'mtj' and 'tm' discussions (to the best of my abilities)
and providing code.
-- stanley
Mika Hoikkala wrote:
> Nice to hear about you Stanley,
>
> You are welcome to join MTJ if you see it feasible.
>
> By "moving above functionality to Eclipse" do you mean that you could
> contribute code + resource to make it happen in practise?
>
> mho (=Mika Hoikkala, project lead for MTJ)
>
>
>
> Stanley Gambarin wrote:
>
>> I'll be the primary contact for Apogee, Inc.
>>
>> Background: we are currently providing ports
>> of IBM's JVM for various embedded platforms.
>> I've implemented a plugin (for WSDD) that allows
>> for (more or less) easy configuration of target
>> device and corresponding run/debug target.
>>
>> I would like to move above functionality to current
>> Eclipse codebase. Please note that I am more
>> concerned with the actual 'remote device management'
>> and not 'emulator management'.
>>
>> I've placed a couple of screenshots of current
>> configuration on http://apogee.com/stanley/
>>
>> thanks,
>> -- stanley
|
|
|
| Re: we're interested (Apogee, Inc.) [message #561156 is a reply to message #1398] |
Tue, 01 November 2005 02:23 |
| Eclipse User |
|
|
|
Originally posted by: stanley.apogee.com
Arto,
i can try to provide as much info as possible. I would
recommend people looking into 'tm' and 'mtj' to check out
the WSDD 5.7.1 (free trial download off ibm.com somewhere).
Essentially, this is how it breaks down (please note that
some information may not be complete/true :)):
- WSDD has a concept of 'Device'. Each device is registered
as a plugin and implements a certain interface. The interface
allows for WSDD to query device properties, e.g. whether it
can run .jar files or only .class files, create a GUI (for
configuration), etc. Each 'Device' also exposes a 'ILaunchable'
class that is used to launch an application on the device.
- Whenever you configure your application's 'Run...' dialog,
you get an option of running your application using one of
'JRE's or a 'Device'. If you select the 'Device' to run your
application, then WSDD will invoke 'ILaunchable' configured from
the device's properties (and that's pretty much it).
Now, what we provide is built on top of the WSDD's infrastructure
and it consists of:
a) a GUI allowing for creation of various devices (the screenshots
that i've sent before). Basically (for us), each device must have
a working TCP/IP stack (needed for JDWP/JVMDI debug, also can be
used to start the VM) and optionally Serial connection
(used to start the VM if we can't do it over TCP/IP for some reason).
The project's files are located on the host system and are
exposed to target's via NFS/Samba. We do not support uploading
files to the target to run them (we found this to be a non-issue in
the development environment). The VM binaries can be placed either
on the host or target file system.
b) 'ILaunchable' interface which is used to launch the VM on the
target 'Device'. After the 'Device' has been configured via above
GUI, it's pretty easy to launch it on the target:
- collect command line that would have been used to execute
the java program on the local machine.
- perform string substitution to change 'local' prefix into 'remote'
prefix (the whole 'NFS mapping' box in the GUI).
- prepend the full location of the VM on the target (specified in GUI)
- prepend the 'external run command' (e.g. ssh, rsh, etc).
Now, the interface is not the most beautiful, but it works quite well
for our purposes (we have close to 20 different platforms that we
support with the above). All 'default' configuration for each device variety
is done via XML, so I only need to distribute single plugin to support above.
Also note that 'Device' interface of WSDD is very generic and provides
support for emulators/simulators (Palm is included), etc. I would like to
have similar functionality in Eclipse so we can provide customers with the
latest and greatest (WSDD is built upon old version of Eclipse, so it has
it's quirks).
-- stanley
Arto Laurila wrote:
> Hi Stanley!
>
> Looks great, could you provide some more information about the
> plugins and do you have any architecture docs about the "remote
> device management".
> I have collected some info in our side in the same area and it would
> be nice to discuss further.
>
> Br. Arto
>
> ------------------
> Arto Laurila
> Chief Architect
> Java and Content Tools, TP Series 60 Platform
> NOKIA
> ------------------------------
>
>
>
>
> "Stanley Gambarin" <stanley@apogee.com> wrote in message
> news:dju99h$f7t$1@news.eclipse.org...
>
>>I'll be the primary contact for Apogee, Inc.
>>
>>Background: we are currently providing ports
>>of IBM's JVM for various embedded platforms.
>>I've implemented a plugin (for WSDD) that allows
>>for (more or less) easy configuration of target
>>device and corresponding run/debug target.
>>
>>I would like to move above functionality to current
>>Eclipse codebase. Please note that I am more
>>concerned with the actual 'remote device management'
>>and not 'emulator management'.
>>
>>I've placed a couple of screenshots of current
>>configuration on http://apogee.com/stanley/
>>
>>thanks,
>>-- stanley
>
>
>
|
|
|
Goto Forum:
Current Time: Fri Apr 19 11:54:26 GMT 2024
Powered by FUDForum. Page generated in 0.04218 seconds |
] 
Search
Help
Register
Login
Home
