Springboards: design as well as code?

[Eli Cochran]

Jacob hit it perfectly.

The current visual design is, well, uninspiring and flat. But once we  
have some working examples we can work on that.

One of the things that we're doing right now is identifying the common  
elements and states that we need to support in our skinning. This will  
allow us to approach the visual design holistically. We don't expect  
to capture everything, but we will have a sense of how the different  
parts of the theme will work together.

Jacob and I have been brainstorming elements and states, both  
conceptually and how they are represented in html and css, and in our  
components.

Please take a look at the lists that we're pulling together here: http://wiki.fluidproject.org/display/fluid/Springboards#Springboards-elementsandstates

The component area is still quite thin.

Thanks,
Eli

On Aug 21, 2008, at 6:55 AM, Jacob Farber wrote:

> I believe the work is to be done in phases;
> Phase 1 is to have simple, working implementations with little as  
> little
> frills as possible
> Phase 2 is to have a theme running consistently as an option to take
> with the components
> Phase 3 is to have multiple themes with purposes (various high  
> contrast
> themes, high-bandwidth/low-bandwidth, etc)
>
> However all phases should compliment the design patterns already
> established, and showcase the "interesting moments" I think. Those
> "interesting moments" may need a little polish when phase 1 is done,  
> as
> we're running into situations where things dont quite gel when the
> components are super-simplified. Passive discoverability, which  
> affects
> all phases, should probably be the first to get another pass in my  
> opinion.
>
> Eli, please correct me if I left anything out or got it backwards....
> Jacob
>
> Anastasia Cheetham wrote:
>> All:
>>
>> I've finally taken a closer look at the Springboards that Jacob and
>> Eli are working on - nice work! I have a question about the purpose  
>> of
>> the Springboards.
>>
>> I understand that they are intended to serve as exemplars of the
>> simplest code necessary to implement a component.
>>
>> Is there also an intention for them to serve as exemplars of our own
>> design patterns? Will they be styled, etc. to illustrate the
>> interesting moments defined by the patterns, for example?
>>
>>
> _______________________________________________
> fluid-work mailing list
> fluid-work at fluidproject.org
> http://fluidproject.org/mailman/listinfo/fluid-work

. . . . . . . . . . .  .  .   .    .      .         .              .                     .

Eli Cochran
user interaction developer
ETS, UC Berkeley