This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 62019 - Upgrade a MIDlet to Visual MIDlet
Summary: Upgrade a MIDlet to Visual MIDlet
Status: NEW
Alias: None
Product: javame
Classification: Unclassified
Component: Visual Designer (show other bugs)
Version: 4.x
Hardware: All All
: P3 blocker (vote)
Assignee: Karol Harezlak
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-08-10 06:44 UTC by ieising
Modified: 2008-05-05 11:35 UTC (History)
0 users

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description ieising 2005-08-10 06:44:24 UTC 
Hi,

I'm finding the J2ME plugin of Netbeans superior to all other J2ME development
environments and with the new Visual MIDlet support, NB is even extending the
gap. But I would like to see the functionality to 'upgrade' a MIDlet to a visual
MIDlet.

Iwan
Comment 1 Lukas Hasik 2005-08-10 07:30:59 UTC 
Iwan, do you mean that you write a midlet by hand and then upgrade to visual
midlet=the midlet will be parsed and all components etc. will appear in visual
designer?
Comment 2 Martin Ryzl 2005-08-10 09:15:34 UTC 
I assume either a possibility to import an existing MIDlet into mvd or full
two-way editing (i.e. without guarded blocks). All possibilities are being
evaluated.
Comment 3 ieising 2005-08-10 09:48:50 UTC 
Ideally I would like the 'upgrade' see all my components and create the
corresponding components so I can edit it visually from then on. Two-way-editing
if you will.

But for starters I wouldn't mind if only an empty .MVD file would be created.
Now I need to create a new visual MIDlet, copy-past all code from the old on to
the visual MIDlet, rename etc etc. Cumbersome in one word.

But if you can get the two-way-editing working. That would be excellent.

Iwan
Comment 4 Lukas Hasik 2006-06-23 14:54:09 UTC 
moving to mobility component
Comment 5 David Kaspar 2007-07-10 16:45:33 UTC 
Designer 1 has been removed. Therefore reassigning to Designer 2 module.
Anyway it is hard to implement such conversion since the Designer would have to inspect the source code. This is similar
to 2-way editing has been postponed to the future.