Hey Pauric, Love the filename ;)
It's an interesting idea, though it does seem like it could get confusing. As you say, maybe with some more refinement it could go somewhere. I'm leaning towards my description of option (a) at the moment. I've sketched it out here: http://www.usabilitymatters.com/work/nested_progress_bars.gif I'm thinking that after Task B is finished and those details no longer matter, we might be able to do away with those steps on the progress bar entirely. Then again, if they choose to step backwards in the process to change some information they've edited, it *could* get confusing. That would lead more to a design like this: http://www.usabilitymatters.com/work/nested_progress_bars_keep_steps.gif I keep thinking there MUST be examples out there of other people who have done this. I have managed to actively avoid this situation up to this point, but there are some situations where you just can't get around it. Meredith > Suggestion: Create a split progress bar once the user jumps from one > task to another. > > User some form of colour coding (green = a, blue =b) to allow the > user to connect each bar with its corresponding task. > > This is a little half-baked and would need a lot of testing... > http://web.mac.com/pauric_ocallaghan/progresseses.jpg ________________________________________________________________ *Come to IxDA Interaction08 | Savannah* February 8-10, 2008 in Savannah, GA, USA Register today: http://interaction08.ixda.org/ ________________________________________________________________ Welcome to the Interaction Design Association (IxDA)! To post to this list ....... [EMAIL PROTECTED] Unsubscribe ................ http://www.ixda.org/unsubscribe List Guidelines ............ http://www.ixda.org/guidelines List Help .................. http://www.ixda.org/help
