[Design] [cosmo] Styleguide updates

Priscilla Chung priscilla at osafoundation.org
Sat May 12 22:35:28 PDT 2007 

Forwarding continued discussion, this is e-mail #3. ;)
-Priscilla

Begin forwarded message:

> From: Mimi Yin <mimi at osafoundation.org>
> Date: May 11, 2007 2:23:17 PM PDT
> To: Priscilla Chung <priscilla at osafoundation.org>
> Subject: Re: Cosmo Styleguide
>
> Hi Priss, do you have time to chat today? I have some thoughts  
> below but maybe we should go over it together?
>
> On May 10, 2007, at 6:42 PM, Priscilla Chung wrote:
>
>>> Here's a new pass with the changes we talked about:
>>> + Rework timezone/subscribe header area
>> Ah, I realize now why I put the subscribe drop down list below the  
>> sign up etc, it was because it made a horizontal line w/ the time  
>> zone drop down list.
>>
>> I realize the reason you mentioned about users wanting to just  
>> move the data out to the desktop—and it's less prominent below the  
>> sign up. I guess it's a bit of, do we want users to sign up for  
>> Hub or if they already have the desktop, then it shouldn't be lost  
>> on them to find this subscribe drop down list. Agreed it's really  
>> a small issue and would not make a big deal about it either way.  
>> Though if I were to make a choice, I think I would flip it back,  
>> but keep the bold +font size 'Sign up!'. That's not an image right?
>
> Hey, let's talk about this more on the phone.
>
> Let's walk through the workflows for when the tz and subscribe  
> pulldowns appear and disappear.
>
> 1. User clicks on ticket-URL to view share in ticket view:
> + User log in links are there.
> + Subscribe pulldown is there.
> + TZ may or may not be there depending on whether collection  
> contains tz data.
>
> 2. User subscribes to share and logs in.
> + User log in links are there.
> + Subscribe pulldown is no longer there.
> + TZ may or may not be there depending on whether collection  
> contains tz data and/or whether user turned on tz support in UI.
>
> Questions to think about:
> Should we optimize for the Logged-in view to look the  
> nicest? ...since that's probably the view that any one person will  
> spend the most time looking at. If we do, I think we don't want the  
> user log-in links to sit above or below the TZ pulldown in the  
> upper-right. It's kind of cramped.
>
> Do we want to try and keep UI elements relatively static, as in not  
> move them around between views?
> + Ticket view
> + Ticket view w/ tz
> + Logged in view
> + Logged in view w/ tz
>
> What about having it all in a line at the top of the screen? See  
> mock-up.
> + Ticket view:
> Subscribe with... | Sign up! | Log in | <TZ Pulldown> | Help
>
> + Logged in view:
> Welcome username | Log out | Settings | <TZ Pulldown> | Help
>
> <TZ Pulldown> is optional.
>
> It will look even better when we can have custom pulldowns.
>
>>> + Get rid of plus icon, replace with Add text underneath
>> Looks great. We'll probably need to make that text in the blue  
>> link. I know Matthew will harp on that one. ;)
>>
>
> Added in mock-up
>
>>> + Streamline NOW/LATER/DONE buttons
>> Excellent!
>>
>>> + Make buttons a middle-grey
>> Looks good. But when the button is in the down state, the gradient  
>> goes from top = dark, bottom = light. I can't tell in the view  
>> selector which one is the selected. Or are you saying in the view  
>> selector, the dashboard is actually in a 'normal' state, so it  
>> looks like it can be pushed?
>
> The Dashboard is selected.
>
>> If you were trying to just whip this up fast, then no big deal— 
>> send it out first and we'll fix the details in the final file. ;)
>>
>>> + Darker outline for RO (Rollover) effect
>> Looks good!
>>
>>> + Flatten out selected sort column header
>> I know we agreed to this, but I'm sorta indifferent to it  
>> currently. Maybe because it's over the triage states?  We'll leave  
>> it as it, it's just looking weird to me.
>
> Yea, I'm not crazy about it either. What about the blue in the mock- 
> up below? We can keep the active state flat.
>
> I'd have to work out RO and MD states for active versus selected  
> though. So there'd be 6 states in all I think.
>
>>
>>> + Rework dialog
>> Looks good! In the style guide, it might be good to indicate  
>> exactly the position from the top left corner to the top left  
>> corner of the dialog—where it's position in the window. That all  
>> dialogs are positioned centered or a few pixels higher on the on  
>> the app., 'cause optically your eye will always make things look  
>> like it's not centered, even when it is.
>
> Sure.
>
>>
>>>
>>> Additionally, I've also tweaked the blue link and selection  
>>> highlight colors so that they're not so they don't compete with  
>>> the red dog as much...
>>
>> Ah, I meant to ask about this but didn't think about it till  
>> recently—the link color you chose, is it ok for color blind ppl? I  
>> realize this is a random issue since the app does not currently  
>> display visited links. You see, Bear had pegged me once, so you  
>> know…it's Bear! ;) In any case, picking a happy medium from a list  
>> here might be useful in case we need to show active vs. visited  
>> etc.: http://www.toledo-bend.com/colorblind/BlueChart.html
>
> Yes it's: #6699ff :D Thx for the link, that's handy to have.
>
>>>
>>> http://wiki.osafoundation.org/Journal/CosmoStyleGuide#LatestMockup
>>>
>>> I've also updated the Sign-up Workflow with the Instructions page.
>>> (I know the buttons and logo are all wrong, but I don't know that  
>>> it's worth fixing it for all the screens.)
>> No need to fix all the screens, but we may want to fix the  
>> activation page I mocked up—if you want the logo on the top left  
>> or centered. The button will be standard w/ the existing button  
>> templates you did.
>>
>> http://wiki.osafoundation.org/Journal/ 
>> SignUpForAnAccountForOtherCalendaringClients#GatewayPage
>
> Oh, I re-styled that page on the Sign-up Workflow page, did you see?
>
>>> http://wiki.osafoundation.org/Journal/CosmoSignUpWorkflow
>> + user types in 'http://hub.chandlerproject.org
>> + probably don't need the 'for one' text, sign up is fine.
>> + #2 sign up dialog which overlaps the login
>> + Last step, user is not taken to log in page, but is logged in  
>> automatically after email verification (I hope, that's what I spec- 
>> ed out). =)
>>
>>> Questions:
>>> + Do we need a Mousedown state?
>> Yes. See file I had sent earlier.
>
> Okay I'm not sure I understand it completely. We can go over it  
> together?
>
>>
>>> + Do we want to do a copy review and make sure we're using  
>>> consistent language across both Hub and Desktop?
>> Yes!!!!!
>
> Okay, can you pull together all the copy that's in the UI? I had  
> started a thread with mde a while ago about error dialogs? Here's  
> the thread: http://lists.osafoundation.org/pipermail/design/2007- 
> January/006152.html
>
> ===
>
> Mock up can viewed on 0.7 spec. updated 5/11/07: http:// 
> wiki.osafoundation.org/Projects/CosmoZeroDotSevenSpec#CurrentMockUp

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osafoundation.org/pipermail/design/attachments/20070512/dc1b9d78/attachment.html

More information about the Design mailing list