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 71056

Summary:	Make Lib Wrapper Project wiz available from Libs panel/node
Product:	apisupport	Reporter:	Jesse Glick <jglick>
Component:	Project	Assignee:	Martin Krauskopf <mkrauskopf>
Status:	RESOLVED FIXED
Severity:	blocker	CC:	jrojcek
Priority:	P3	Keywords:	UI
Version:	5.x
Hardware:	All
OS:	All
URL:	http://apisupport.netbeans.org/50u1-ui.html
Issue Type:	ENHANCEMENT	Exception Reporter:

Description Jesse Glick 2006-01-05 19:54:09 UTC

May be wise to expose the existence of the Library Wrapper Module Project wizard
from

1. The Libraries panel of the module customizer.

2. The (upcoming) Libraries node of the module logical view.

3. "Add >" submenu on the suite's Modules node.

For cases #1 and #2, optionally could have the starting module add a dep on the
new lib wrapper right away.

Comment 1 Martin Krauskopf 2006-01-10 04:24:12 UTC

> 1. The Libraries panel of the module customizer.

Just let's be sure it is ok from the HIE point of view. Since is is supposed
that changes in customizers are not propagated until the user presses OK. This
rule would be broken. Or if implemented (we would delete genereated libraries if
the cancel is pressed) it would look probably odd. CCing Jano. -1 from me.

> 2. The (upcoming) Libraries node of the module logical view.

Yup. As soon as Libraries node is implemented.

> 3. "Add >" submenu on the suite's Modules node.

Really submenu? Or another item "Add Library...". Since now there are "Add
New..." and "Add Existing...".
So probably either submenu and moving there all "Add Xxxx..." all just put it as
a menu item. There are just these menuitem in the meantime so I'm voting for
non-submenu way.

Comment 2 Jesse Glick 2006-01-10 17:14:57 UTC

Re. #1 - we already let user launch Java Platform Manager, NetBeans Platform
Manager, and Library Manager from customizers and make whatever changes there
they want. Only changes made physically inside the customizer dialog are
controlled by its OK/Cancel buttons.

Re. #3 - sure, a new top-level context menu item is fine.

Comment 3 Martin Krauskopf 2006-01-18 15:38:29 UTC

I will implement at least #3 for consistency into 5.0u1.

Comment 4 Martin Krauskopf 2006-01-18 17:07:28 UTC

#3 implemented

ui/Bundle.properties; 1.25 -> 1.26;
ui/SuiteLogicalView.java; 1.28 -> 1.29;
ui/wizard/BasicInfoVisualPanel.java; 1.48 -> 1.49;
ui/wizard/NewNbModuleWizardIterator.java; 1.27 -> 1.28;
www/50u1-ui.html; 1.4 -> 1.5;

Comment 5 pzajac 2006-01-19 10:08:10 UTC

Development of nb plugins is every day easier :-)

Comment 6 Martin Krauskopf 2006-01-31 08:09:00 UTC

#2 implemented. I'm also investigating/prototyping #1. Since it is UI sensitive.
But looks somehow good so far.

../phase-II-ui.html; 1.55 -> 1.56;
ui/LibrariesNode.java; 1.4 -> 1.5;
ui/SuiteLogicalView.java; 1.31 -> 1.32;
ui/wizard/NewNbModuleWizardIterator.java; 1.30 -> 1.31;

Comment 7 Martin Krauskopf 2006-01-31 11:27:08 UTC

#1 implemented. I hope UI is ok - could be tweaked. See the specification (URL).
Or better to look directly in NB - looks quite ordinarily.

www/50u1-ui.html; 1.9 -> 1.10;
ui/Bundle.properties; 1.29 -> 1.30;
ui/SuiteLogicalView.java; 1.32 -> 1.33;
ui/UIUtil.java; 1.24 -> 1.25;
ui/customizer/AddModuleFilter.java; 1.3 -> 1.4;
ui/customizer/AddModulePanel.java; 1.37 -> 1.38;
ui/customizer/Bundle.properties; 1.71 -> 1.72;
ui/customizer/CustomizerComponentFactory.java; 1.7 -> 1.8;
ui/customizer/CustomizerLibraries.form; 1.11 -> 1.12;
ui/customizer/CustomizerLibraries.java; 1.43 -> 1.44;
ui/customizer/SingleModuleProperties.java; 1.50 -> 1.51;
test/unit/ui/customizer/AddModuleFilterTest.java; 1.4 -> 1.5;