VCS usability--distinctions without a difference?

What is the rationale for giving CVS and Subversion special treatment in
IDEA's user interface? For example, why is there a "Check Out from
Version Control" menu item with a sub-menu containing entries for CVS
and SVN (not to mention "Browse CVS repository" and "Import into CVS"
commands). Given the work done in 6.0 to provide a uniform set of VCS
capabilities, is it time for this to change? It has the effect of making
the VCS interface less convenient to use on projects that don't use CVS
and SVN.

1 comment
Comment actions Permalink

Hello Michael,

What is the rationale for giving CVS and Subversion special treatment
in
IDEA's user interface? For example, why is there a "Check Out from
Version Control" menu item with a sub-menu containing entries for CVS
and SVN (not to mention "Browse CVS repository" and "Import into CVS"
commands). Given the work done in 6.0 to provide a uniform set of VCS
capabilities, is it time for this to change? It has the effect of
making the VCS interface less convenient to use on projects that don't
use CVS and SVN.


While it's true that we strive for more uniformity in the version control
capabilities, we do not want to spend time implementing features only for
consistency purposes. Could you please describe what VCS are you using, what
operations supported for CVS/SVN are you missing for that VCS, and how would
you like to use them?

For example, Perforce doesn't really have a "check out" operation in the
same sense as for CVS and SVN.

--
Dmitry Jemerov
Software Developer
JetBrains, Inc.
http://www.jetbrains.com/
"Develop with Pleasure!"


0

Please sign in to leave a comment.