Hello to all!
Adam said:
So, getting back to my question, if after drilling down within Comics
I click on Artwork so I can see something there and then go back to
Comics should I still see my drilled down results.
I find this thing very interesting, though it is not explained that clearly.
Well here is a wrench to throw into the works. I was working on a core
UI architecture for an Oil and Gas application that had three tabs:
Home, Search and Map. Our big debate was should the search results,
which could be a huge spreadsheet view, be reflected on the map or
should the map be
Vlad,
I think you misunderstood the interaction I was trying to describe -
and that's my fault. The comic book/artwork scenario was meant as an
example and a really bad on now that I look at it.
After requesting a bit more time from the business client and
following Jared's advice on getting out
It is still in the wireframe stage so I'm working it out, but I don't think
it needs any instruction because the asterisk (maybe combined with a minor
font change, or an icon instead of an asterisk) appears after a change is
made so it is part of the feedback loop.
Paul
On Jan 25, 2008 12:38
I am designing a tab structure right now that saves the data as you move
between tabs. The purpose is to build a complicated query of a database by
filling out various forms, so there is no process involved on each page.
One thing I did was I marked each tab where a field was changed for a little
I feel like the answer to this should be pretty cut-and-dry, but I can't
help but second guess myself.
I'm working on a web app with a tabbed interface (what else is new).
Under each tab is a workflow that carries the user through a few screens
in order to reach a result.
Consider the
It may be somewhat context specific (i.e., what this is actually used
for), but in the general case you outlined I would retain statefulness.
Regards,
Al
Sent from my iPhone
On Jan 23, 2008, at 12:38 PM, Connor, Adam [EMAIL PROTECTED]
wrote:
I feel like the answer to this should be
It depends. ;)
This is an issue I constantly run into as web apps become more
complex. The same interaction patterns are being used for 2 different
purposes: (1) pure navigation or (2) as a card stack / tabbed dialog /
(whatever you want to call it).
In the end - it really depends on
A more abstract question is this -
Why are essentially two independant wizard like form operations happening
inside of tabs to begin with? Is that the right metaphor to separate out
different categories, types of interactions, workflows
What does the tab metaphor mean in the context of the
On Jan 23, 2008, at 3:38 PM, Connor, Adam wrote:
Consider the following, I have two tabs Tab A and Tab B. Under Tab
A is
Process A and under Tab B is Process B. If a user begins Process A,
and
at any point clicks on Tab B (for any reason) when the user returns to
Tab A, should they be
Hmm, you guys have given me some things to think about. Perhaps tabs
is an inappropriate metaphor to use here due to what it implies. Maybe
simple navigation buttons/links would be better.
To add a bit more detail to the problem I am working on, and because I'm
a geek and fanboy I'll give the
If the user has to progress through a flow to reach the result, then
letting them jump a step or two ahead seems confusing ... but I
don't know the full context. Is it critical the user completes the
interaction on each tab? There's always the simple continue
button, or skip this step. Depends on
12 matches
Mail list logo
