Benches macOS

15

Finder and Windows Explorer Functionality to be 'Merged'

apple Verified

Imported from the Apple Support Forums via the Wayback Machine 🔗

Right, before I start what I expect will be an epic battle, this is not what I intend this thread to entail...

I have recently moved from being a purely windows user (Software Developer), to using OS X as well. My girlfriends study dictated that I recommended her buying a Mac. Consequently, her inexperience dictated that I should learn OS X in order to be her technical support. Everything until earlier this week was great, but I'm still a lover of the OS.

The aforementioned 'until earlier this week' has caused one major usability gripe with which I have now read up on exstensively; the way that finder handles copying folders.

Now to a certain extent I see why it was slightly naieve of me to think that copying a folder should ONLY replace the files within and not the whole folder, but thats because I have grown up basically Windows only.

So I copied the folder structure (containing organised subfolders) of ALL of my girlfriends university work to date across to the Mac and misinterpreted what the copy would do, it turns out that this replaces the whole folder, and does not move the original folder to trash.

AND NOW TO THE POINT OF THIS THREAD...

As I began, I do not intend this thread to be a Windows vs Mac rantfest. I would merely like to rally up who can see the benefits of merging the way that OS X replaces the whole folder with the Windows options to only replace files within (merge).

This would then allow the possibility of easily copying folders with nested sub-folders (a la windows), but also allow the original method of replacing the destined folder (keeping with the mac tradition).

I don't want to go down the route of 'but every other OS merges folders' because this isn't every other OS, its OS X, and it seems that everything else that they have done, they've done well!

If the proposed could be implemented, not only would it allow more options for existing Mac users, but also allow a smoother crossover for users from other OS's

Perhaps something like below could work.

'The folder <folder name> already exists, do you wish to replace this folder, or merge its contents with the current folder?'

|| Replace || || Merge || || Cancel ||

As I am no expert of usability, the wording above should probably be changed.

Given enough interest (and perhaps a little understanding from long term mac users ;o) ) I wish to inform Apple of this thread so we will all get the best of both worlds (and I won't have a nagging girlfriend with much lost work).

I look forward to your interest/comments (but please keep it nice).

Robsta

Message was edited by: Robsta83

15 replies

Sign in or join Beachball Help to reply.

  1. 0

    Michael Conniff

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Your suggestion has some merit, but it won't attract much attention from Apple here. You should post it to Feedback, where it will get read and logged by Apple personnel.

  2. 0

    Robsta83

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Thanx for the advice Michael, I shall certainly follow that when I hopefully have some eager supporters.

    I must also thank you for keeping to the thread too. :o)

    I just want us to all have a happy mac and windows ecosystem (as good as that ever will be any way). Usability is a key factor for us all after all.

    Robsta

  3. 0

    Robsta83

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    How many Windows to Mac 'converters' have had the same problem here? I have seen a lot of posts along this topic, so guess I'm not alone.

    I just don't understand how a stacked, subfoldered hierarchy could be copied. I'm sure I'm not alone in wanting a best of both worlds option; Merge AND replace.

  4. 0

    Martin.au

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Not just ex windows users. I've been using Mac since 1992 or so and I think it's time to change. The old "replace" method might have been acceptable 10 years ago, but it's 2007. A merge option is essential especially as a lot of people aren't using a single machine anymore. I use a laptop and a desktop and need the ability to merge or sync folders regularly.

    At the moment I'm using a 3rd party app to merge my folders together but this function should definitely be included in the OS.

  5. 0

    R C-R

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    FWIW, "merge" functions are not as simple & straightforward as some might think. This is best shown by example:

    Say one folder hierarchy has a subfolder named "My Stuff" with files "My Doc A" & "My Doc B" in it & another subfolder named "My Other Stuff" with a "My Doc C" file in it. A second folder hierarchy also has a "My Stuff" subfolder with files "My Doc B" & "My Doc C" in it. The two "My Doc C" files are identical, but the two "My Doc B" files are different versions of the same application document ... or maybe documents belonging to entirely different applications with entirely different contents that just happen to have the same name.

    How do you propose that the OS should handle merging these two folder hierarchies without causing data loss, user confusion, or requiring a succession of user requests to choose among the possibilities?

  6. 0

    Robsta83

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Well R-C-R, that is quite simple...

    Any kind of hierarchical folder copying on the Mac would cause huge data loss in this situation.

    First things first, generally files from different applications use different extensions, but for the sake of solving this problem lets say all files involved are .jpg's

    If you have ever used Linux or Windows, they go about this approach on a per file basis, and the key point to make would be to offer the user with a prompt which would allow them to make a decision on whether or not to replace the FILE with the same name. Usually with enough information about the file in question. Windows also offers a replace all files option.

    If you wished to have the option to compare the files then albeit this would not be too difficult, just open them in the case of images, or even implement an application like
    Kdiff to compare the text in that case.

    I do not see where the problem is with asking the user about what they wish to do. At least it is another option to aid the end user, and isn't that what a file manager, and even operating system is aiming to achieve?

    Besides which, currently, OS X does not even use any method to catch the folder that is overwritten... Isn't that what the recycle bin (trash in OS X speak) was put there for?

    The important point is that there should be some way to traverse down the subdirs and copy their contents creating what ever is not there already.

    How does everyone feel about an implementation of that?

    Robsta

  7. 0

    Yer_Man

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Robsta

    If you have ever used Linux or Windows, they go about this approach on a per file basis, and the key point to make would be to offer the user with a prompt which would allow them to make a decision on whether or not to replace the FILE with the same name. Usually with enough information about the file in question. Windows also offers a replace all files option.

    And when you use a Mac you'll learn that if you try to replace a FOLDER with one of the same Name, you will get asked once, about the Folder.

    However, if you grab a fist full of files and try to drag them into a folder with files of the same name, you will get asked about the first one, with the option of Yes, No, and Apply to All. If you select Apply to All, then you won't get asked again, if you simply slect Yes, you'll get asked for each one in turn.

    Besides which, currently, OS X does not even use any method to catch the folder that is overwritten... Isn't that what the recycle bin (trash in OS X speak) was put there for?

    No, it's not. That's for files and folders that you want deleted from the HD - well, as you know, really from the OS's index of the HD. Overwriting is not the same as trashing, just like copying is not the same as merging.

    How does everyone feel about an implementation of that?

    Finally, if you read the terms and conditions that you agreed to when you signed up, you'll realise that polling is not allowed. The forum is for helping each other with technical issues and a whole lot of "me too" and/ or "me not" posts will not do anything. You've been told the way forward is to send feedback, so that's what you do.

    Regards

    TD

  8. 0

    Robsta83

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Terrence,

    Thank you kindly for your two cents. This is not a poll of who likes/dislikes the way that OS X, and only OS X works. It is merely the fact that blatantly a whole bunch of people here want this functionality yet Apple have not responded to the demand.

    I have learned that the Mac replaces my whole folder, but to whom is that helpful? Only people that purely like to REPLACE folders. What about the rest of the world? Like Martin.au for example, a normal, everyday Mac user.

    However, if you grab a fist full of files and try to drag them into a folder with files of the same name, you will get asked about the first one, with the option of Yes, No, and Apply to All. If you select Apply to All, then you won't get asked again, if you simply slect Yes, you'll get asked for each one in turn."

    What about sub folders... Is that catered for? Or do they just get overwritten as well?

    I was wondering how long it would take for someone like you to blatantly misread the relevance of this post. As I'm sure you read, I do not wish to take away the existing functionality, which is IMHO only useful for a handful of cases, but add to this, and help users who have other cases for copying. And is that not helping us all to have one great OS??

    I also stated that there are many areas of OS X that I do like, so don't just pigeon hole me as a Windows user

    The esoteric way that EVERY other OS works is to give the option to merge, not to just overwrite the data. AND YES I mean overwrite, the old data is ALMOST ALWAYS lost as HFS OVERWRITES data not in the allocation table to prevent fragmentation from what I understand.

    So should the old folder data, which is in effect "deleted from the HD" be put into the Trash also???

    As I stated in the first post, I did not want this to be a Mac Fan Boy vs every other OS arguement. So please keep away from that and actually use this thread as a means "helping each other with technical issues" instead of flaming!

    With this in mind, wouldn't added functionality in turn collectively help a vast array of users, and make for a more rounded OS? (Perhaps even bringing OS X further into the forefront of one of the greatest OS's - p.s. I know that Windows has many more issues, and I complain about them also)

    So there!

  9. 0

    R C-R

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    A couple of points to ponder:

    • Folder copying should not result in data loss on the Mac if users heed the warning about the folder's name already being in use & take the simple step of canceling the copy & renaming it.

    • Copying a folder hierarchy to a different location is a very different process from merging the contents of two folder hierarchies. Presumably, most users expect the former to be a one step operation that, once started, results in a faithful copy of the original with no further user interaction involved.

    • I believe that at least some if not most Mac users would assume a merge would be similarly undemanding if it were presented as an alternative to the copy process they initiated.

    • While a simple merge that required no or very few user replacement decisions would not be annoying, the same would not be true as the number increases. So in general, a succession of dialog boxes asking for a decision on one file pair after another isn't a very good user interface for this sort of thing.

    • Because some users are fastidious about folder organization & some aren't, we can't assume that a folder-by-folder comparisons will identify & eliminate duplicates throughout a merged folder hierarchy. I believe this is what most would expect from a useful merge function. Again, a succession of prompts is not a very good way to implement this.

    • For these reasons, I believe merging should be implemented as a separate utility with its own, purpose-designed UI that gives users a better overview of file duplications, name conflicts, & so on.

  10. 0

    Yer_Man

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Robsta

    You miss my point entirely.

    How can you reconcile

    How does everyone feel about an implementation of that?

    and

    This is not a poll

    That's a contradiction right there. A poll is precisely what that is.

    I made no comments about you personally, I made some indications about where the behaviour of the OS is similar to other ones - not for your benefit, but for the benefit of others who may misunderstand the behaviour of the OS from your post.

    Regards

    TD

  11. 0

    Robsta83

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    R C-R,

    You have some very concise points with which all I believe could definately contribute towards a great solution.

    To further the last point, perhaps the dialog box that currently exists could expand to offer the relevant merging procedures where a simple merge just wouldn't suffice.

    Without going into a great deal of detail about the specifics, something like the below in my mind could complement your suggestions nicely.

    || Replace || || Merge
    v || || Cancel ||

    Once clicking on Merge, dialog box would expand...

    || || Replace || || Merge
    ^ || || Cancel ||

    ||-------------------------------------------------------||

    ||-----Source----------||----------Destination-----------||

    ||---------------------||--------------------------------||

    ||---------------------||--------------------------------||

    ||Source file list here||-Destination File list here-----||

    ||---------------------||-(Multi-option tick boxes to----||

    ||---------------------||-accommodate for replace, or----||

    ||---------------------||-keep the specific files and to-||

    ||---------------------||-merge the folders or replace---||

    ||---------------------||--------------------------------||

    ||---------------------||-All folders could be collapsed-||

    ||---------------------||-or expanded.-------------------||

    ||-------------------------------------------------------||

    ||-[]Tick box here to perm. delete to recycle overwrites-||

    ||-------------------------------------------------------||

    I know that its a very rough design and needs some imagination but seems viable, and definitely a better option that that of the windows multi-(pain in the a**e)-dialog box approach.

    **Apologies for the rubbish formatting above, but you get the idea of what it could look like... I'll try and mock up at least a windows version and post, as I do not have any mac tools.

    Robsta

    Message was edited by: Robsta83 (**formatting)

  12. 0

    Robsta83

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Is it not in fact asking someones opinion, perhaps even offering an opportunity for an individual, such as R C-R, to offer such an insightful response??

    In this case one that I have considered with great esteem.

    Pro's and con's.

    Simple science!

  13. 0

    a brody

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    A slightly different angle of approach here can be viewed by how I think Superduper operates. Superduper has a really smart update function in its cloning. It will when updating the clone look for files on a bit by bit basis and see if there are changes to any specific file. If it sees changes, it will ensure that the files that are changed on the original get updated on the clone. It will ensure the files that are deleted on the original get deleted on the clone, and it will ensure that the files that are added on the original get added to the clone when the update is performed.

    Now here in is the problem. Some users actually want OLDER versions to be preserved on their backup but not the original when they copy to the archived backup. We've seen here people are complaining that their archived backup is not preserved by Time Machine:

    http://discussions.apple.com/thread.jspa?messageID=6107525#6107525

    So the problem we are faced with here, is there are different needs for different people when copying files. While some are happy just to maintain a current copy of their files, others wish to manage archives when copying files. So a merge function would have to include the caveat of what does not get preserved when the merge happens. In the face of trying to be simple, you can't be all things for all people. As a freelance technician not working for Apple, I can just say, it probably is best for the user to see how an effort has been made to simplify the process, and work around it if necessary to achieve your needs.

    I've used Windows 2000 and XP Pro and know it asks me whether or not to replace each file that is identical each time I copy from one folder to another when the names are the same. This is a laborious process, saying OK, cancel, ok, cancel if it is done indefinitely. I can see the dialog box asking:

    "Do you want to replace all older files, some older files, with newer files of the same name, or do you want to replace newer files with some older files of the same name?"

    A new computer user would go "Huh???"

    Merge is nice for those of us who can keep track of it in real life.

    For the rest of us who are organizationally challenged, or time challenged, we just want it done right the first time. Unfortunately neither Apple, nor the computer can read everyone's mind.

    I agree a merge function would be nice, but I think it would overly complicate matters.

  14. 0

    Robsta83

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Here is a quick mockup of what I think that R C-R was getting at...

    Sorry in advance for the Window$ theme but I only develop in VS 2005 for M$ Win Mobile devices so don't have any Mac IDE's, you get the idea though...

    User uploaded file

    Upon clicking ||Merge
    v|| the dialog below should be shown:

    User uploaded file

    Second image renders badly if set to full size but click to see original image.

    The tick boxes should be expected to allow for options such as keep original, replace, possibly even add/dont add if the file is not in the destination.

    These could be shown with a different symbol for each action and illustrated in a key somewhere on the dialog box.

    Robsta

  15. 0

    R C-R

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    I don't think expanding a dialog box that currently exists would suffice. Because of the complexities involved in a flexible, intelligent merge utility, I really think it should be just that -- a separate utility. However, I have no objections to a launch button being included in the 'already exists' warning dialog, perhaps with the helpful ability to pass to it the source & target folder hierarchies as a starting point for the utility's options.

    This would be much more "Mac-like" & could make great use of existing Mac technologies & UI formats already familiar to some users. For example, imaging a multi-pane window with list views of each folder hierarchy in two of the panes, & various 'inspector' panes that offered QuickLook views of selected items, tabular or graphic lists of file differences in another, & so on. Each could have an 'exposure' triangle to reveal or hide various levels of detail appropriate to the file type(s) being examined. A very useful feature would be to flag each duplicate or file name conflict in each list (perhaps by color code) & then have the corresponding file(s) in the other list blink when one in the first list is selected, expanding the folder hierarchy to show it's path if it happens to be in another folder. The utility could also offer rename-in-place for any file or folder by simply double-clicking on its name, an option to edit metadata related to but not necessarily in the file itself, & more.

    It is hard to describe how all this could be made both user-friendly & powerful, but by example, if you happen to have Safari's Debug menu activated, check out the rather awesome Web Inspector included in the application. In particular, click on the first Documents item, switch to the "DOM" view (the rightmost tiny icon in the second pair of icon buttons at the top of the window), & then click around on various elements to expose & select their children, properties, & so on.

    I think something like this is necessary to give users sufficient info to decide how to merge large file hierarchies -- for this sort of thing you need both an overview that doesn't overwhelm users with too much info & details appropriate to decide what to do about near-matches, duplicates in different sub-directories, & so on.

    Best of all, this could be implemented much like a change script so that users could study the effects of a merge procedure before implementing it, & possibly even save the changes as a document file (that would update on opening as files were added to either hierarchy) if they wanted or needed to postpone actually implementing the merge until later, or wanted to do this on a recurring basis.

    Toss in Smart Folder support & Time Machine awareness & the possibilities are just about limitless.