|RE: [dsdp-mtj-dev] The new JAD editor extension point|
This thread has really got me thinking about my on assumptions what problem MTJ is trying to solve. I had assumed that MTJ would be a platform which ME developers could use to create applications, and which could be extended by manufacturers for manufacturer specific concepts/SDK’s etc. So far so good. But I had also assumed that manufacturer-specific extensions could co-exist on top of the same MTJ instance. ME developers could then have only one “IDE” and be able to target specific manufacturers from within that single IDE.
Now, based on this discussion, it sounds like this is not the major concept of MTJ as I understood it. Is it intended that MTJ is more of a runtime that is not intended to stand on its own, and it is expected to only be bundled into a “proprietary” IDE targeting a specific manufacturer? ME developers would then still have to manage multiple IDE’s for every manufacturer they want to support?
Please let me know if I understand correctly. It certainly seems like this needs to be clarified for the purposes of this specific discussion as well, as it would certainly lead us in different directions for how to support custom JAD editor extensions.
Team Lead - Java Development Platform Tools
Research In Motion
dsdp-mtj-dev-bounces@xxxxxxxxxxx [mailto:dsdp-mtj-dev-bounces@xxxxxxxxxxx] On Behalf Of Paula Gustavo-WGP010
ok... let me return to my original comment :)
by default mtj runtime will never have any vendor specific page on the jad editor (at least this is the current design). the only place that it will appear would be in a nokia IDE that distribute mtj and only if nokia decide to implement the jad editor extension point and add their own page. in this scenario, maybe it is not bad that the nokia page is shown with a nokia sdk and, if the user decide to use the same nokia IDE to develop to motorola, the page will not be shown (actually the page is not even in that distribution :)).
so i think that probably those changes that we are discussing make more sense only if we decide to move the vendor specific pages to MTJ runtime and maintain that code inside MTJ. does that make sense to everyone?
dsdp-mtj-dev-bounces@xxxxxxxxxxx [mailto:dsdp-mtj-dev-bounces@xxxxxxxxxxx] On Behalf Of Craig Setera
Perhaps it is time to add some new UI to control the JAD editor? A preference page that lists the available pages and allows them to be turned on and off? For instance, if I never want to make vendor-specific changes, I could go into the preferences and deselect those pages? Even better would be if the pages could be closed from the editor and then reenabled from the preferences. That would solve these issues because it would be an explicit action on the part of the user.
On Aug 5, 2008, at 6:36 AM, Paula Gustavo-WGP010 wrote:
the problem is that the vendor that diego mentioned is not the device manufacturer. this field on the jad is the midlet suite developer (like gameloft, EA games, etc.). since that, i don't think that we make the nokia, mot, etc pages context sensitive based on this information.
On Behalf Of Gang.Ma@xxxxxxxxxx
This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful.