1. I guess it depends how granular should it be. Quarter, half, single and
double seemed to cover basics, but if you think quarter step increments is
worth the file size, I can update.
2. Oops!
3. - Can you help me understand the first point here? How would the BP
gutter affect the spacing classes.
Agree with the file size consideration. This goes back to the first point
somewhat.
- Multiple files: I think having multiple files for generic padding/margin
goes against the idea of have a set of spacing tools on the ready. If you
need to think about adding space-large-to-megalarge.css to your doc just to
get .margin-left-large class, you might as well just write the style.

- Meaningful names worth increased file size: IMO no, if you are using them
often, you will become familiar with naming conventions.

Of course what I do for my own projects doesn't mean it's a good fit for
BP!

I can revise:
- For names how about 'padding-all-0', 'padding-all-1-4' (quarter),
'padding-all-1-2' (half). Or 'padding-all-1of4'?
- What about quarter, half, single and double in the plugin core, and 1/4
step increments as a plugin to the plugin?


Kevin


On Wed, Dec 15, 2010 at 1:21 PM, kaiser <[email protected]> wrote:

> @Kevin: And please always name your core plugin files screen.css. They
> will be put in some directory named /plugins/whatever/screen.css. On
> the other hand, please take a look at the other plugins and try to
> find class names that fit the current scheme. It's pretty semantic and
> uses "-" slashes, which makes reading the source code easier and the
> class names more semantic/context oriented. Thanks.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Blueprint CSS" group.
> To post to this group, send email to [email protected].
> To unsubscribe from this group, send email to
> [email protected]<blueprintcss%[email protected]>
> .
> For more options, visit this group at
> http://groups.google.com/group/blueprintcss?hl=en.
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Blueprint CSS" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/blueprintcss?hl=en.

Reply via email to