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: | better control of VCS status display | ||
---|---|---|---|
Product: | obsolete | Reporter: | John Jullion-ceccarelli <johnjullion> |
Component: | vcscore | Assignee: | Martin Entlicher <mentlicher> |
Status: | RESOLVED FIXED | ||
Severity: | blocker | ||
Priority: | P3 | ||
Version: | 3.x | ||
Hardware: | PC | ||
OS: | Windows ME/2000 | ||
Issue Type: | ENHANCEMENT | Exception Reporter: | |
Bug Depends on: | |||
Bug Blocks: | 35564, 35640 |
Description
John Jullion-ceccarelli
2002-08-01 15:58:54 UTC
Well, generally I agree. Perhaps there can be two versions of annotation property editor. One simple with just Status, Revision Number and Sticky Tag with predefined structure allowing just show or hide them. It's IMHO still handy to have the full annotation property editor as it is now for power users. It can replace the simple property editor when [Expert] button is pressed. What do you think? As to "Show file status in Source Editor tabs", this has to be implemented in openide. There is issue #19229 already filled for this. I suppose we can leave this for advanced users. I don't really like the node approach, but it works good enough if it isn't the only way users can do this. The problem is that if we integrate javacvs into generic vcs with a profile, then all the global javacvs properties, including this one, will disappear. All global properties, that are currently maintained by javacvs would have to be implemented by vcscore. It would have sense for most of them. It would probably be necessary to create another module, that will hold all CVS specific dialogs and actions (including CVS connection manager, etc). This is going to be solved by issue #25139. Note also patches re HTML status |