Hi,
I spent some time on understanding the installable_sdk branch. Here it what I suggest as a plan further.
- At this moment, if you see, Oracle and Nokia seems to be the only active customers of MTJ. I would suggest MTJ should use complete feature of Device SDK Manager (DSM) from Nokia which provides device details, screen size, etc. By doing this, MTJ will have
default support of Nokia and Oracle SDKs through DSM. Of course other SDKs can be added as there would be extension point provided to add SDKs to DSM. Also, as and when there is new J2ME SDK, either MTJ or the SDK owner can use the extension point to add their
SDK to device SDK manager. For example: Tomorrow, ABC company wants to add the SDK to the DSM, they just need to use the extension point we provide and create the plugin. MTJ would fetch the information using p2 and display those SDKs along with other SDKs
in DSM.
Note: default support if manual SDK integration would still be available, in case anybody wants to integrate the SDK manually.
I have started looking at this.
- Oracle can continue their changes on installable_sdk branch. As and when they are ready, we help to merge their code.
- Lots of new changes will be available in installable_sdk. Finally, installable_sdk branch to be merged with master.
- Code drag and drop feature: It would help developer to drag and drop the code snippet directly to the selected location.
For example: user is writing the SMS application. He can drag “SMS Send” option from the Code Snippet list and drop it to the selected location in the code. It would add the code of sending the SMS to the application.
I would appreciate your views.
Thanks,
Pranav
