Tag Info

New answers tagged

13

Start by figuring out what you want to communicate Since you are (rightly) looking for a reasoned, non-hacky way to lay this out, you can start with first principles. 1. Understand the layout pattern The layout you're trying to use is a common one....I call it the mini-map or navigator pattern although there is probably a more correct UX term for it. ...


12

Broken axes are only useful if they are intended to be used sparingly. If, as you say, the axis is broken everywhere, it makes more sense to use a table instead describing the relevant points. +-------+-----------+------+ | Depth | Structure | Icon | +-------+-----------+------+ | 0 | Oil Rig | A | | 6100 | Foo Pipe | F | | 6200 | Bar Pipe ...


34

You could: Remove the axis line entirely. If the diagram is not to scale, then the axis line itself is the confounding/confusing element of the UX that is causing failed perception. Use simple labels attached to sections that are set off from each other only in the sense of a list. You could put a larger space between items that are spaced farther apart, ...


1

Although I can't produce a graphic, I'd go with your first inclination, to use the 'zig-zag' indicators. They're pretty much everywhere and I think users would intuitively understand what they mean. However, the way you've used them isn't great with your use case, as you've noticed. I'd recommend having a range of depth for each section instead of the ...


17

I have graduated as a Petroleum Engineer, so perhaps I can help you here. This is a domain specific problem and the right solution depends on the kind of equipment you're using in the oil well. Let me give you a few examples here. It's slightly technical but I'll try my best to explain it clearly: Example 1: Casing Installation You do well casing before ...


3

As answered by JeromeR the Save paradigm is a byproduct of early hardware software design. For simplicity I am only going to talk about two types of memory. "Save" actually means moving information from temporary memory (RAM) to permanent memory (Hard disk, flash ROM, etc). Temporary memory (RAM) can only keep information while it is powered on. Permanent ...


3

It's an Engineering decision That simplifies and complements some of the features Google docs boasts about Real-time Collaboration Offline editing Revision history Cloud storage ...allowing the user to focus only about writing/editing the content while the technology ensures that their precious content is always preserved. Content you edit on the ...


3

FYI, they used to have a save button in Google Docs: http://googleappsupdates.blogspot.com/2010/02/new-saving-buttons-in-google-docs-and.html however, it's been removed in Google Drive. I can't find anything online stating why they removed it, so can only speculate. Given that Google is an engineering centric organization my guess is that the change came ...


37

Save is a byproduct Save is a byproduct of early hardware- and software design. It doesn't have a common equivalent in the real world. Consider: If you take a pencil and make a mark on paper, that mark doesn't require an extra step in order to become permanent. In other words, it does not need to be saved. The paper may need to be stored somewhere so it ...


0

Give the user a chance to see examples. On iOS, there's a help button when Siri is listening. Tapping it gives you suggestions on things it can do:


1

I think command based systems always come with a learning curve because ultimately you're giving a command. Affordances are not present for CLI or command based tools. The only option I can think of is context-sensitive tab-completion or context-aware suggestions. Related discussion on Hacker News. That being said, the example you've quoted reminds me of ...



Top 50 recent answers are included