Design walkthrough meeting on Thursday?

Paul Zablosky Paul.Zablosky at ubc.ca
Fri Jun 6 22:19:21 UTC 2008


Erin, Jonathan,
    I really like the dynamic "jump to the middle" design.  This allows 
the viewer to do a sort of manual binary search -- terrifically useful 
if you have a long list, and don't know the distribution of the sorted 
entries. 

I had a need for just this functionality recently. I wanted to look up 
pages in some race results. Out of 44,160 finishers, I wanted to view 
the pages of the persons who finished 969th, 18,472nd, and 41,115th.  
This would have been perfect mechanism for locating the pages.

Paul


erin yu wrote:
> Great idea! It would be lovely to be able to share our doodles. We 
> don't have a scanner at the moment, but we could take pictures. 
>
> I just had a lot of material from the previous pager design, so it was 
> pretty quick to throw some wireframes together. Jon had great ideas, 
> and here are the results of our discussion.
> http://wiki.fluidproject.org/display/fluid/Pager+Design+Iteration
>
> Jon also suggested a mouse-over text like this:
> This helps users predict what would be in that page without having to 
> click on it, and hence reduce clicks to get to a certain item.
>
> The 80:20 guideline came up when we were discussing the second design 
> I posted (link above). This design is very useful for cases with tens 
> or hundreds of pages of data, but not very much so with three pages of 
> data. In the bSpace instance we've looked through, most lists had 1 or 
> 2 pages (80) rather than hundreds of pages (20). 
>
> Erin
>
>
> On 6-Jun-08, at 2:06 PM, Daphne Ogle wrote:
>
>> Just a thought...  How about putting a picture of your rough sketches  
>> on the wiki?  Pretty illustrations are great but are not at all  
>> necessary in early design -- and in fact there are many reasons not to  
>> rush into finished mockups.  I am a huge fan of wireframes whether  
>> they be hand drawn sketches or basic boxes drawn in your favorite wire  
>> framing application.  They help us focus on the interaction rather  
>> than the visual design which sounds like the stage you may be at.
>>
>> As far as the 80/20 question.  Can you say more about this?  Are you  
>> saying it meets use cases that fall into < 20% of pager use?  It would  
>> be great to see what use cases the design meets when you share the  
>> designs.
>>
>> The 80/20 rule is really about deciding what usage to support in the  
>> component.  We don't want the less often needed functions to get in  
>> the way of those that are required more often.  And the bottom line is  
>> that most software tries to do way too much and it becomes  
>> overwhelming to accomplish anything.  What could be the case is the  
>> 20% you refer to are actually common use cases for a certain user  
>> group and so perhaps we would decide to create an additional component  
>> that is focused specifically on that user group.  I'm kind of jumping  
>> ahead here but this is a pretty common situation.
>>
>> Looking forward to seeing the new design options!
>>
>> -Daphne
>>
>>
>> On Jun 5, 2008, at 2:33 PM, Eli Cochran wrote:
>>
>>> You're such a tease... show us!
>>>
>>> Then let us figure out a way to make the 20 work. We're a creative
>>> bunch, I'm sure that we can figure out a way.
>>>
>>> - Eli
>>>
>>> On Jun 5, 2008, at 1:40 PM, Jonathan Hung wrote:
>>>
>>>> I echo Colin's remarks. Today's meeting was really good!
>>>>
>>>> During the discussion I became inspired and doodled two alternatives
>>>> to the pager design... and they're keyboard navigable too. Erin and I
>>>> chatted about it and it seems really cool, but one design falls in  
>>>> the
>>>> 20 of the 80/20 rule.
>>>>
>>>> Aside remark: what if programming for that 20 adds that "delight"
>>>> aspect to a design? Should that 20 be pursued?
>>>>
>>>> I think Erin is going to help make some pretty illustrations of
>>>> them. :)
>>>>
>>>> - Jonathan.
>>>>
>>>> 2008/6/5 Colin Clark <colin.clark at utoronto.ca 
>>>> <mailto:colin.clark at utoronto.ca>>:
>>>>> Hi everyone,
>>>>>
>>>>> On 5-Jun-08, at 11:02 AM, Colin Clark wrote:
>>>>>> Great, thanks for helping with the scheduling.  It looks like both
>>>>>> times work for everyone. Let's go with the 9 am PDT time slot  
>>>>>> unless
>>>>>> you guys would prefer something a bit later in the day.
>>>>>
>>>>> Just a quick note to say how useful I found today's meeting. I
>>>>> learned
>>>>> a lot about the new designs, and I think we're in good shape to  
>>>>> break
>>>>> down the work and start iterating on user stories.
>>>>>
>>>>> For those of you who weren't at the meeting, here are some links to
>>>>> the in-progress designs:
>>>>>
>>>>> Inline Edit:
>>>>> http://wiki.fluidproject.org/display/fluid/Inline+Edit+Design
>>>>> +Overview
>>>>>
>>>>> Pager:
>>>>> http://wiki.fluidproject.org/display/fluid/Smart+Page+Navigation+(aka+Pager 
>>>>> <http://wiki.fluidproject.org/display/fluid/Smart+Page+Navigation+%28aka+Pager>)
>>>>>
>>>>> Uploader revisions:
>>>>> http://wiki.fluidproject.org/display/fluid/Uploader+Design+Iteration
>>>>>
>>>>> Daphne and Jess are working on getting the component design pages
>>>>> into
>>>>> a more common format along the lines of the Inline Edit Design
>>>>> Overview page, which will be great.
>>>>>
>>>>> Colin
>>>>>
>>>>> ---
>>>>> Colin Clark
>>>>> Technical Lead, Fluid Project
>>>>> Adaptive Technology Resource Centre, University of Toronto
>>>>> http://fluidproject.org
>>>>>
>>>>> _______________________________________________
>>>>> fluid-work mailing list
>>>>> fluid-work at fluidproject.org <mailto:fluid-work at fluidproject.org>
>>>>> http://fluidproject.org/mailman/listinfo/fluid-work
>>>>>
>>>>
>>>>
>>>>
>>>> -- 
>>>> Jonathan Hung / jonathan.hung at utoronto.ca 
>>>> <mailto:jonathan.hung at utoronto.ca>
>>>> University of Toronto - ATRC
>>>> Tel: (416) 946-8312
>>>> _______________________________________________
>>>> fluid-work mailing list
>>>> fluid-work at fluidproject.org <mailto:fluid-work at fluidproject.org>
>>>> http://fluidproject.org/mailman/listinfo/fluid-work
>>>
>>> . . . . . . . . . . .  .  .   .    .      .         .              . 
>>>                     .
>>>
>>> Eli Cochran
>>> user interaction developer
>>> ETS, UC Berkeley
>>>
>>>
>>> _______________________________________________
>>> fluid-work mailing list
>>> fluid-work at fluidproject.org <mailto:fluid-work at fluidproject.org>
>>> http://fluidproject.org/mailman/listinfo/fluid-work
>>
>> Daphne Ogle
>> Senior Interaction Designer
>> University of California, Berkeley
>> Educational Technology Services
>> daphne at media.berkeley.edu <mailto:daphne at media.berkeley.edu>
>> cell (510)847-0308
>>
>>
>>
>> _______________________________________________
>> fluid-work mailing list
>> fluid-work at fluidproject.org <mailto:fluid-work at fluidproject.org>
>> http://fluidproject.org/mailman/listinfo/fluid-work
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> fluid-work mailing list
> fluid-work at fluidproject.org
> http://fluidproject.org/mailman/listinfo/fluid-work
>   

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://fluidproject.org/pipermail/fluid-work/attachments/20080606/80404c13/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 4172 bytes
Desc: not available
URL: <http://fluidproject.org/pipermail/fluid-work/attachments/20080606/80404c13/attachment.png>


More information about the fluid-work mailing list