3 ms·
Looks like a cool utility. I will probably be well received by those who rely on dragging and dropping. I personally never drag-and-drop unless it is the only
by robomartin 15y ago
Looks like a cool utility. I will probably be well received by those who rely on dragging and dropping.
I personally never drag-and-drop unless it is the only way to get something done. Copy and Paste via the keyboard is faster and far easier to use. It also gives you all the time you need to navigate wherever you need to go.
Further to that, because I switch between platforms multiple times per day I just can't deal with the weird keyboard mappings on the Mac. Weird, of course, from the perspective of any other platform. If you are only on Mac it is very likely that everything else feels weird to you. I get it.
For example, I wanted copy and paste to be Ctrl-C and Ctrl-V. I wanted the editor in Xcode to behave like most other editors behave in other platforms and IDE's. I'm old school, for me the keyboard can be far faster than going for the mouse/touchpad/trackball all the time.
My solution was to install KeyRemap4Macbook (no affiliation) and make the Mac keyboard mimic Windows/Linux keyboard and mappings as much as possible.
I won't be buying your app, but great job. Like it a lot. Apple should buy it off you and integrate it into the OS. It's that good.
- jacobolus 15y agoThe problem with keyboard or menu cut/copy/paste (hereafter c/c/p) is that it’s a mode (or at least a sort of quasi-mode), and modes are a fundamentally inhumane user interface approach that shift cognitive burden from computers to humans. The traditional c/c/p includes no visual feedback whatsoever, is an extremely overloaded concept (many types of objects can be copied, the result of pasting depends on context and there’s no way to tell precisely what will happen from past experience with other applications, sometimes a copy instruction only places a link to the content (for performance reasons) so that closing a document or application alters the paste behavior, c/c/p between applications is often brittle, especially when dealing with rich text), and is very limited and inflexible (no way or bad ways (depending on the implementation) to copy two things and then paste them back, copying another thing destroys the user intent of the previous copy operation and can’t be undone, no visual/spatial context is provided for the operation, etc. etc.). C/c/p is better than what came before it (it was invented at PARC in the early 1970s, and the alternative was much more mode-ful, something like vim), but is still too unfriendly for novices and too limited for experienced users. Unfortunately, it is so ubiquitous that it has forced all users to learn it, forced all software to implement it, and crowded out alternative approaches, even in contexts like file managers where the concept doesn’t really make sense. The best we can typically hope for is extensions of the typical c/c/p interaction which work like other implementations in the simple case but have some extra functionality for experienced users. These are usually entirely undiscoverable, and still share most of the problems of the traditional c/c/p.
- lukeschlather 15y agoI'm not sure I follow where you're coming from. The biggest thing that I don't understand is what the alternative to c/c/p is. I feel like drag and drop is an even fuzzier metaphor than c/c/p. At best it has most of the issues you've outlined with c/c/p. But, I'm an Emacs user, so c/c/p is instinctual. If everyone grew up using Emacs people would probably be writing papers about how chaining keystrokes is some sort of deeply evolved human skill.
- jacobolus 15y agoThere are many possible alternatives to c/c/p in “idea space”, and the little details matter. A better system, though, would have some of these properties: it would persistently store cut/copied content in some kind of list, at least content of manageable size; it would have some way to see the clipboard visually/spatially; it would interact with drag/drop; it would give some visual indication that there was currently copied content, and perhaps the type as well; it would allow a user to interact with the history of cut/copied items in a more flexible way both from keyboard and mouse; it would allow easy conversion of copied chunks into “documents”/“files”/“pages” in their own right. Many of the problems here intersect with the problems of our current files + hierarchical filesystem + semi-spatial file browser + open/save dialog system for dealing with “content” in general. Ideally, a generally more intuitive and flexible basis for these problems would be built, and the replacement for c/c/p would integrate with these other tools. That’s sort of wishful thinking though. (Well, the idea of replacing c/c/p is also probably wishful thinking. Systemically different approaches like the Canon Cat word processor are all pretty much dead by now.)
- JackC 15y agoMany of your requirements are met by Ditto (on Windows) and ClipMenu (on the Mac). The basic model is: Ctrl-V pastes like usual, Ctrl-Shift-V pops up a menu of every previous paste. Previous items can be selected and pasted using either the keyboard or the mouse. This gives you persistence, visual display of the clipboard, and keyboard and mouse interaction with the history. And it turns out to be insanely useful. Oh man. I would never go back.