Hi James,
I apologize for not responding to your email on time. The main
difficulty I face when trying to answer your question is that I'm not
sure what format of the icons will be the most convenient to work with.
I guess that transparent png will do fine and as to the way of getting
to them I agree with Justin about attaching them to the jiras. The two
issues that I'm working on are:
Code entry:
http://issues.fluidproject.org/browse/ENGAGE-293
My Collection:
http://issues.fluidproject.org/browse/ENGAGE-163
Regards,
Svetoslav
Colin Clark wrote:
James,
I realized no one got back to you concretely about this. I like Justin's idea
of attaching images to JIRA issues associated with each screen or component.
So far, we've been doing pretty well just pulling graphics and icons directly
out of the OmniGraffle wireframes, but not everyone in the community has access
to this (Mac-only) tool. Guest book is a priority, since Antranig is working on
this right now and won't have access to the raw wireframes to pull the graphics
out himself.
We are indeed using transparent PNGs. FSS does indeed handle buttons, so you're
correct that only the graphics inside them are needed. For icons that are
displayed at a fixed size, we'd prefer images that are cropped to exactly the
specified size.
Does this help?
Colin
On 2010-01-28, at 12:41 PM, James William Yoon wrote:
Hullo folks,
We have a bunch of icons and graphic assets. You need them. How do we get them
to you?
Thoughts/questions:
- .png w/ transparency seems like the best way to go
- For buttons, I understand that mFSS provides CSS-based buttons, so it seems
all you need is the actual graphic inside them
- Should we just email them to you? Slip them into the repository (if so, which
one?)?
- Should we ship the icons so that icons of the same type are all exactly the
same size (i.e., include a transparent trim buffer around the icons), or should
we ship them fully trimmed? (i.e., the graphic itself will touch the image
border; the icons of the same type will be roughly the same size, but a few
pixels off from each other)
Cheers,
James
_______________________________________________________
fluid-work mailing list - [email protected]
To unsubscribe, change settings or access archives,
see http://fluidproject.org/mailman/listinfo/fluid-work
---
Colin Clark
Technical Lead, Fluid Project
http://fluidproject.org
_______________________________________________________
fluid-work mailing list - [email protected]
To unsubscribe, change settings or access archives,
see http://fluidproject.org/mailman/listinfo/fluid-work
_______________________________________________________
fluid-work mailing list - [email protected]
To unsubscribe, change settings or access archives,
see http://fluidproject.org/mailman/listinfo/fluid-work