rubyonrailsin

A Ruby and Rails talk

Tuesday, March 30, 2010


Re: [Radiant-Dev] Compass in Core?

by rubyonrailsin 0 comments

Tag


Share this post:
Design Float
StumbleUpon
Reddit

On Tue, Mar 30, 2010 at 10:43 AM, John Long <johnwlong2000@gmail.com> wrote:
> I've included some of the modules form compass, but I am a little
> picky on the kinds of things that I want included. I prefer that we
> work out something custom for Radiant.

while we're on the topic of core sass/css. can i ask why the modules
prefer proprietary declarations over standard ones? for example from
the opacity module(same goes for rounded and shadow and maybe more...i
got tired of looking):

=opacity(!opacity)
opacity= !opacity
-moz-opacity= !opacity
-khtml-opacity= !opacity
-webkit-opacity= !opacity
filter= "alpha(opacity=" + round(!opacity*100) + ")"
-ms-filter= "progid:DXImageTransform.Microsoft.Alpha(Opacity=" +
round(!opacity*100) + ")"

shouldn't `opacity= !opacity` be the last line there? it seems to me
it would be preferable for browsers that support the standard
declaration to use it.

> --
> John Long
> http://wiseheartdesign.com
> http://recursivecreative.com
>
> On Tue, Mar 30, 2010 at 10:55 AM, [Square Talent] Dirk Kelly
> <dirk.kelly@squaretalent.com> wrote:
>> I pretty much use compass for clearfix, 960, stickyfooter and (in edge)
>> rounded corners.
>> Like Will said, it just means less code repetition. Could be just as useful
>> to have them in modules (which I see is what John has done in his prototype)
>> DK
>>
>> On Tue, Mar 30, 2010 at 10:40 PM, William Ross <will@spanner.org> wrote:
>>>
>>> On 29 Mar 2010, at 11:17, Mislav Marohnić wrote:
>>>
>>> > First of all, we should ask ourselves what does "Compass in core" mean
>>> > for Radiant? It means that the admin interface is done using it. So until
>>> > someone actually steps up and has a strong argument for using Compass for
>>> > the admin UI (and actually does the work), I don't think Radiant will ship
>>> > with Compass.
>>>
>>>
>>> I don't see a need for all of compass in core, so I'd vote no too, but it
>>> would be useful to offer a standard grid for more complex forms. I've been
>>> experimenting with a sassified version of the 960 grid system in
>>> sass/admin/_modules. It's quite compact, and being programmatic it has the
>>> great advantage of working with whatever widths and margins you specify,
>>> including percentages as well as pixel values.
>>>
>>> You can make a full-width 12-column grid very easily like this:
>>>
>>>        http://gist.github.com/349148
>>>
>>> It's a nice example of the sort of thing sass does well. The css original
>>> is over 600 lines, and in the event calendar (which I'm just now converting
>>> to 0.9) it means that most of the layout is as simple as this:
>>>
>>>      @import modules/_grid.sass
>>>      p.title
>>>        +grid(8)
>>>      p.keywords
>>>        +grid(4)
>>>      p.description
>>>        +grid(12)
>>>
>>> I haven't done many browser tests yet but it does seem worthwhile. Anyone?
>>>
>>> will
>>>
>>>
>>>
>>> --
>>> Radiant CMS Dev Mailing List
>>> Post:        radiantcms-dev@googlegroups.com
>>> Unsubscribe: radiantcms-dev-unsubscribe@googlegroups.com
>>> Group Site:  http://groups.google.com/group/radiantcms-dev/
>>>
>>> To unsubscribe from this group, send email to
>>> radiantcms-dev+unsubscribegooglegroups.com or reply to this email with the
>>> words "REMOVE ME" as the subject.
>>
>> --
>> Radiant CMS Dev Mailing List
>> Post: radiantcms-dev@googlegroups.com
>> Unsubscribe: radiantcms-dev-unsubscribe@googlegroups.com
>> Group Site: http://groups.google.com/group/radiantcms-dev/
>>
>> To unsubscribe from this group, send email to
>> radiantcms-dev+unsubscribegooglegroups.com or reply to this email with the
>> words "REMOVE ME" as the subject.
>>
>
> --
> Radiant CMS Dev Mailing List
> Post:        radiantcms-dev@googlegroups.com
> Unsubscribe: radiantcms-dev-unsubscribe@googlegroups.com
> Group Site:  http://groups.google.com/group/radiantcms-dev/
>
> To unsubscribe from this group, send email to radiantcms-dev+unsubscribegooglegroups.com or reply to this email with the words "REMOVE ME" as the subject.
>

--
Radiant CMS Dev Mailing List
Post: radiantcms-dev@googlegroups.com
Unsubscribe: radiantcms-dev-unsubscribe@googlegroups.com
Group Site: http://groups.google.com/group/radiantcms-dev/

No comments:

Post a Comment

Subscribe feeds via e-mail

Blog Archive