Re: [Radiant] Anyone else using compass?

2009-05-06 Thread Ken Mayer
After some more playing around, I've got a pretty good workflow for  
using compass. There may be a simpler way to do this, but the start up  
costs are pretty small, so I just go with the flow. This avoids the  
haml version conflicts and gem requirements, because, as Sean  
metioned, the files don't need to be generated at runtime.


Follow the instructions on setting up compass with a rails app (tweak  
your css paths accordingly)

Immediately delete the config/initializer/compass.rb initializer
Immediately delete the vendor/plugins/haml/init.rb file
run compass --watch (which watches & compiles your .sass files, a la  
autotest)

Have fun styling
When you're at a stopping point, ^C auto of compass, commit your  
changes to your repos (public/stylesheets/compiled will be modified),  
push, then deploy. Or, cut and paste the css files back into Radiant.


Aloha a hui hou,
Ken
--
Ken Mayer / kma...@bitwrangler.com / 808-722-6142 / http://www.bitwrangler.com/


On Apr 14, 2009, at 2:46 PM, Sean Cribbs wrote:

I started using it on a Radiant project recently.  Since the files  
don't have to be generated at runtime, you can just generate them  
manually and copy them into public.  I generated the Compass project  
in a plugin in my project and added a Rake task to generate and copy  
the CSS to public/.


Sean

Ken Mayer wrote:
I've been noodling around with compass on a Radiant 0.7.1 tree (so  
I can use blueprint.css, but use SASS for markup). It works,  
mostly, but only with an installed gem. I get production issues if  
I try to use a frozen gem because compass wants HAML 2.1 and  
Radiant has her own copy of 2.0.1 in the vendor/plugins tree.


Is anyone else out there building stylesheets using SASS with  
Blueprint + Compass? I pretty much followed the Rails recipe from  
the compass page.


Aloha a hui hou,
Ken
--
Ken Mayer / kma...@bitwrangler.com / 808-722-6142 / http://www.bitwrangler.com/


___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant



___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant



___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant


Re: [Radiant] Anyone else using compass?

2009-04-14 Thread Sean Cribbs
I started using it on a Radiant project recently.  Since the files don't 
have to be generated at runtime, you can just generate them manually and 
copy them into public.  I generated the Compass project in a plugin in 
my project and added a Rake task to generate and copy the CSS to public/.


Sean

Ken Mayer wrote:
I've been noodling around with compass on a Radiant 0.7.1 tree (so I 
can use blueprint.css, but use SASS for markup). It works, mostly, but 
only with an installed gem. I get production issues if I try to use a 
frozen gem because compass wants HAML 2.1 and Radiant has her own copy 
of 2.0.1 in the vendor/plugins tree.


Is anyone else out there building stylesheets using SASS with 
Blueprint + Compass? I pretty much followed the Rails recipe from the 
compass page.


Aloha a hui hou,
Ken
--
Ken Mayer / kma...@bitwrangler.com / 808-722-6142 / 
http://www.bitwrangler.com/



___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant



___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant