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.
| Summary: | Upgrade a MIDlet to Visual MIDlet | ||
|---|---|---|---|
| Product: | javame | Reporter: | ieising <ieising> |
| Component: | Visual Designer | Assignee: | Karol Harezlak <kharezlak> |
| Status: | NEW --- | ||
| Severity: | blocker | ||
| Priority: | P3 | ||
| Version: | 4.x | ||
| Hardware: | All | ||
| OS: | All | ||
| Issue Type: | ENHANCEMENT | Exception Reporter: | |
|
Description
ieising
2005-08-10 06:44:24 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? 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. 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 moving to mobility component 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. |