| RES: [dsdp-mtj-dev] RE: MIDlet template suggestion |
this is somehow related to the bug that i opened about how to filter the templates. we could do the filter based on some classpath definition of the project and/or based on the exernal library that is associated to the project. so each template on the extension point could defines its requirements to be added to a mtj project. for instance, a unit test template could only be available to a project that has the unit test library associated to it we still don't have a solution and a clear requirements for that. it is also not clear if if make sense to do this now. those are all new apis and we deon't yet how it is going to be used :) gep ________________________________ De: dsdp-mtj-dev-bounces@xxxxxxxxxxx em nome de Sandin Diego-WDS057 Enviada: seg 16/2/2009 14:00 Para: Mobile Tools for The Java Platform mailing list Assunto: RE: [dsdp-mtj-dev] RE: MIDlet template suggestion We could integrate the MIDlets templates functionality with the external library one. Each External library has an ID, which could be specified in the implementation of a MIDlet template E.P. It would be very useful and I don't believe it would require a lot of effort to be implemented. ________________________________ From: dsdp-mtj-dev-bounces@xxxxxxxxxxx [mailto:dsdp-mtj-dev-bounces@xxxxxxxxxxx] On Behalf Of Craig Setera Sent: Monday, February 16, 2009 1:44 PM To: Mobile Tools for The Java Platform mailing list Subject: Re: [dsdp-mtj-dev] RE: MIDlet template suggestion It sounds like there is some general confusion about the templates function... As described by David and Gustavo, this is not a "project" template, but a "midlet" (ie. class) template. On the other hand, if a user wanted to create a "test midlet", the ability to add libraries to the classpath as part of the template does sound appealing. On Feb 16, 2009, at 10:41 AM, Paula Gustavo-WGP010 wrote: hi tomas, on mtj, there is feature called "externallibraries". this feature provide an extension point that can be used to provide libraries, such as mobileunit, to the project. those libraries are shown during the project creation wizard and the user can add it to the project and are automatically exterd and included on the final midlet suite jar. maybe the way to implement the use case you suggested is: 1- create an extenallibrary plugin that will encapsulate the mobileunit library. we already do something like that with the jmunit library that is distributed with mtj. 2- create a template plugin with all java files / resource that you want to have on your project 3- create a mtj project preconfigured with mobileunit library (from step 1) 4- the user will them create a midlet from the template (that you provide on step 2) so you can provide your developers: 2 plugins that he will add to the dropins folder and an example project tht he will import to his workspace. does that make sense to you? there are examples of how to implement both the library and the templates on mtj sdk and also some documentation of how to do it. do you think that this cover your use case? i can send you some more examples if it is not clear how to use the externallibraries and templates. those are all new apis so it is not complety clear yet to everyone how to use them. :) gep _______________________________________________ dsdp-mtj-dev mailing list dsdp-mtj-dev@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/dsdp-mtj-dev
<<winmail.dat>>