subcommander.tigris.org

I really like subcommander, but I have been running into one
 
annoyance, and I am wondering if I just haven't figured out
how to  
use it right:

Is there a way in subcommander to add items by default? For
example,  
when I add a new file to my checked out working copy, I
currently go  
into subcommander and right-click on the file and select
'Add Item'  
and it then is marked to be uploaded to the repository. I
would  
prefer to have it automatically add new items, and delete
missing  
items, when I perform a commit. I would be fine with a
Messagebox  
asking me if I was sure, but I don't like having to browse
through  
the list on each commit and manually confirm that I have
added each  
new item.

Thanks,
Josh

------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribesubcommander.tigris.org
For additional commands, e-mail: dev-helpsubcommander.tigris.org

Hi,

Josh Rochester wrote:
> I really like subcommander, but I have been running
into one annoyance, 
> and I am wondering if I just haven't figured out how to
use it right:
> 
> Is there a way in subcommander to add items by default?
For example, 
> when I add a new file to my checked out working copy, I
currently go 
> into subcommander and right-click on the file and
select 'Add Item' and 
> it then is marked to be uploaded to the repository. I
would prefer to 
> have it automatically add new items, and delete missing
items, when I 
> perform a commit. I would be fine with a Messagebox
asking me if I was 
> sure, but I don't like having to browse through the
list on each commit 
> and manually confirm that I have added each new item.

Subcommander can't do that at the moment.

How would the ui look like?
I can imagine  a list of added (missing) items and a way to
remove items from 
the list before auto-adding (deleting) them. Maybe as part
of the commit 
dialog.. Or simply two new commands "add (all)
unversioned" and "delete (all) 
missing)" unrelated to the commit command.

Alt least it should be optional and not an extra step before
i can select commit.

-- 
Martin

Subcommander 1.2.2 - http://subcommander.ti
gris.org
a cross platform Win32/Unix/MacOSX subversion GUI client
& diff/merge tool.

------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribesubcommander.tigris.org
For additional commands, e-mail: dev-helpsubcommander.tigris.org

Hi,

Josh Rochester wrote:
> Part of the commit dialog would be good. I'd make it
some check boxes to
> the left of the 'List Items' button. These check boxes
should persist
> between uses, so they are automatic, if set that way.
Alternatively, an
> 'Options' button that opened a dialog of persisting
options, in case
> there are more, would work.
> 
> I'd also add the 'Add (all)' and 'Delete (all)'
commands to the context
> menu of the working copy bookmark. 
> 
> What do you think?

Sounds good. I just can't promise that it will make it into
2.0.0.
Although it doesn't sound very complicated.. let's see..


> Josh

-- 
Martin

Subcommander 1.2.2
Subcommander 2.0.0 Beta 1

http://subcommander.ti
gris.org
a cross platform Win32/Unix/MacOSX subversion GUI &
diff/merge tool.


------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribesubcommander.tigris.org
For additional commands, e-mail: dev-helpsubcommander.tigris.org