Hi everyone, Thanks for everyone's feedback on the Builder design.
I have started documenting the interactions more thoroughly on the Fluid Wiki, and I have also uploaded some wireframes demonstrating the interaction with the Builder. Wireframe - http://wiki.fluidproject.org/display/fluid/Infusion+Builder+v2.0+Design+and+Wireframes Textual Description of Interactions - http://wiki.fluidproject.org/display/fluid/Infusion+Builder+Rev+2.0+Interactions Please take a look at the above links if you are interested in reading / seeing the behaviour of the new Builder. Changes from previous iteration: - vertical orientation instead of horizontal (easier for keyboard navigation and future modifications / additions). - dependency notification is less alarming - third party modules are now listed in the same container as the selectable Infusion components Additions: - explicit listing of dependent files if a required file is excluded. - keyboard instructions. - space for icons for Infusion components Removed: - Ignore feature Work is also progressing in revising the descriptions and wording for Infusion and 3rd party components on the Builder page. Please take a look at the documentation and images in the wiki links above and share any comments. In particular to Cindy and Harris (who worked on developing the previous Builder), please take a look and let me know if there is anything there I may have missed or should consider. Thanks! - Jonathan. --- Jonathan Hung / [email protected] <[email protected]> IDRC - Interaction Designer / Researcher Tel: (416) 977-6000 x3959 Fax: (416) 977-9844 On Tue, Feb 1, 2011 at 2:03 PM, Jonathan Hung <[email protected]> wrote: > Hi Justin and Anastasia, > > Both of you brought up similar points about the use of the Ignore feature. > After some discussions with both of you, I agree that it is confusing that > Ignore is present for the 3rd party modules, and not for Infusion. Also, > after some thought and discussions with James, it seems that the Ignore > feature would be difficult to implement in a checklist in a way that is > clear and logical for someone using an AT. (It's possible to do, but > requires more metadata and markup than one would expect for this kind of > interaction). > > So for now, the Ignore feature is going to be omitted unless there's a nice > way to implement that makes sense for both sighted and non-sighted users. > > As for categorization of components and wording of text, this isn't final > and definitely requires refinement. I will be sure to approach y'all in the > next few days to do some "card sorting" of components. > > I'm working on another iteration. Hope to have it out very soon. > > Thanks for the feedback! > > --- > Jonathan Hung / [email protected] <[email protected]> > IDRC - Interaction Designer / Researcher > Tel: (416) 977-6000 x3959 > Fax: (416) 977-9844 > > > > On Tue, Feb 1, 2011 at 9:52 AM, Cheetham, Anastasia <[email protected]>wrote: > >> >> Jonathan, I purposely had a look at the new illustration before reading >> your explanation, to get a sense of what a user might experience. Here are >> my first impressions: >> >> - The "ignore" column in the third-party modules is not clear: What does >> it mean to ignore something? It's possible that in a live scenario, where I >> could observe checkboxes turning themselves on and off as I make other >> changes, this might become more clear. >> >> - Why is the "ignore" option only on the third-party modules, and not on >> anything else? >> >> After reading our description/explanation, here are my thoughts: >> >> - I'm still not clear on the different interface for the Infusion Core >> stuff and the third-party stuff: Why does only the third-party stuff have >> the "ignore" option? What happens if I select a component (which will >> automatically select the Framework), then deselect the Framework, then >> select another component? Will Framework come back on? Should I be able to >> "ignore" it? >> >> I guess I'm still not quite clear what the "ignore" function does. Perhaps >> it might be helpful to see a sequence of steps, to show what would turn >> on/off when, and what happens when the user 'ignores' something? >> >> -- >> Anastasia Cheetham Inclusive Design Research Centre >> [email protected] Inclusive Design Institute >> OCAD University >> >> >
_______________________________________________________ fluid-work mailing list - [email protected] To unsubscribe, change settings or access archives, see http://fluidproject.org/mailman/listinfo/fluid-work
