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 11588 - better enabling and disabling commands
Summary: better enabling and disabling commands
Status: NEW
Alias: None
Product: obsolete
Classification: Unclassified
Component: vcscvs (show other bugs)
Version: 3.x
Hardware: Sun Solaris
: P4 blocker (vote)
Assignee: issues@obsolete
Keywords: UI
Depends on:
Reported: 2001-04-20 02:36 UTC by Rochelle Raccah
Modified: 2006-12-04 22:06 UTC (History)
1 user (show)

See Also:
Exception Reporter:


Note You need to log in before you can comment on or make changes to this bug.
Description Rochelle Raccah 2001-04-20 02:36:25 UTC
I don't think cvs commit be enabled for an up to date file.  I don't think   
cvs remove be enabled on a file which has never been added or committed.
Comment 1 Martin Entlicher 2001-04-20 10:54:59 UTC
Commit should be enabled on Up-to-date files also. You are still able to commit
a new revision by turning "Advanced Options" to true and checking on "Force to

Remove really does not have sense on [Local] files.
Changing product to vcscvs, since CVS support is not built in vcsgeneric.
Comment 2 Martin Entlicher 2001-04-26 11:50:30 UTC
This should be done in a consistent way for all commands. If people from the CVS
team think about other combination of other enabled/disabled commands, please
write it to this issue.
IMO no CVS commands have sense on [Local] files with the exception of CVS->Add.
Therfore we should perhaps remove the whole CVS->... menu and replace it by
"CVS Add" for [Local] files. What do you think ?
Comment 3 Jiri Kovalsky 2001-04-26 13:20:48 UTC
I propose these situations:

Status of the file    Disabled commands
[Locally Removed]     Remove, Diff Graphical, Diff Textual, Export
[Needs Checkout]      Commit, Export, Diff Graphical, Diff Textual
[Locally Added]       Check Out, Export, Diff Graphical, Diff Textual, Tagging,
                      Editing, Watching and Locking, Patch
[Needs Patch] and [Needs Update] probably the same as for [Needs Checkout]

What do other guys think ?
Comment 4 Martin Entlicher 2001-04-26 16:24:14 UTC
Well, I would do some further modifications to this:

Status of the file    Disabled commands
[Locally Removed]     Remove, Update
[Needs Checkout]      Commit
[Locally Added]       Tagging, Editing, Watching and Locking

[Needs Patch] and [Needs Update] the same as for [Needs Checkout].

I've removed Diff Graphical, Diff Textual, Export and Patch, because they can
work on other revisions of the file, than that in the working directory.
Even [Locally Added] file can exist on different branches.
Comments ? Do you think, that this is complete ?
Comment 5 Ann Sunhachawee 2001-04-28 00:46:02 UTC

I don't think this is complete. Earlier in this thread you mentioned [Local]

Status of the file    Disabled commands
[Local]		      [All but Add] <-- wait, can't a user still also do
			graphical or textual diffs as well?

I wouldn't recommend getting rid of all the other commands, i'd just disable
Comment 6 Dirk Ruiz 2001-05-04 17:21:00 UTC
The general rule for disabling vs. removing commands (or objects) is this.  If
there is some (reasonably local) action that the user can take in order to 
re-enable the command/object, then it should be disabled, not removed.  
However, if nothing the user can do will re-enable the command/object, it 
should be removed.  (Some users will go nuts trying to figure out how to 
re-enable a command/object if it cannot be re-enabled.)  So in general I
agree with Ann.  However, having only an amateur's knowledge of CVS, I am
not qualified to decide whether any commands should be removed instead of 
Comment 7 Martin Entlicher 2001-07-31 16:32:09 UTC
More like an enhancement than a bug.
Comment 8 Filip Rachunek 2002-04-30 15:36:36 UTC
UI keyword added.