Community
Participate
Working Groups
Currently the developer needs to manually configure his run/debug configuration everytime that he creates a new midlet inside a midlet suite. a way to improve this feature is to add an option in the "Create MIDlet" wizard to automatically create a run and/or debug configuration for that specific MIDlet. Probably a good to do it: - Create two checkboxes on the "Create MIDlet" wizard. similar to the "Add to Application descriptor checkbox" - The first one can be "Create Run Configuration" and the second "Create Debug Configuration" - The checkboxes can be marked by default (since usually the user will want to execute each MIDlet he creates) - The final name of the Run / debug configurations can be: <project name>.<MIDlet name>
Hi gep, When user right click a Midlet and select run/debug as...-> Emulated Java ME Midlet, it will automatically vreate a run/debug configuration. User need not create one manually.
hi feng, but in the end this is a two steps process that i think it is not necessary, since everytime that the user creates a midlet he will definitely wants to run it :) i was talking with diego about this and one suggestion that he has is that when the run is pressed we automatically launch a class that extends MIDlet. if there is more than one midlet we present a dilog with the list of midlets. do you think that make sense? according to diego we might need a perspective to do that (i already opened a bug to create a mtj prespective :)). :) gep
Hi gep, I am creating a patch that will allow user select a project/package -> click run/debug button -> select run as Midlet -> choose a Midlet among all Midlets in the project/package -> launching. This patch is much like Applet launcher in JDT. Do you think it will solve the issue? Thanks Feng (In reply to comment #2) > hi feng, > > but in the end this is a two steps process that i think it is not necessary, > since everytime that the user creates a midlet he will definitely wants to run > it :) > > i was talking with diego about this and one suggestion that he has is that when > the run is pressed we automatically launch a class that extends MIDlet. if > there is more than one midlet we present a dilog with the list of midlets. do > you think that make sense? according to diego we might need a perspective to do > that (i already opened a bug to create a mtj prespective :)). > > :) > gep >
One more comment: The patch I am creating is exactly like Diego's suggestion. And I find it don't need a special perspective to function. BTW, I think MTJ perspective is useful and have already append a patch about that. (In reply to comment #2) > hi feng, > > but in the end this is a two steps process that i think it is not necessary, > since everytime that the user creates a midlet he will definitely wants to run > it :) > > i was talking with diego about this and one suggestion that he has is that when > the run is pressed we automatically launch a class that extends MIDlet. if > there is more than one midlet we present a dilog with the list of midlets. do > you think that make sense? according to diego we might need a perspective to do > that (i already opened a bug to create a mtj prespective :)). > > :) > gep >
hi feng, sorry for the late response... i think if we have some like what you suggest it would definitely solve the issue. besides that it is more the eclipse-way of launching and improve the developer workflow with mtj :) gep (In reply to comment #3) > Hi gep, > > I am creating a patch that will allow user select a project/package -> click > run/debug button -> select run as Midlet -> choose a Midlet among all Midlets > in the project/package -> launching. > > This patch is much like Applet launcher in JDT. > > Do you think it will solve the issue? > > Thanks > Feng > > (In reply to comment #2) > > hi feng, > > > > but in the end this is a two steps process that i think it is not necessary, > > since everytime that the user creates a midlet he will definitely wants to run > > it :) > > > > i was talking with diego about this and one suggestion that he has is that when > > the run is pressed we automatically launch a class that extends MIDlet. if > > there is more than one midlet we present a dilog with the list of midlets. do > > you think that make sense? according to diego we might need a perspective to do > > that (i already opened a bug to create a mtj prespective :)). > > > > :) > > gep > > >
Created attachment 110058 [details] patch for this enhance Midlet launching feature. Make it more like what Applet launching did.
Created attachment 110059 [details] Correct two typos in Java doc I misspell 'future' to 'feature' in Java doc. Correct it now:)
The MIDlet launching enhancement was integrated.
all bugs we integrated and release on MTj 0.9
