Enumerating modified files

[GoogleCodeExporter]

Feature idea,

I think it would be useful to have a dialog or some other way to clearly
enumerate a list of the files that are modified/unknown/added in a project
folder.

I noticed this as useful when I added a project with a very large amount of
files and subdirectories to the plugin to work with. With the tree control
it gets a little difficult to see what files are modified when they are in
different folders and spread through the tree, selecting all of them to
commit becomes even more difficult because expanding a tree node causes the
selection to be lost.

It may be possible to copy/reuse much of the code in the History window to
 create the ui component of such a dialog.

Original issue reported on code.google.com by CodyPrec...@gmail.com on 7 Sep 2007 at 9:45

[GoogleCodeExporter]

This isn't possible with the way things work in the Projects pane.  It might be 
able to track the 
added/modified/etc. files that are visible, but once a folder is collapsed, it 
doesn't track that information 
anymore.  Is it really necessary though?  You can select the top level folder 
and do a commit of that.  Then the 
source control commands will determine what files need to be pushed.

Original comment by Kevin.Da...@gmail.com on 7 Sep 2007 at 1:07

[GoogleCodeExporter]

It was more an idea of the moment than anything I suppose. If it would require 
design
changes then I would say its not necessary.

Original comment by CodyPrec...@gmail.com on 8 Sep 2007 at 12:05

[GoogleCodeExporter]

As a compromise, when collapsing a folder containing modified files (or 
folders),
maybe the folder could be marked modified? Better yet, mark the folder modified 
as
soon as a modification to its contents is detected.

Original comment by ronw.m...@gmail.com on 23 Jun 2008 at 2:39

[GoogleCodeExporter]

Yea, I have been thinking about this issue again. What I would like to do is to 
add 
another menu option that shows itself when a context click is sent to a 
directory 
that would do a (recursive) status check on the directory and pop open a list 
control in the Shelf with the status of files found in that directory. I think 
that 
this may not even require any additions to the SourceControl interface as the 
existing status command could be used to retrieve the neccessary data in most 
cases 
and would simply need to be re-routed to the list control.

From the list control in the Shelf one could then manage the checkins, ect... 
This 
would also be a solution for the issues with doing a remove from repository, 
where 
you cannot commit the removal from the interface.

I am planning to try and put some effort towards this plugin again before the 
next 
release, so if it sounds good I might be able to implement.

cody

Original comment by CodyPrec...@gmail.com on 24 Jun 2008 at 1:03

[GoogleCodeExporter]

I have worked with SVN, at least, and when you remove something from the 
repository,
you have to commit the removal from a directory above the removal. I's be 
surprised
if this was a problem from the Project panel.

Of course, I don't know about the other VCS options.

Original comment by ronw.m...@gmail.com on 24 Jun 2008 at 10:31

[GoogleCodeExporter]

Started on a new component for listing the state of the repository on a whole 
in the
Shelf.

Should be ready for next release.

Original comment by CodyPrec...@gmail.com on 23 Oct 2008 at 3:00

• Changed state: Started

[GoogleCodeExporter]

Done

Original comment by CodyPrec...@gmail.com on 24 Oct 2008 at 4:16

• Changed state: Fixed

[GoogleCodeExporter]

Move old 'fixed' issues to verified

Original comment by CodyPrec...@gmail.com on 3 Feb 2009 at 8:18

• Changed state: Verified