Source code navigation
Reviews are less effective when the execution path can not be readily followed across files (including those not changed), and symbols cannot be located. This is a serious defficiency in my opinion, leading me to jump over to an editor that supports this, and then back to the review.
5 comments
-
dkarr
commented
@Roy - I have no idea what you're talking about. I don't know what this "version drop-down" is. I don't see anything like that in the compare view. The compare view is not a part of the CC plugin, it's part of Eclipse.
-
AdminRoy
(Admin, Code Collaborator)
commented
@dkarr - this feature request is talking specifically about our web UI. The eclipse plugin can already mostly do what you want - in the diff viewer select "local file" from the version drop-down. Then you can e.g. ctrl-click on a method call, etc...
-
dkarr
commented
This touches on perhaps the only disadvantage of CC vs. the Eclipse Jupiter plugin. Jupiter annotates reviews in the normal source files in Eclipse. In CC, if I want to see the changed files "live" I have to import them manually. That being said, I'm not hopeful anything like this could be implemented in CC (or any similar product).
-
From another user:
I'd love to be able to (within CR/...) go to the P4 tree and see any other file within that branch.
Often, changes will add calls to new functions etc., and I want to go look at the prototype or implementation of those functions to check the parameters or semantics. -
ruza
commented
LXR style cross referencing would be nice.