![]() With short name setting, it's impossible to identify deeply nested folder under consideration without mouse hovering and examining tooltip text. Moreover, aligning will be not comfortable: full string "filename with full path" is not shifted to the left to make filename visible, but just truncated from the right possibly hiding filename itself (which is hte most important part of the string).Ģ. With full paths setting, there will be much repeating garbage with fully qualified path to each modified file. I think that any representation setting will not give comfortable results:ġ. May be you do not face long paths in your synchronizations and that's why current representation is quite comfortable for you?.įor example, consider some very deeply nested subfolder in your sync directory and many modified files inside this folder. For example, in Unison folder path/name is always shown and it is shown only once for each sequence of files from the same folder (and files from this folder are additionally tabbed for convenience) - no textual garbage (repeating long paths that are absolutely the same) and no filename truncation (files from the same folder are shown without any paths, only with tabbing). Additional problem on the second screenshot is that folders are not shown at all! Files with their short names are shown, but folders are completely hidden. ![]() The problem here is not only in short name only mode for folders because they use the same mode as files (and it's hard to identify folder only by it's name if it is located deep in folder hierarchy). The second method show pretty non-truncated filenames without their long paths but it does not allow to identify folders where all these items are located (without manual mouse hovering). The first method (a) will show many truncated names and (b) it is not optimized for many items from the same folder (each item is always listed with it's long path even if this path is absolutely the same as for many previous/next items), it produces mach unwanted textual garbage (repeating long paths for items from the same folder). What can we see with additonal assumptions? Let's assume additionally that path nesting is high (so item names on the first screenshot will be truncated because of long paths) and some of different items a located in the same folder (it's not so on these screenshots but that doesn't matter). Screenshot_20200427_213411.png (20.7 KiB) Viewed 4063 timesīoth show the same items in 2 different view modes: with or without paths. This prevents text garbage.īut the main proposal is just to separate folder / file settings, make them independent from each other. Hiding may be replaced by collapsing/extending by user request. For example, in Unison, if one folder is completely new (on some side) and it contains many new files inside it - Unison just show this folder as one item (marked as new on some side) and do no show all these new files at all - they are hidden because the whole folder is new and the sync action (either auto or manual) is assigned to the whole folder at once. Collapsing or hiding files in folder if they all have the same status. Tabulation for files based on their nesting level (1-2 spaces per tab level is quite enough). Possible additional improvements that should be also mentioned (they are directly related): For example Unison-like view may be easily setup in FreeFileSync: enable full or relative path for FOLDERS and at the same time item name only for FILES - and that's all. I do not ask you to simulate Unison of course, but I think that allowing separate view settings for folders and files at least for full path/relative path/item name option will make FreeFileSync much more flexible and customizable. When I play with FreeFileSync I find items only mode too short (I cannot easily identify the real path because I see only the folder name) and at the same time I think relative/full path mode is too excessive for files - sometimes their names are truncated because of long paths. It sound a bit complicated but it's really very convenient. And at the same time all other files in the same folder do not contain paths at all (no excessive garbage text), but are marked with tabulation to identify that they are from the same folder. So looking at the first entry of the group which is either extended folder path or path of the first file in folder we can easily identify location. It's fully a matter of taste but I find Unison's default compare view a bit more clear for the user because it shows extended paths only for folder or the first file of folder, and all other files in the same folder are just tabbed by several spaces and do not contain paths. Unison is quite a smart application and I never had problems with it, but it's development is actually stalled for many years and it lacks some new features. I'm examining FreeFileSync after using Unison file sync ( ) for many years.
0 Comments
Leave a Reply. |