Infusion Builder Rev 2 design - feedback needed

Jonathan Hung jhung at ocad.ca
Fri Jan 21 17:48:19 UTC 2011


Hi everyone,

I have been working on updating the design of the Infusion Builder based on
feedback received on the current builder (visit the current builder site:
http://forge.fluidproject.org/infusionBuilder/html/InfusionBuilder.html).

** The Issue
The predominant issue to be addressed is the matter of Exclusion - the
scenario where a user chooses to remove items from the download package even
though they are required by other selected components.

** Example:
- User selects a few Infusion components which in turn automatically selects
its dependencies.
- The user decides for themselves that they do not need jQuery or jQuery UI
and deselect it from the list.

In this case, how should the UI react? What would a user expect to see in
terms of feedback? Is it better to provide more or less information in this
circumstance?

** Feedback
With this in mind, attached are a series of images illustrating this
scenario. Please review the images and let me know how you feel about the
design addressing this issue of Exclusion.

I'm particularly interested in your thoughts on how Exclusion is being
handled in this design, but welcome thoughts on other aspects of the design
as well.


** Description of Images

   - Builder-rev2-01 - the initial state of the builder after the user loads
   the page.
   - Builder-rev2-02 - user selects Infusion Framework Core.
   - Builder-rev2-03 - user selects a few components: Inline Edit
   - Builder-rev2-04 - user selects a few components: Reorderer and Progress
   - Builder-rev2-05 - user de-selects Infusion Framework Core (may be
   intentional, or may be a mistake), jQuery, and jQuery UI
   - Builder-rev2-06 - Download Minified Package is pressed.


Your feedback is appreciated!

- Jonathan.
---
Jonathan Hung / jhung at ocad.ca <jhung.utoronto at gmail.com>
IDRC - Interaction Designer / Researcher
Tel: (416) 977-6000 x3959
Fax: (416) 977-9844
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://fluidproject.org/pipermail/fluid-work/attachments/20110121/a308f9f4/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Builder-01.png
Type: image/png
Size: 81388 bytes
Desc: not available
URL: <http://fluidproject.org/pipermail/fluid-work/attachments/20110121/a308f9f4/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Builder-02.png
Type: image/png
Size: 85787 bytes
Desc: not available
URL: <http://fluidproject.org/pipermail/fluid-work/attachments/20110121/a308f9f4/attachment-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Builder-03.png
Type: image/png
Size: 85981 bytes
Desc: not available
URL: <http://fluidproject.org/pipermail/fluid-work/attachments/20110121/a308f9f4/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Builder-04.png
Type: image/png
Size: 90246 bytes
Desc: not available
URL: <http://fluidproject.org/pipermail/fluid-work/attachments/20110121/a308f9f4/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Builder-05.png
Type: image/png
Size: 95094 bytes
Desc: not available
URL: <http://fluidproject.org/pipermail/fluid-work/attachments/20110121/a308f9f4/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Builder-06.png
Type: image/png
Size: 91780 bytes
Desc: not available
URL: <http://fluidproject.org/pipermail/fluid-work/attachments/20110121/a308f9f4/attachment-0005.png>


More information about the fluid-work mailing list