Yes, you can probably run eSWT and eJFace
in CLDC/MIDP. I'm not sure if the eSWT provided with the eRCP runtime
will work as-is or if it might need to be tweaked. eJFace does have a few
CDC/Foundation dependencies. I don't think any of these should be a big
problem. You can either code around them or remove the offending classes.
J9 is usually pretty stable. More likely
is that eSWT is getting an exception. If you can pin point the problem
to a certain eSWT operation, you may be able to work around it.
<edgar@xxxxxxxxxxxxxxxxxxxxxx> Sent by: dsdp-ercp-dev-bounces@xxxxxxxxxxx
09/10/2008 11:00 AM
Please respond to
DSDP ercp list <dsdp-ercp-dev@xxxxxxxxxxx>
It is possible to run eSWT + eJFace as a standalone (midlet) program?
This is relevant becouse In this way, there are more choises to workaround
any eRCP full stack problem,
and at the same time, keep going with the "eclipse way and API"
For example: currently I'm developing for S80 platform, yes, yes "too
old" and I get a breakdown of the entire eWorkbench frequently.
and it is becouse probably due to J9...
whatever ! I do not have money to buy a new communicator E90, so
I want to solve the problems that I have, doing any steps backward as necessary,
but keeping the "eclipse way" that includes APIs like eSWT, eJFace,
and releated technologies and I'm confident it will be in any way
a good investment becouse, I also develop in the full eclipse platform
This is my case, but actually, it may be the case of many people (that
probably prefer abandon the way eventually, waiting for more mature times
-what not is good to foster a small community-) So it requires have
a clear path to make workarounds, and at least, to keep
going with the API and doing that, still being doing a good investiment
of time, learnning and developing skills releated to eclipse API.