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.
Users have complained about VCS status display taking up too much room in the Explorer and especially in the Source Editor tabs. We now have two ways of dealing with this. Javacvs has a dialog which IMO is not intuitive and gives users more control than they want (I don't think users care about the order in which information is displayed or what separators are used). Generic VCS has the one property that just shortens the status names, which isn't enough. I'd like to see one dialog for both systems (won't be a problem if we make a profile for javacvs and integrate it in generic vcs). It would look something like this: Choose which types of VCS status information you want to display for each file: Status Revision Number Sticky Tag _ |_| Show file status in Source Editor tabs This way users could choose to have full status information in the Explorer but not take up room in the Source Editor tabs.
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