Kicking the tires on the UX toolkit

[Clay Fenlason]

Let's talk about what that means, certainly.  I can say that the
opportunity is there, but with the caveat that the nearer term is
focussed on RSF conversion, test coverage for reliability and
performance, and gradebook integration via "helpers" - the first
deliverables are in fact going to be "reduced" versions of the
existing tool.  New directions are going to be postponed, but they'll
be back on the table somewhere in the second quarter, I'd expect.  We
are however in the process of trying to distill what's essential in
this problem space, and it would be a valuable time to work through
the kinds of questions you probably want to raise, Sean.

~Clay

2007/12/4, Sean Keesler <smkeesle at syr.edu>:
> Guys...this is a HUGE opportunity to make Assignments "Goal Aware" in a very
> "Fluid" way. What are the prospects of "baking that in" to the design of the
> new tool?
>
>
> ------------------------------
> Sean Keesler
> Project Manager
> The Living SchoolBook
> 030 Huntington Hall
> Syracuse University
> 315-443-4768
>
>
>
>
> On 12/4/07 10:31 AM, "Mara Hancock" <mara at media.berkeley.edu> wrote:
>
> > Clay -- Do you have a designer on the project or do we need to talk
> > about finding UI support?
> >
> >
> > On Dec 4, 2007, at 9:10 AM, Clay Fenlason wrote:
> >
> >> An inter-institutional team is coming together to rewrite the
> >> Assignments tool in Sakai, a team without any allocated design
> >> resource, and so I've been actively reviewing the UX toolkit from the
> >> perspective of those needs.
> >>
> >> There are design patterns and components we might wish were already in
> >> a Fluid release, of course, but that's not the point I'm trying to
> >> make.  It seems very likely that our Assignments work presents an
> >> opportunity to create reusable chunks of UI, and it would really be
> >> best for everyone if we tried to create them as Fluid components (as
> >> opposed to merely trying to develop the UI portions in such a
> >> commonsensical way that someone might review and adapt them).
> >>
> >> So what we're missing is documentation on how to develop a Fluid
> >> component.  I think we'd like to contribute, fulfilling the ideal of
> >> meeting local needs in a communally beneficent way, but we need to
> >> better understand the standards, packaging, or what have you, which
> >> would allow Fluid to accept and incorporate our contribution.
> >>
> >> ~Clay
> >> _______________________________________________
> >> fluid-work mailing list
> >> fluid-work at fluidproject.org
> >> http://fluidproject.org/mailman/listinfo/fluid-work
> >
> > ======================================================
> > Mara Hancock
> > ETS Associate Director of Learning Systems
> >
> > http://ets.berkeley.edu
> > University of California, Berkeley
> > Educational Technology Services
> > 9 Dwinelle Hall, #2535
> > Berkeley, CA 94720
> >
> > Desk: 510-643-9923
> > Mobile: 510-407-0543
> >
> >
> > _______________________________________________
> > fluid-work mailing list
> > fluid-work at fluidproject.org
> > http://fluidproject.org/mailman/listinfo/fluid-work
>
>


-- 
Clay Fenlason
Director, Educational Technology
Georgia Institute of Technology
(404) 385-6644