![]() > I think I would mind //graphical menus// less than the change to an always in your face ribbon. For all that I know, there is a super common case for "-group" without "-owner", and this is just me not knowing about it. If I were trying to do a popular product, I'd have to spend some time asking people / looking at the forums to determine which sets of features do people use. this was just my subjective design, based on how I use the program. Most of the time, first three options would be fine, but "custom" will show entire new group of checkboxes. A good design might have a dropdown: "everything", "nothing", "x-bit only", "custom". This will decrease cognitive load because there are less things to read and there is no need to worry what happens if you check both.Īnother great GUI feature is dynamicity - take the metadata for example. There is a very wide variety of input elements, so checkboxes are are not the right solution all the time! For example, while having separate "-verbose" and "-quiet" options is fine for CLI, one would expect to see a drop-down or a slider in the GUI. Having "hardlinks" all the way on the left and "symlinks" all the way on the right does not make a good GUI. One area of the screen would be options related to what is transferred, a second area is metadata, the third one is speed-only optimizations, fourth is logging and so on. There should be some sort of logical grouping. This is the hard part about GUI design - it is pretty easy to make a list of 100 command-line options listed alphabetically on the man page, but for GUIs, people expect much more. No timeline for a fix, however-or even a commitment to modify the Drobo’s SMB configuration.> Is it better to make up common rsync “recipes” for people to use, or is it better to let folks have access to ALL of the flags and pick’n’mix what they want? ![]() I’ve been in contact with Drobo customer support and they acknowledge this pathological behavior. (No matter what file-copy tool is used this is not an rsync problem.) So the while the content of the files will be unaltered when you make a round trip between a Mac and a Drobo, the file permissions in most cases will not be correct when you move the file back to the Mac. Unlike other Linux-based servers, the Drobo 5N’s SMB configuration automatically and quite nonsensically modifies the permission bits on files transferred from an OS X filesystem. Drobo’s implementation of the SMB protocol is, to put it as charitably as possible, nonstandard. There is one endemic problem keeping files synchronized between a Mac and a Drobo. You’ll need to be comfortable with command-line tools to use it, however. ![]() Rsync (part of the free Apple Xcode developer’s bundle for OS X) is quite reliable and has features to maximize file synchronization efficiency. ![]() I have a large lightroom library on my mac that will change often - and so far syncing from the mac seems painfully slow - often times it will hang. So if I’m backing up to my Drobo 5N what’s the best way to keep stuff “in sync?” Shall I use a utility to do this or is there some app that I can have the Drobo to “monitor” a remote folder and automatically update? ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |