Thanks, everyone, for the feedback thus far. Let me clarify why it's
important that I come up with a common terminology that people
understand: I'm writing installation instructions for a client that
provides a service that works with different blog services, so being
able to call something o
I guess a good approach could be addressing the parts at their
information architecture level: TOP LEVEL navigation, SECOND LEVEL
navigation, and so on; after all, "tabs" is just the current UI
pattern you're using in your design solution... if you decide to
change for drop-down/collapsible trees/e
>I don't know if I understand why we often try to find special
>descriptions to call things.
Having a commonly understood set of terminology makes life infinitely
easier during meetings. I find that half of the roadblocks we face
during design meetings are caused by terminology misunderstandings.
I don't know if I understand why we often try to find special
descriptions to call things.
The more that Rich interfaces become common, designers will make
attempts to create interactions and UI elements that "work" to solve
"the problem".
In the example you sent, it looks to me like a series of "t
On Jun 6, 2008, at 3:56 PM, Jason Zietz wrote:
What would you call "Current Design" in this example?
Invisible.
Jared
Welcome to the Interaction Design Association (IxDA)!
To post to this list ... [EMAIL PROTECTED]
Unsubscr
My humble recommendation would be navigation (links) and subnavigation (links),
since tab or no, that's what they are and do, right?
It's what I call such elements in most documentation since it allows
flexibility of use
if the design turns away from presenting them as tabs.
Scott
On Fri, Jun 6,
A bit of clarification: I'm writing instructions, hence the need to know
what to call these things.
What would you call "Current Design" in this example?
A link?
That could work, but a link could be anywhere on the page. I could call
it a "Navigation Link", but that sounds awkward.
On Jun 6, 2008, at 3:56 PM, Jason Zietz wrote:
Clearly "Design" is a tab, but "Current Design" and its siblings
don't look like tabs, though they do *behave* like tabs.
A "tab" is a pattern that is quite obviously based on physical tabs
used in books, filing cabinets, etc. For that reason,
Many portal applications call those "pages", for lack of any better
term to describe them. For some reason, many folks have a very
difficult time "seeing" them, so whatever you call them, make them
obvious and provide alternative methods to get to them if people can't
remember they're ther
Apologies if this has been discussed before, but I couldn't find
anything related in the archives. I checked my Designing Interfaces
book as well and came up empty, so now I seek the guidance of the
collective.
http://anxiousplanet.com/ixda/SubmenuOrSubnav.gif
What would you call "Current De
10 matches
Mail list logo
