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 91723 - OOBE Versionability - UI review
Summary: OOBE Versionability - UI review
Status: RESOLVED INVALID
Alias: None
Product: projects
Classification: Unclassified
Component: Generic Projects UI (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: Milos Kleint
URL:
Keywords:
Depends on:
Blocks: 89629
  Show dependency tree
 
Reported: 2007-01-03 10:28 UTC by jrojcek
Modified: 2012-07-26 10:52 UTC (History)
5 users (show)

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 jrojcek 2007-01-03 10:28:35 UTC 
NB plan issue:
http://www.netbeans.org/issues/show_bug.cgi?id=89629
Comment 1 Jesse Glick 2007-01-06 00:29:40 UTC 
I think this is premature. We have no concrete plan for #89629 yet.
Comment 2 jrojcek 2007-01-15 13:19:02 UTC 
It's planned for 6.0M8 according to #89629.
Comment 3 Jesse Glick 2007-04-02 17:42:09 UTC 
Provisionally reassigning to Dafe, if he has time.
Comment 4 pzajac 2007-05-24 17:06:22 UTC 
I have few comments to UI of OOBE Versionability - UI review:

1) Library manager:

Add button "Load Definitions" is not bad idea. But one will understand what it
is means till he read documentation.  I prefere something like "Add Libraries
Group". I am for to rather select (or create) folder with libraries definition
than to select properties file. The propertis file will be created automatically
if it doesn't exist.  I have for it two reason. 

1)Developer will use shared libraries if he want to store libraries in
versioning repository (CVS). Developers usually store external libraries to a
folder. It's then simplier to transfer global libraries to shared libraries in
folder. It can be done by clicking to an action from popup of Library in
Libraries Manager dialog. 

2)IMHO it's better to show name of folder in libraries group name.
Comment 5 pzajac 2007-05-24 17:14:20 UTC 
Another one comment:
Developer has already created project with global libraries. It will be nice to
be able to move libraries to cvs from popup of library in project. For example
either "Copy to project" or "Copy to shared folder". 
1) Copy to project - It will be created libraries folder if it desn't exist and
library will be copied to it. 

2) copy to shared libraries - Developer will select libraries folder (with
libraries.properties) or create new folder.
Comment 6 Jesse Glick 2007-05-24 17:45:30 UTC 
Obviously the name of the button can be changed to whatever.

Re. copying global libraries to project locations - that is out of scope for
issue #44035, though of course it is fine to discuss the future possibilities.
See issue #49638.

It would be simple enough to change the filechooser to a dirchooser, and assume
a standard .properties file name - e.g. index.properties or
libraries.properties. The chooser could also have some sort of quick option to
pick a conventional location for a given project, e.g.
$projdir/libs/index.properties. However it may make sense to defer such changes
until a GUI for issue #49638 is settled upon.
Comment 7 Jiri Prox 2007-09-17 21:28:41 UTC 
Obsolete milestone, please reevaluate
Comment 8 Milos Kleint 2012-07-26 10:52:18 UTC 
no longer relevant, closing