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 88033 - Capability to use something other than JFrame as the wizard container
Summary: Capability to use something other than JFrame as the wizard container
Status: VERIFIED FIXED
Alias: None
Product: installer
Classification: Unclassified
Component: NBI (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: Kirill Sorokin
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-10-26 07:37 UTC by Kirill Sorokin
Modified: 2008-03-11 12:28 UTC (History)
0 users

See Also:
Issue Type: TASK
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 Kirill Sorokin 2006-10-26 07:37:54 UTC 
Currently the only way to start the engine is via JNLP or running the jar
directly. Running as an applet would a nice value-add. It's a low-priority task
however.
Comment 1 Kirill Sorokin 2006-11-11 23:33:09 UTC 
The task seems to be slightly broader than it was initially perceived. The
wizard should be able to use different containers:
- JFrame (as it is now)
- JApplet (as we would possibly like to introduce this behavior)
- JPanel (if we would like to run the wizard directly in NB IDE)
- JDialog (???)
- ??? (if we feel the need for it)
Comment 2 Kirill Sorokin 2006-11-27 15:48:40 UTC 
Posponing to M07, since we failed miserably to achieve this task for M06.
Comment 3 Kirill Sorokin 2006-12-20 07:36:13 UTC 
-> M08
Comment 4 Kirill Sorokin 2007-01-15 17:55:33 UTC 
Fixed with the refactoring of the wizard framework.
Comment 5 Kirill Sorokin 2008-03-11 12:28:41 UTC 
Verifying installer issues.