UI Options fix ups

[James William Yoon]

Hi all,

James and I have also been doing quite a bit of chatting on the design of UI
> Options itself... variations on how to present the customization controls in
> a way that's intuitive, not too overwhelming, easily available, and makes
> everyone happy - no small feat!
>

It's been exciting to think about the directions we could take UI Options.
Heidi and I have been looking at the earlier work, and have been thinking
about ways to push the design forward.

We liked the degree of customization available in the current designs (
http://wiki.fluidproject.org/display/fluid/User+Interface+Options+Wireframes),
but felt that it introduced too much granular control too soon, effectively
overwhelming the user with options. An earlier iteration of the designs (
http://wiki.fluidproject.org/display/fluid/User+Interface+Options+Wireframes+-+Iteration+1)
took the step of offering a handful of preset options.

Right now, we're thinking of taking a combination of these ideas into a
two-tiered approach: offer the user a good, narrow range of presets, and
then easily allow further customization. Iteration 1 of the designs did
something like this, and we hope to take some of the advances from later
iterations to improve upon it.

James


On Fri, Sep 17, 2010 at 3:36 PM, Valles, Heidi <hvalles at ocad.ca> wrote:
> hi folks,
>
> Michelle and I looked over the current implementation of UI Options and
made a list of things to fix up, as well as a small to-do list for getting
UI Options up on the inclusivedesign.ca website (dev.inclusivedesign.ca to
start).
>
> I've made JIRAs for the work I'll be doing:
>
> FLUID-3742 - table of contents fix so one doesn't have define in init
script (set default)
> FLUID-3743 - add preview url as an option, right now hard-coded
> FLUID-3745 - improve/update documentation
> FLUID-3733  w/ sub tasks - add UI Options to IDI site
> FLUID-3738 - noteable subtask about creating a Drupal module to install
infusion properly within the CMS
> FLUID-2616 - UI Options should load its own template
>
> James and I have also been doing quite a bit of chatting on the design of
UI Options itself... variations on how to present the customization controls
in a way that's intuitive, not too overwhelming, easily available, and makes
everyone happy - no small feat!
>
> The BBC accessibility case studies are a good read FYI:
http://www.bbc.co.uk/accessibility/bbc/case.shtml
>
> cheers,
> heidi
>
>
> ---
> Heidi Valles
> Accessible Software Developer
> Inclusive Design Research Centre, OCAD University
>
>
>
>
>
>
> _______________________________________________________
> fluid-work mailing list - fluid-work at fluidproject.org
> To unsubscribe, change settings or access archives,
> see http://fluidproject.org/mailman/listinfo/fluid-work
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.idrc.ocad.ca/pipermail/fluid-work/attachments/20100920/ab6d716c/attachment.htm>