Hampton, I think this is a great development. Sass is a game changing technology and it certainly needs its own identity and the ability to install it stand-alone. I am curious how development will proceed going forward. Is Nathan still the only maintainer or are you going to be taking a more active development role?
I'd like to couple your announcement with an announcement of my own. Introducing Compass: The Sass Stylesheet Meta-Framework. http://github.com/chriseppstein/compass/wikis Compass grew out of my work to make a blueprint port to sass, but has since grown to include a partial port of YUI and will include other frameworks as the community involvement grows. The main goal of Compass is to provide a comprehensive library of Sass mixins to make building semantic webpages a snap. The other aspect of Compass will be an ability to build and share UI scaffolds and designs so that we can share page layouts as easily as we share code plugins (easier I hope). Part of compass is a command line tool that generates projects and will regenerate the entire project's sass files into CSS without needing any app server because not everyone is lucky enough to have Ruby in their production environment. Perhaps this command line tool (or portions of it) should be part of Sass instead? I look forward to having this and other such conversations over on the Sass Mailing list... Chris On Sep 27, 10:00 am, 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 -~----------~----~----~----~------~----~------~--~---
