Bug 60623 - Replacement SetupWizard with Module Catalog
Replacement SetupWizard with Module Catalog
Status: RESOLVED FIXED
Product: platform
Classification: Unclassified
Component: -- Other --
5.x
PC All
: P1 (vote)
: 5.x
Assigned To: Jiri Rechtacek
issues@platform
NbFeature1153, NbFeature1102
: API_REVIEW_FAST
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2005-06-29 15:18 UTC by Jiri Rechtacek
Modified: 2008-12-22 21:28 UTC (History)
1 user (show)

See Also:
Issue Type: ENHANCEMENT
:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jiri Rechtacek 2005-06-29 15:18:21 UTC
Provide only one simple Module Catalog which is accessible from Tools menu as
replacement of Setup Wizard.
Rid of Setup Wizard and its panels registered in layer. Only two modules: core
and autoupdate are using registration of own panels in SetupWizard, all panels
has some replacement either in new Options panels or in ModuleCatalog.
This feature is developed on branch uninstall_module_20323 together with
Uninstall Module feature. Only modules core, core-ui are autoupdate are subject
of this change.
Needs to change the platform and IDE documentation and note in a upgrade-guide.
Comment 1 Jiri Rechtacek 2005-07-19 14:50:30 UTC
Possibility to declare own panel to Setup Wizard is undocumented 'api', don't
afraid to broke this 'api'. IMHO it can be tracked as API_REVIEW_FAST instead of
API_REVIEW.
Subject of this api change is:
- rid of Setup Wizard: all panels (formerly a part of Setup Wizard) will own
replacement in new Preferences Dialog (issue 58412) and new Module Catalog Dialog
- new Module Catalog Dialog designed in UI spec.
http://ui.netbeans.org/docs/ui/update/manager.htm

Module Catalog Dialog is based on core/src/ModuleNode, core/src/ModuleBean and
core/startup/ModuleList w/o any API change.

Not a subject of this review is placement of Module Catalog Panel. The panel is
placed originally in Core module - probably not ideal. I'll file a another issue
where to place these classes in a another module inserted of Core module I'll
prefer the Autoupdate module as general handler of module customizations.

Any objections, comments? Thanks for review.
Comment 2 Jiri Rechtacek 2005-07-29 09:15:27 UTC
Thanks for review. I'm going to integrate early next week.
Comment 3 Jiri Rechtacek 2005-08-03 15:12:17 UTC
Impl has been integrated in main trunk 05/08/03.


By use of this website, you agree to the NetBeans Policies and Terms of Use. © 2012, Oracle Corporation and/or its affiliates. Sponsored by Oracle logo