Layout reorderer demo design update

James William Yoon jyoon at ocad.ca
Wed Oct 6 14:39:18 UTC 2010


Comments inline:

On Tue, Oct 5, 2010 at 2:00 PM, Jonathan Hung <jhung at ocad.ca> wrote:

> I guess it really depends on the content.


Yep, definitely! We don't want to overwhelm the user with flashy,
distracting content.


> As long as it is content that not interactive, then I think it will be
> okay. Otherwise users may be confused as to what is being shown to them (as
> with the uPortal demo) or file bugs against components / UI elements that
> isn't part of the primary demonstration.
>

I think there's probably a balance to be struck here.

You make a great point that we don't want users to be confused by other
components or interactions when we're really trying to demo the reorderer. I
think sticking with simple, conventional interactions (links, text fields,
buttons, etc.) in conjunction with the more novel reordering interaction
would sidestep that.

It's also worth remembering that the user is at the demo to see the use and
integration of the layout reorderer--they're already heavily primed and
biased toward looking for that. It's not as though we're throwing out a
random site to them and testing them to see what they think we're demoing,
;)

I think it's okay to abstract a little for these demos. If they want to see
> it functioning in a more complex case, we can put a link to the uPortal
> example?
>

Links to the full integration demos sounds like a great idea! But I still
think it's worthwhile to be consistent across our component demos wrt to
their complexity (i.e., let's design all our demos so that they introduce a
reasonable amount of context, instead of having some that do and others that
don't)

James
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://fluidproject.org/pipermail/fluid-work/attachments/20101006/288eda09/attachment.html>


More information about the fluid-work mailing list