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: | Put wizard utils somewhere public | ||
---|---|---|---|
Product: | platform | Reporter: | Rochelle Raccah <raccah> |
Component: | Dialogs&Wizards | Assignee: | Jiri Rechtacek <jrechtacek> |
Status: | RESOLVED WONTFIX | ||
Severity: | blocker | CC: | abadea, mkrauskopf |
Priority: | P3 | Keywords: | API |
Version: | 5.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | ENHANCEMENT | Exception Reporter: |
Description
Rochelle Raccah
2006-08-12 00:05:58 UTC
Please, describe the use-cases and some justification what methods should be public and who will use these method. It's need to consider where should publish them. Thanks The use case is any wizard which creates a set of files and therefore cannot use JavaTargetChooserPanel directly. Mostly those wizards create their own ui including a PackageView (examples: entity from db, jsf from entity, etc). For each of the 3 points: 1 & 2) Allow usage of a smaller component (than the whole JavaTargetChooserPanel) which automatically update the wizard's valid status with an error if an unwritable dir is chosen. Alternatively, introduce another kind of Panel like JavaTargetChooserPanel which allows the use of customized ui. Or, have some kind of wizard utils class which has methods similar to the isValid and canUseFileName methods in JavaTargetChooserPanel. For the case of existing file, there needs to be something like canUseFileName because the target folder package is not sufficient to do the test A similar check for a valid identifier would be the same case. 3) Here we see that the methods which would be useful canUseFileName and existsFileName are already copied into JavaTargetChooserPanel from somewhere else. To me, that reinforces the idea that they should be shared from somewhere else. It's not planned for long time. It's fair to close as WONTFIX |