RES: [ercp-dev] which parts of eRCP are compliant with CLDC / MIDP

["Paula Gustavo-WGP010" <wgp010@xxxxxxxxxxxx>]

Hi gorken,

Thanks for your response.

Let me clarify a little how the library support is implemented on MTJ. Currently we can distribute a plugin with binary, source (optional), javadocs(optional). Base on that, the developer is able to add a library to his project and after that MTJ automatically add code assist support and javadoc/source access on the editor. By default the binary is packed with the MIDlet suite JAR. The user is able to disable this library deployment option.

It seems to me based on your answer that you are assuming that the MIDP device will already have eSWT support on it, isn't it? in that scenario, I agree that it doesn't make sense to pack eSWT with the MIDlet. but probably it is still interesting to the user to have the code assist and javadoc access. 

But there is also the case of devices that don't have eSWT on its api list. if eSWP only depends on standard MIDP/CLDC APIs, it is feasible to think that the developer could use it and pack with the MIDlet suite the classes that he is using isn't it? 
it seems to me that this might be valuable to the MIDP developers since he will have a more power full UI toolkit than the usual LCDUI. This approach is similar to what netbeans does with its sun LWUIT. 

Does it make sense to you?

If you think it make sense and that it add value to eRCP/MIDP communities, we are interested to help on providing the binaries of both eSWT and also the XML parser. We could do it manually first based on last eRCP code release. After, we can think about how to automate that.

:)
Gep

PS.: can you send me the eRCP cvs configuration?

-----Mensagem original-----
De: ercp-dev-bounces@xxxxxxxxxxx [mailto:ercp-dev-bounces@xxxxxxxxxxx] Em nome de Gorkem Ercan
Enviada em: quarta-feira, 7 de janeiro de 2009 05:47
Para: ERCP developers list
Assunto: Re: [ercp-dev] which parts of eRCP are compliant with CLDC / MIDP

Gustavo,
eSWT is the only part that we are actively supporting compatible with
MIDP CLDC. As Ove mentioned the support on tooling is coming through
the UEI on SDKs (Nokia S60 SDK).
It might be possible to provide a package that provides eSWT
compilation support (for Mac) but eSWT classes should not be packed
with the midlet as the current MTJ library support does. I am not sure
about the value of such a support for eSWT without the emulator
support. So microemulator support is needed.  It would be great if we
could find a better way to attach the sources for eSWT, in order to
have better code assist.

As you have mentioned there is also a CLDC version of the eRCP's XML
parser in our repository, however we are not providing binaries at the
moment.

--
Gorkem


On Tue, Jan 6, 2009 at 1:16 AM, Ove Nordström <ove.nordstrom@xxxxxxxxx> wrote:
> Hi Gustavo,
> Great, this could perhaps help JavaME developers on Mac OS X.
> I would be very happy if I could compile a eSWT Midlet on my Mac and using
> Eclipse MTJ!!!
> This not possible today, because neither Netbeans 6.5 or Eclipse MTJ 0,9
> support eSWT on Mac OS X
>
> Currently, Nokia are supporting eSWT midlet development through the Nokia
> SDKs.
> This works ok if you are using MS Windows XP, but for Mac OS X there is no
> support for the Nokia SDK.
>
> Today when I develop JavaME applications on my Mac I am using Netbeans 6.5
> and instead of Nokia SDK I am forced to use Netbeans Mobility Microemulator
> Plugin.
> ( http://blogs.sun.com/kharezlak/entry/solaris_mac_os_linux_microemulator )
>
> I think it also would be great if the MTJ-project could look at the
> microemulator and try to get eSWT
> support through it.
>
> Regards,
> Ove
>
> 2009/1/5 Paula Gustavo-WGP010 <wgp010@xxxxxxxxxxxx>
>>
>> Hi,
>>
>> My name is gustavo and i'm one of MTJ committers. One of the features that
>> we just added to MTJ is the library support. With it, it is possible to
>> distribute libraries with MTJ that can easily added to a MIDP project. The
>> library is distributed as a JAR file (inside a library plugin) with some
>> additional metadata and when the project is build it is packed with the
>> final MIDlet suite JAR. This feature simplifies the life of the developer to
>> use external JARs on the MIDlet project.
>>
>>
>>
>> Currently we are not distributing any library with MTJ and we are now
>> evaluating some options to be included on our next release.
>>
>> I note based on eRCP wiki that it is already possible to use eSWT with
>> MIDlets (http://wiki.eclipse.org/How_to_use_eSWT_with_Midlets). I was
>> wondering if there are other parts of the code that depends only on CLDC and
>> could be packed as a library on MTJ. i also saw a xml parser, but I'm not
>> sure if it builds against CLDC.
>>
>> If we are able to distribute some libraries with MTJ that comes from eRCP,
>> that will make it easy to MIDP developer to use them and also distribute
>> them with their MIDlets.
>>
>> Do you guys think that this make sense?
>>
>> Regards,
>>
>> Gustavo
>>
>> PS.: can someone also forward to me the eRCP project cvs configuration? I
>> couldn't find on the project website
>>
>> _______________________________________________
>> ercp-dev mailing list
>> ercp-dev@xxxxxxxxxxx
>> https://dev.eclipse.org/mailman/listinfo/ercp-dev
>>
>
>
>
>
>
>
> _______________________________________________
> ercp-dev mailing list
> ercp-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/ercp-dev
>
>
_______________________________________________
ercp-dev mailing list
ercp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ercp-dev