Fools rushing in
daphne at media.berkeley.edu
Wed Apr 30 17:17:00 UTC 2008
This all sounds great Clay!
Is there someplace we can see the current design thinking for
As you know, we will be using in-line editing in the Image Gallery and
have done quite a bit of research and thinking about it so let's stay
in touch as you move forward. Any idea when you'll be working on
it? From a component perspective it would be really valuable to think
through the editing interactions in both contexts and what that means
to the component, implementation and design pattern(s). Here's what
Jennifer Tidwell has to say about "Edit-in-place" in Designing
Interfaces (my favorite design pattern resource), http://designinginterfaces.com/Edit-in-Place
We'd (Fluid UX folks) be happy to help with design and testing so let
us know what makes sense. We do our 2-week iteration planning on
Tuesday's. The next iteration will start on May 13th so let me know
if there's anything we can work into the plan.
On Apr 30, 2008, at 3:33 AM, Clay Fenlason wrote:
> We at Georgia Tech have felt compelled to pursue some significant
> redesign work under the umbrella of the assignment2 project. The
> basic issues and concepts remain those that were sketched out on the
> Fluid wiki several months back (see
> http://wiki.fluidproject.org/x/KhQa), and we have a fledgling design
> or two built around that problem space, but we feel also the need for
> an extended period of usability testing and refinement of the design
> across a number of iterations.
> What allows this temerity is the sdata-JSON-client-side approach
> pioneered in the My Sakai efforts at CARET, combined with the fact
> that the UI views concerned are mostly a matter of focused
> arrangements of tabular data.
> Carl has written extra handlers for producing JSON feeds for
> assignment data, and now the stage is fairly well set. We're pressing
> cross-browser issues, among other things), while we plan to enter
> usability testing in the middle of May, for which we've recruited a
> dozen or so interested faculty and students. Our lack of design
> resource is compounded by an ignorance of JS accessibility snares, but
> it's the hope that between keeping things fairly simple and our
> ability to iterate more rapidly that we won't paint ourselves into any
> inaccessible corners that we can't work our way out of.
> We also feel that a tactic of attempting to identify and produce Fluid
> components as we go is a natural way to educate ourselves, to achieve
> some reusability (and hence consistency) in our output, and to allow
> the Fluid team to find it worth their time to help us. An early
> component identified is the in-line editor, since this was already
> somewhere on Fluid's radar. It sounds like Colin's already laid some
> of the groundwork for us.
> When we enter the usability testing phase we'll plan also to have a
> public testing server, so that we can also take into account feedback
> from others in the Sakai community.
> Suggestions and questions most welcome.
> This automatic notification message was sent by Sakai Collab (https://collab.sakaiproject.org/portal
> ) from the DG: User Experience site.
> You can modify how you receive notifications at My Workspace >
Senior Interaction Designer
University of California, Berkeley
Educational Technology Services
daphne at media.berkeley.edu
More information about the fluid-work