Export from working copy

[GoogleCodeExporter]

Feature request to be able to export folders and files not only from the 
repository but from local files too.

Thank you.

Original issue reported on code.google.com by rodriggo...@gmail.com on 5 Sep 2010 at 4:37

[GoogleCodeExporter]

If you mean moving folders and files from a local directory to the repository, 
this is called "import"--look in the repository window.
If you mean moving folders and files from a local directory to the working 
directory, then you should just copy them, I would expect.

If you're requesting a locally hosted repository, that's a duplicate request 
(54): http://code.google.com/p/svnx/issues/detail?id=54&q=local

Original comment by vanc...@gmail.com on 13 Sep 2010 at 7:43

[GoogleCodeExporter]

Thank you, but what I mean was to be able to export folders from a working copy 
(local) to another local folder. If I simply copy the working directory using 
Finder, folders with .svn name will be copied too.

What I am suggesting is to make the Export button (in the repository window) to 
work in the working copy window too. This is needed in case you have a large 
folder that need to be exported (get rid of .svn folders). Because today we 
only could export it from the repository, which (most of the time) is online.

Sorry my bad english.

Original comment by rodriggo...@gmail.com on 13 Sep 2010 at 8:31

[GoogleCodeExporter]

I understood the OP was requesting that svnX support the `svn export 
<folder-in-WC> <other-folder>` command.

Unfortunately it is not as simple as just copying the Export toolbar item from 
the Repository window to the Working Copy window :-).
I would like this command to be able to export multiple, selected, files & 
folders.  In a Repo window all items in a multiple selection are in the same 
folder & are thus all are exported to the same (local) folder.  In a WC the 
selection may encompass items at varying folder depths.  So how should they be 
exported?

The request has been noted & added to my TO-DO list.

[Rodriggomuniz, there's nothing wrong with your English.]

Original comment by chris...@gmail.com on 13 Sep 2010 at 11:20

• Changed state: Accepted
• Added labels: Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

This is great! If there's a problem with the way of displaying folders and 
files in a WC, I think this could be solved showing the same list from Repo 
window, but using local data after we click in the Export button and before 
choosing the destination folder.

For instance, Tortoise SVN exports local items by selecting the source, 
selecting if unversioned items will be exported and then selecting the 
destination. This could give you guys an idea.

Original comment by rodriggo...@gmail.com on 14 Sep 2010 at 12:54

[GoogleCodeExporter]

I'm not really sure what you mean.
I think the obvious parts of this are obvious & don't require discussion.

The `svn export` command only provides support for exporting 1 item from a 
directory at a time.
[That limitation is hidden by svnX's Repo Export & Open commands and also 
should be by an svnX WC Export command.]

The issue is not with: Select 'item1' & 'item2' -> Export -> choose dest folder
    -> 'item1' & 'item2' are written into dest folder.  [Obviously]
It's with: Select 'folder1/item1' & 'folder1/item2' -> Export -> choose dest 
folder
    -> Do we write 'item1' & 'item2' into <dest> folder or into <dest>/folder1?
And with: Select 'folder1/item1' & 'folder2/item1' -> Export -> choose dest 
folder
    -> what should we do?
And with: Select 'folder1' & 'folder1/item1' -> Export -> choose dest folder
    -> what should we do?
And with ... any other edge cases you can think of.

[I don't really care what other apps do.  I'm more interested in providing a 
good Mac user interface/experience.]

Original comment by chris...@gmail.com on 14 Sep 2010 at 11:06

[GoogleCodeExporter]

Let me see if I can clean this up: What I'm trying to suggest as a solution is 
to add an extra window for the "local Export button". If is possible to export 
from an online repository because the window let me select the items only the 
right way (1 item from a directory at a time), if I press the Export button on 
the WC window, svnX could open that same window model but with local items 
listed. Is it possible? (Just an idea).

[Don't take me wrong. I'm not comparing apps, but I don't think using other 
apps as an example could do harm. As an interface designer (that's why I use 
this app, great UI and I not a huge fan of line-cmd), when we're designing 
things we search to lots of references. The bad and the good ones.]

Original comment by rodriggo...@gmail.com on 15 Sep 2010 at 2:16

[GoogleCodeExporter]

I think you are missing the point I was trying to make.

SvnX allows you to export multiple items from the repo with one command.
Subversion only supports one-at-a-time.  Therefore svnX improves upon this.
However, this was simpler in the repo as the multiple items must be in the same 
directory due to the nature of the interface & thus they must all have 
different names & there is no ambiguity.

As a user I would also like to be able to export multiple items simultaneously 
from the WC.
(After all most commands now work on multiple items in the WC.  It's an 
important part of the user experience.)
However, for export, this is complicated by the fact that multiple selections 
in the WC are not restricted to a single folder.
It would be bad to add this restriction.
It is important that I consider the edge cases.
You suggested the feature, so I thought you would like an opportunity to say 
what you think should happen in these edge cases.
(That's why I asked the questions - not because I don't know what to do.)
It doesn't mean I'm going to take any notice of what you suggest, but it also 
doesn't mean I won't :-).
Or to put it another way - tell me what you want svnX to be able to do, and let 
me figure out how to do it.

[Adding a new window that presents a (columnar) view of the WC so that the user 
can only select items in a single directory, doesn't seem right to me & is 
unlikely to happen.  The columns in the repo are populated via `svn list` the 
WC item list is populated via `svn status`, two very different things.]

My inclination is to make svnX ‘do the smart thing’ and only ask the user 
to intervene if necessary.

Original comment by chris...@gmail.com on 15 Sep 2010 at 4:10

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Added in svnX 2.0b1.

Original comment by chris...@gmail.com on 24 Aug 2015 at 7:00

• Changed state: Fixed