Re: [ercp-dev] Enhancing the eSWT experience for MIDlet developers

[Mark Rogalski <rogalski@xxxxxxxxxx>]

All good ideas.   I know from past
experience at looking at whether JFace would run on CLDC that there are
several areas dependent on CDC API.  It would probably not be a huge
effort to modify these parts to remove the dependency. However, if some
of this code is difficult to replace, would we consider creating a smaller
set of eJFace for MIDP?

It seems to me that single sourcing
may not be too difficult. The eSWT demo already can run in 3 different
modes using the same source (stand-alone java/eSWT app, RCP app, eRCP app).
The most important consideration would be to restrict yourself to using
CLDC API.

         
      Mark

Gorkem Ercan <gercan@xxxxxxx>
Sent by: ercp-dev-bounces@xxxxxxxxxxx

01/26/2009 06:15 AM

Please respond to
ERCP developers list <ercp-dev@xxxxxxxxxxx>

To	ERCP developers list <ercp-dev@xxxxxxxxxxx>
cc	David.Prather@xxxxxxxxxxxxxxxx
Subject	[ercp-dev] Enhancing the eSWT experience for MIDlet developers

Hi,
As you may know, since some of the adopters of eRCP project (such as
Nokia S60) started shipping eSWT with their platforms. eRCP has gained
a MIDP community. However I feel that so far we have not worked on
providing better experience to MIDP developers when they are using
eSWT (or any other eRCP technology). I would like to start a
concentrated effort on providing better utility APIs for MIDP
developers. Some areas that comes to my mind are

1. Providing MIDlet helpers so that the plumbing code for using eSWT is
hidden
2. Create a port of eJFace for MIDlet use.
3. Make it easier to port applications between MIDlets and eRCP
applications (single sourcing)

As always this is a community effort and the whole eRCP community is
invited to help, test and provide ideas.

--
Gorkem
_______________________________________________
ercp-dev mailing list
ercp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ercp-dev