Cvs file view

Has the functionality that used to be in the cvs file view been moved to
somewhere else? What I cannot do now for instance is check quickly which
files have been scheduled for removal or filter out only those files
that have been updated and not yet commited to cvs. Is it possible to do
this in another way in aurora?

Pepijn Van Eeckhoudt

11 comments
Comment actions Permalink

Checkin project (control-k) seems to be the new "cvs do it all".

There have been suggestions (complaints :) that invoking checkin (even if
cancel is pressed) is not an adequate procedure if one only wants to see
changes in the project.


0
Comment actions Permalink

I have to say, I think the old CVS File view is an essential feature and should be reinstated. I cannot imagine working with complex projects without it.. badly need to be able filter directory/file structures based on CVS states.

This is the main thing that prevents me from using Aurora on a daily basis instead of 3.0.x

0
Comment actions Permalink

Could you please point the particular usecases where you need the old CVS
file view?

--
Valentin Kipiatkov
JetBrains, Inc
http://www.intellij.com
"Develop with pleasure!"

"Paul Wilton" <no_mail@jetbrains.com> wrote in message
news:22467797.1060291483054.JavaMail.itn@is.intellij.net...

I have to say, I think the old CVS File view is an essential feature and

should be reinstated. I cannot imagine working with complex projects without
it.. badly need to be able filter directory/file structures based on CVS
states.
>

This is the main thing that prevents me from using Aurora on a daily basis

instead of 3.0.x
>
>


0
Comment actions Permalink

Personally, I'd like be able to see an overview of the changes in the
project vs. the repository without having to go into the Commit Project
dialog. This is because the dialog's modal and there's always a risk of you
pressing ok inadvertently - I've done it before and it was very
embarrassing, not to mention the time taken to clean the mistake up.

It seems sensible to have it as another sub-view of the project pane for
which the tree just shows the changed/added/removed files just like the old
cvs file view did.

N.

see also http://www.intellij.net/tracker/idea/viewSCR?publicId=14075,
http://www.intellij.net/tracker/idea/viewSCR?publicId=12644

Valentin Kipiatkov wrote:

Could you please point the particular usecases where you need the old
CVS file view?

>
>

"Paul Wilton" <no_mail@jetbrains.com> wrote in message
news:22467797.1060291483054.JavaMail.itn@is.intellij.net...

>> I have to say, I think the old CVS File view is an essential feature
>> and

should be reinstated. I cannot imagine working with complex projects
without it.. badly need to be able filter directory/file structures
based on CVS states.

>>
>> This is the main thing that prevents me from using Aurora on a daily
>> basis instead of 3.0.x


0
Comment actions Permalink

+1.

I think the CVS commit dialog should be changed so that it was a "CVS view"
without being tied to the commit command. To be able to see all changes
against the repository and perform any CVS operation from that view would
be a massive improvement.

Some example use cases:

  • I want to see the list of all changes I've made in my local copy before

committing them all as a single group. "Commit project" handles this
wonderfully.

  • I want to see the list of all changes before committing the files in

groups according to which feature/issue they are related to. Currently I
have to go to "Commit project", wait while it checks what has changed then
manually exclude all files that aren't part of the group I want to commit. I
have to do this once for each separate group of files I want to commit. It
would be much easier if I could select a group of files from the CVS view
and commit them without the dialog closing.

  • I'm looking at "Commit project", deciding what to commit. I decide I need

to view the history of some files before committing. I have to close the
"Commit project" dialog, open each of the files (or locate them in the
project tree) and choose the "Show history" option from the CVS menu. It
would be much easier if I could do that directly from the "Commit project"
dialog.

Vil.

Nathan Brown wrote:

Personally, I'd like be able to see an overview of the changes in the
project vs. the repository without having to go into the Commit Project
dialog. This is because the dialog's modal and there's always a risk of you
pressing ok inadvertently - I've done it before and it was very
embarrassing, not to mention the time taken to clean the mistake up.

It seems sensible to have it as another sub-view of the project pane for
which the tree just shows the changed/added/removed files just like the old
cvs file view did.

N.

see also http://www.intellij.net/tracker/idea/viewSCR?publicId=14075,
http://www.intellij.net/tracker/idea/viewSCR?publicId=12644

Valentin Kipiatkov wrote:

>>Could you please point the particular usecases where you need the old
>>CVS file view?
>>
>>
>>"Paul Wilton" <no_mail@jetbrains.com> wrote in message
>>news:22467797.1060291483054.JavaMail.itn@is.intellij.net...
>>
>>>I have to say, I think the old CVS File view is an essential feature
>>>and
>>
>>should be reinstated. I cannot imagine working with complex projects
>>without it.. badly need to be able filter directory/file structures
>>based on CVS states.
>>
>>>This is the main thing that prevents me from using Aurora on a daily
>>>basis instead of 3.0.x



--
Vilya Harvey
vilya.harvey@digitalsteps.com / digital steps /
(W) +44 (0)1483 469 480
(M) +44 (0)7816 678 457 http://www.digitalsteps.com/

Disclaimer

This e-mail and any attachments may be confidential and/or legally
privileged. If you have received this email and you are not a named
addressee, please inform the sender at Digital Steps Ltd by phone on
+44 (0)1483 469 480 or by reply email and then delete the email from
your system. If you are not a named addressee you must not use,
disclose, distribute, copy, print or rely on this email. Although
Digital Steps Ltd routinely screens for viruses, addressees should
check this email and any attachments for viruses. Digital Steps Ltd
makes no representation or warranty as to the absence of viruses in this
email or any attachments.

0
Comment actions Permalink

That second use case is a strong one for me. As described, I used to use the cvs view to selective commit groups of files all the time.

And the folks on my team like to just view what they've changed periodically, and having to hit the "Commit" button to do that is not intuitive.

0
Comment actions Permalink

There seem to be a few separate SCRs for this (there were links to two
earlier in this thread). Do you (or anyone else) know which we should be
voting for?

Vil.
--
Vilya Harvey
vilya.harvey@digitalsteps.com / digital steps /
(W) +44 (0)1483 469 480
(M) +44 (0)7816 678 457 http://www.digitalsteps.com/

Disclaimer

This e-mail and any attachments may be confidential and/or legally
privileged. If you have received this email and you are not a named
addressee, please inform the sender at Digital Steps Ltd by phone on
+44 (0)1483 469 480 or by reply email and then delete the email from
your system. If you are not a named addressee you must not use,
disclose, distribute, copy, print or rely on this email. Although
Digital Steps Ltd routinely screens for viruses, addressees should
check this email and any attachments for viruses. Digital Steps Ltd
makes no representation or warranty as to the absence of viruses in this
email or any attachments.

0
Comment actions Permalink

On Mon, 11 Aug 2003 10:07:13 +0100, Vilya Harvey
<vilya.harvey@digitalsteps.com> wrote:

+1.

>

I think the CVS commit dialog should be changed so that it was a "CVS
view" without being tied to the commit command. To be able to see all
changes against the repository and perform any CVS operation from that
view would be a massive improvement.

>

Some example use cases:

>

  • I want to see the list of all changes I've made in my local copy before

committing them all as a single group. "Commit project" handles this
wonderfully.

>

  • I want to see the list of all changes before committing the files in

groups according to which feature/issue they are related to. Currently I
have to go to "Commit project", wait while it checks what has changed
then manually exclude all files that aren't part of the group I want to
commit. I have to do this once for each separate group of files I want to
commit. It would be much easier if I could select a group of files from
the CVS view and commit them without the dialog closing.

>

  • I'm looking at "Commit project", deciding what to commit. I decide I

need to view the history of some files before committing. I have to close
the "Commit project" dialog, open each of the files (or locate them in
the project tree) and choose the "Show history" option from the CVS menu.
It would be much easier if I could do that directly from the "Commit
project" dialog.

>

Vil.

>

Nathan Brown wrote:

>> Personally, I'd like be able to see an overview of the changes in the
>> project vs. the repository without having to go into the Commit
>> Project
>> dialog. This is because the dialog's modal and there's always a risk of
>> you
>> pressing ok inadvertently - I've done it before and it was very
>> embarrassing, not to mention the time taken to clean the mistake up.
>>
>> It seems sensible to have it as another sub-view of the project pane for
>> which the tree just shows the changed/added/removed files just like the
>> old
>> cvs file view did.
>>
>> N.
>>
>> see also http://www.intellij.net/tracker/idea/viewSCR?publicId=14075,
>> http://www.intellij.net/tracker/idea/viewSCR?publicId=12644
>>
>> Valentin Kipiatkov wrote:
>>
>>> Could you please point the particular usecases where you need the old
>>> CVS file view?
>>>
>>>
>>> "Paul Wilton" <no_mail@jetbrains.com> wrote in message
>>> news:22467797.1060291483054.JavaMail.itn@is.intellij.net...
>>>
>>>> I have to say, I think the old CVS File view is an essential feature
>>>> and
>>>
>>> should be reinstated. I cannot imagine working with complex projects
>>> without it.. badly need to be able filter directory/file structures
>>> based on CVS states.
>>>
>>>> This is the main thing that prevents me from using Aurora on a daily
>>>> basis instead of 3.0.x
>>
>>
>>
>
+1


--
Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/

0
Comment actions Permalink

The second use case is of particular need for me. I don't think the current approach is very intuitive, and as someone else mentionned, it opens a door into a world of error that I do not wish to enter.

The third use case could probably be easily integrated into the CVS file view if it were to come back.

Cheers

0
Comment actions Permalink

Seems like there are a lot of strong views on this..
The use cases posted by Vilya pretty much sum up my thinking.

I think it is incorrect to have to goto Commit Project to see (narrow down) the changes that have been made.. and risky.

Another solution/idea might be to have CVS filter buttons in the main project tab, so as well as the like of 'flatten packages' and 'view members' there is also 'hide missing files', 'hide unknown files' etc..

0
Comment actions Permalink

On my box, I always have smartcvs up in one of my monitors. I use it for
all the reasons others have posted. Any usecase you can identify for a
smartcvs or wincvs like tool, could be applied to idea.

Mainly, I find it invaluable to be able to, at a glance, see the scope
of my current changes, quickly do diffs, look at a version tree, etc.
All in completly modeless. Where as with idea, many of the cvs actions
are modal, which greatly limit their usefullness.


Valentin Kipiatkov wrote:

Could you please point the particular usecases where you need the old CVS
file view?


0

Please sign in to leave a comment.