http://github.com/chriseppstein/compass is a sass framework that includes a command line interface for working without a ruby app server. The Sass command line can only process one file at a time.
chris On Oct 4, 12:39 am, Nathan Weizenbaum <[EMAIL PROTECTED]> wrote: > That's what the shoes app is for - the idea is to create an application > that's easy to distribute and use without requiring designers to touch > Rubygems or Ruby. If you're interested in appealing to that group of > people, I think that's where you should focus your effort. > > Eric wrote: > > Good point! I mentioned the PHP/.htaccess combo specifically because > > of its ease of use by the less technical. I'm thinking particularly of > > the barely-able-to-deploy-Wordpress designers out there. I'd love to > > get Sass into their hands. Guess I should write some code... > > > Is there an official grammar written up somewhere for Sass? > > > On Oct 4, 2:09 am, Nathan Weizenbaum <[EMAIL PROTECTED]> wrote: > > >> I don't see the necessity for porting Sass to other languages. Unlike > >> Haml, it's not tightly integrated with Ruby, so the full effect can be > >> run using the command-line script. It should be reasonably easy to setup > >> a Sass module for Apache, although for efficiency it would probably be a > >> better idea to hand-compile it. > > >> Eric wrote: > > >>> Oh happy day! This gives me the perfect reason to learn Shoes. > > >>> I must admit I'm a little late to the game, so I'll throw this one out > >>> there: Has anyone talked about bundling a PHP port of Sass with > >>> a .htaccess (for url rewriting) so that we can deploy Sass files > >>> directly to a webserver? The .htaccess would route the calls for .css > >>> files to the php script, which would then turn the Sass into CSS -- > >>> with caching of course. > > >>> In that same vein, has anyone written a version of Sass in a language > >>> other than Ruby? I've seen other similar projects (like Python's > >>> CleverCSS), but I believe their syntax is slightly different from > >>> Sass. > > >>> Cheers! > > >>> On Sep 27, 1:00 pm, Hampton <[EMAIL PROTECTED]> wrote: > > >>>> I'd like to start by thanking everyone here in the Haml community for the > >>>> help with Sass. When I came up withSass it was obviously the right thing > >>>> to > >>>> do to bundle it with Haml, because of the great community we have here > >>>> and it allowed us to share innovations between the two languages. You > >>>> guys > >>>> have done an *amazing* job > >>>> of taking Sass from a small improvement over CSS to an entire styling > >>>> language itself. > > >>>> I am humbled and amazed at the great ideas and work that have come from > >>>> all > >>>> of you. And, when reading > >>>> the recent posts and conversations about Sass, I realized that it was > >>>> time > >>>> to implement Phase 2 of Sass. > > >>>> Ever since I first had the idea, I knew that it would be a fantastic > >>>> language *outside* of the Ruby/Rails/Merb > >>>> communities. There are thousands of CSS developers out there still > >>>> dealing > >>>> with a really simple language > >>>> in CSS and could really use some of the tools we have developed here with > >>>> Sass. > > >>>> Moving into the future, Sass is becoming more of its own project. Its not > >>>> going to be ripped out of Haml > >>>> completely until Haml 3.0 or so (just to make it easy with your Haml > >>>> projects), but the two languages are > >>>> parting ways fundamentally at this point. > > >>>> Obviously, we wouldn't get much done if we just kept Sass as a regular > >>>> gem > >>>> and required all of the Ruby-fu > >>>> to use it... so, I have created a GUI for Sass in Shoes. Which means > >>>> that we > >>>> can release desktop applications > >>>> for OS X, Linux, and Windows that include the Ruby interpreter and a nice > >>>> interface for updating and working > >>>> with Sass. > > >>>> The basic idea is that a CSS developer would launch the Sass app... then > >>>> point it at a Sass file on their system > >>>> and the application would bond to that Sass file (or soon, directory of > >>>> them) and start pumping out CSS files > >>>> whenever a Sass file is modified. Its what Sass does with > >>>> Rails/Merb automatically without needing to use > >>>> those frameworks. > > >>>> I have a prototype working that is ugly and I need your help to make it > >>>> *awesome*. With open source > >>>> development... you can't do it alone. > > >>>>http://github.com/hcatlin/sass/tree/master > > >>>> Viola! Its a really, really, really basic app right now. > > >>>> Branch and modify as you will! I think this is going to be a huge hit and > >>>> once its ready for the wild > >>>> I'm going to go attend every CSS conference I can find to pimp this baby. > > >>>> Finally, there is a new google group for Sass. > > >>>>http://groups.google.com/group/sass-lang > > >>>> Alright guys, you behind me on all of us ganging up on the shitty world > >>>> of > >>>> CSS development and making > >>>> it rock? > > >>>> -hampton. > > >>>> PS: Check out the new Logo for Sass... ! I'm still tracking down the > >>>> original font for the Haml logo... that will be changed to match exactly. > > >>>> logo.gif > >>>> 46KViewDownload > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Haml" 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/haml?hl=en -~----------~----~----~----~------~----~------~--~---
