Re: Garden, Thorn - Looking for contributors
So there's 2 points that I raised. The main one is getting the *@import*working. And I probably just need to see an example of how to do that in the API. With that, I'd probably move over to hiccup / garden. Wrt garden-watch https://github.com/twashing/garden-watch, I understand and agree with your rationale. However, I can think of at least 2 considerations where a user of the tool may not want to enter the repl. 1. A user in some other language wants a simple tool from which they can generate HTML or CSS. For example, when I use guard and it's plugins (see here https://github.com/guard/guard-haml and herehttps://github.com/hawx/guard-sass), it doesn't force my project to use Ruby. And we shouldn't make that imposition on others. 2. If I have a designer building out solely my HTML / CSS, I'd like her to just edit edn, and have corresponding code generated. No need for her to dive into a repl unnecessarily. But again, for my immediate needs, point 2 is secondary. I just need @import and those other edge cases working. I still think inlining raw CSS is a good idea, for just seeing which use cases garden misses. Hth Tim Washington Interruptsoftware.com http://interruptsoftware.com On Thu, Mar 27, 2014 at 10:33 AM, Joel Holdbrooks cjholdbro...@gmail.comwrote: I've answered this question numerous times and am convinced I need to write a blog post so I can just drop a link. In general the biggest win is that you can use Clojure and all of the facilities therein to write more sophisticated stylesheets. Large CSS codebases are notoriously hard to manage and require a lot of discipline to get right. If you're not writing a lot of CSS it isn't necessarily a big win. On Tuesday, March 25, 2014 5:42:45 PM UTC-7, Daniel wrote: I wonder what is so bad about pure CSS. Don't get me wrong - I do appreciate projects like these. -- You received this message because you are subscribed to the Google Groups Clojure group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups Clojure group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Garden, Thorn - Looking for contributors
I've answered this question numerous times and am convinced I need to write a blog post so I can just drop a link. In general the biggest win is that you can use Clojure and all of the facilities therein to write more sophisticated stylesheets. Large CSS codebases are notoriously hard to manage and require a lot of discipline to get right. If you're not writing a lot of CSS it isn't necessarily a big win. On Tuesday, March 25, 2014 5:42:45 PM UTC-7, Daniel wrote: I wonder what is so bad about pure CSS. Don't get me wrong - I do appreciate projects like these. -- You received this message because you are subscribed to the Google Groups Clojure group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups Clojure group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Garden, Thorn - Looking for contributors
Thanks! I'll be in touch. On Tuesday, March 25, 2014 1:54:23 PM UTC-7, Alan Moore wrote: Joel, Count me in... You can contact me offline at kahunamoore a/t coopsource d/o\t org Thanks for this library! Alan On Tuesday, March 25, 2014 12:33:15 PM UTC-7, Julien wrote: Hi Joel, thanks for your great work on garden! Definitively helping me every day. Can you share what you have in mind regarding CSSOM integration? It certainly opens cool perspective and I'm curious how you see it fit with garden. I would be interested in giving you a hand here. Maybe a github issue would help start discussions? Julien Le samedi 22 mars 2014 22:41:04 UTC-3, Joel Holdbrooks a écrit : Greetings everyone, About a year ago I began working on Garden and in the short time the library has been around it's grown a bit. Although many folks seem to be interested in it, there's certainly not as much adoption of the library as I'd like to see. Sass, Less, and (god help us) pure CSS still appear to be the default choices for many people writing web applications in Clojure. This is something I'd like to change... but I need *your* help! No, no. Put down the phone. Don't look for a KickStarter URL. It's nothing like that. How you can help Garden I'm looking for individuals who are interested in the following: - improving the compiler code - improving/extending existing API's - building an interface to the CSSOM I'm also open to good 'ol fashioned suggestions, pain points you've experienced using the library, or flat out letting me know what it would take to get you to choose Garden over the alternatives for your next project. How you can help Thorn Thorn is very young project and has no official release yet. So what is it? At the moment it's the beginnings of a Sass Parse Tree transformer; something that will take CSS/SCSS/Sass code and give you Garden code. There's a lot of fabulous libraries available in Sass and I'm sure it's a big factor when choosing how to go about CSS generation. I'm looking for individuals who are interested in the following: - accurately transforming CSS/SCSS/Sass to real Clojure code targeting Garden - accurately transforming Less to real Clojure code targeting Garden Why? I deeply believe that being able to author CSS in Clojure or ClojureScript is a key piece to having an extremely compelling story for web application development in Clojure. Being able to *program* CSS and not just *preprocess* is a big advantage over existing tools. Being able to use all of Clojure everywhere has astounding possibilities. If any of this sounds interesting to you please get in contact with me or reply here. I will also be in San Francisco tomorrow until Tuesday for Clojure/West if you'd like to discuss these items in person. Truly, Joel -- You received this message because you are subscribed to the Google Groups Clojure group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups Clojure group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Garden, Thorn - Looking for contributors
Hi Joel, I think this is a good idea. We've discussed one of my pain points; particularly *Exploring Garden At Rules*. Our thread basically looked like the below (last few messages ellided). Now, for the moment, I indeed went back to *SCSS*, because *i)* it did what I wanted out of the box and *ii)* I took a look at garden code and it wasn't clear to me how *cssfn*and *defcssfn* solved my *@import* problem. So I'd imagine there are a few more of those kinds of edge cases with which I'd need to wrestle. And it's sort of on me, to fix and contribute, like you said. But at the moment, I'm just strapped for time, and needed something that worked. Also, I've neglected garden-watchhttps://github.com/twashing/garden-watch, which is another use case that I needed filled. Ie, I have an external designer. And I'd just like him to work with *edn*, and have *CSS* be spit out. So that's my 2 cents. And if I were to have those things working now, I'd ditch *HAML* and *SCSS*. *1. * Hi Joel, I'm playing around with garden a little, and wanted to ask you a question about the at rules. If I execute the below command, I get the result output. *(css (at-import url(http://fonts.googleapis.com/css?family=Gentium+Book+Basic:700italic http://fonts.googleapis.com/css?family=Gentium+Book+Basic:700italic)))* *= @import \url(http://fonts.googleapis.com/css?family=Gentium+Book+Basic:700italic http://fonts.googleapis.com/css?family=Gentium+Book+Basic:700italic)\;* However, I need the result CSS to have the below string, without quotes, etc. *@import url(http://fonts.googleapis.com/css?family=Gentium+Book+Basic:700italic http://fonts.googleapis.com/css?family=Gentium+Book+Basic:700italic);* Now, of course, I peered into the sourcehttps://github.com/noprompt/garden/blob/master/src/cljx/garden/stylesheet.cljx#L48, and tried just passing in the url. But that doesn't give me the output I want either (has quotes + missing url). *(css (at-import http://fubar.com http://fubar.com/))* *= @import \http://fubar.com http://fubar.com/\;* Is there a correct way of calling this? Otherwise, is there a way to just pass through raw CSS, from my input edn / clj? Thanks for any insights. *2. * Hi Tim, You can do two things here. Use garden.stylesheet/cssfn to create a temporary css function: (def url (cssfn :url)) Use garden.def/defcssfn to do essentially same thing: (defcssfn url) You can then use either of these approaches to achieve the result you're interested in. (css (at-import (url http://example.com/;))) Otherwise, is there a way to just pass through raw CSS? People have asked me about this a number of times and it's something I've generally been against from the start. It leads to dirty hacks and strange bugs which are usually the result of operator errors. By eliminating the number of places where one can pass raw strings Garden can ensure correct output for most cases and in turn the number of issues that might be opened. Of course, you can still do wacky stuff inside selectors. Feel free to ask your questions in the issue tracker as well. It's nice to have these answers documented there for future users. ... Thanks Tim Washington Interruptsoftware.com http://interruptsoftware.com On Sat, Mar 22, 2014 at 9:41 PM, Joel Holdbrooks cjholdbro...@gmail.comwrote: Greetings everyone, About a year ago I began working on Garden and in the short time the library has been around it's grown a bit. Although many folks seem to be interested in it, there's certainly not as much adoption of the library as I'd like to see. Sass, Less, and (god help us) pure CSS still appear to be the default choices for many people writing web applications in Clojure. This is something I'd like to change... but I need *your* help! No, no. Put down the phone. Don't look for a KickStarter URL. It's nothing like that. How you can help Garden I'm looking for individuals who are interested in the following: - improving the compiler code - improving/extending existing API's - building an interface to the CSSOM I'm also open to good 'ol fashioned suggestions, pain points you've experienced using the library, or flat out letting me know what it would take to get you to choose Garden over the alternatives for your next project. How you can help Thorn Thorn is very young project and has no official release yet. So what is it? At the moment it's the beginnings of a Sass Parse Tree transformer; something that will take CSS/SCSS/Sass code and give you Garden code. There's a lot of fabulous libraries available in Sass and I'm sure it's a big factor when choosing how to go about CSS generation. I'm looking for individuals who are interested in the following: - accurately transforming CSS/SCSS/Sass to real Clojure code targeting Garden - accurately transforming Less to real Clojure code targeting Garden Why? I deeply believe that being able to author CSS in Clojure or ClojureScript is a
Re: Garden, Thorn - Looking for contributors
Hi Joel, thanks for your great work on garden! Definitively helping me every day. Can you share what you have in mind regarding CSSOM integration? It certainly opens cool perspective and I'm curious how you see it fit with garden. I would be interested in giving you a hand here. Maybe a github issue would help start discussions? Julien Le samedi 22 mars 2014 22:41:04 UTC-3, Joel Holdbrooks a écrit : Greetings everyone, About a year ago I began working on Garden and in the short time the library has been around it's grown a bit. Although many folks seem to be interested in it, there's certainly not as much adoption of the library as I'd like to see. Sass, Less, and (god help us) pure CSS still appear to be the default choices for many people writing web applications in Clojure. This is something I'd like to change... but I need *your* help! No, no. Put down the phone. Don't look for a KickStarter URL. It's nothing like that. How you can help Garden I'm looking for individuals who are interested in the following: - improving the compiler code - improving/extending existing API's - building an interface to the CSSOM I'm also open to good 'ol fashioned suggestions, pain points you've experienced using the library, or flat out letting me know what it would take to get you to choose Garden over the alternatives for your next project. How you can help Thorn Thorn is very young project and has no official release yet. So what is it? At the moment it's the beginnings of a Sass Parse Tree transformer; something that will take CSS/SCSS/Sass code and give you Garden code. There's a lot of fabulous libraries available in Sass and I'm sure it's a big factor when choosing how to go about CSS generation. I'm looking for individuals who are interested in the following: - accurately transforming CSS/SCSS/Sass to real Clojure code targeting Garden - accurately transforming Less to real Clojure code targeting Garden Why? I deeply believe that being able to author CSS in Clojure or ClojureScript is a key piece to having an extremely compelling story for web application development in Clojure. Being able to *program* CSS and not just *preprocess* is a big advantage over existing tools. Being able to use all of Clojure everywhere has astounding possibilities. If any of this sounds interesting to you please get in contact with me or reply here. I will also be in San Francisco tomorrow until Tuesday for Clojure/West if you'd like to discuss these items in person. Truly, Joel -- You received this message because you are subscribed to the Google Groups Clojure group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups Clojure group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Garden, Thorn - Looking for contributors
Joel, Count me in... You can contact me offline at kahunamoore a/t coopsource d/o\t org Thanks for this library! Alan On Tuesday, March 25, 2014 12:33:15 PM UTC-7, Julien wrote: Hi Joel, thanks for your great work on garden! Definitively helping me every day. Can you share what you have in mind regarding CSSOM integration? It certainly opens cool perspective and I'm curious how you see it fit with garden. I would be interested in giving you a hand here. Maybe a github issue would help start discussions? Julien Le samedi 22 mars 2014 22:41:04 UTC-3, Joel Holdbrooks a écrit : Greetings everyone, About a year ago I began working on Garden and in the short time the library has been around it's grown a bit. Although many folks seem to be interested in it, there's certainly not as much adoption of the library as I'd like to see. Sass, Less, and (god help us) pure CSS still appear to be the default choices for many people writing web applications in Clojure. This is something I'd like to change... but I need *your* help! No, no. Put down the phone. Don't look for a KickStarter URL. It's nothing like that. How you can help Garden I'm looking for individuals who are interested in the following: - improving the compiler code - improving/extending existing API's - building an interface to the CSSOM I'm also open to good 'ol fashioned suggestions, pain points you've experienced using the library, or flat out letting me know what it would take to get you to choose Garden over the alternatives for your next project. How you can help Thorn Thorn is very young project and has no official release yet. So what is it? At the moment it's the beginnings of a Sass Parse Tree transformer; something that will take CSS/SCSS/Sass code and give you Garden code. There's a lot of fabulous libraries available in Sass and I'm sure it's a big factor when choosing how to go about CSS generation. I'm looking for individuals who are interested in the following: - accurately transforming CSS/SCSS/Sass to real Clojure code targeting Garden - accurately transforming Less to real Clojure code targeting Garden Why? I deeply believe that being able to author CSS in Clojure or ClojureScript is a key piece to having an extremely compelling story for web application development in Clojure. Being able to *program* CSS and not just *preprocess* is a big advantage over existing tools. Being able to use all of Clojure everywhere has astounding possibilities. If any of this sounds interesting to you please get in contact with me or reply here. I will also be in San Francisco tomorrow until Tuesday for Clojure/West if you'd like to discuss these items in person. Truly, Joel -- You received this message because you are subscribed to the Google Groups Clojure group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups Clojure group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Garden, Thorn - Looking for contributors
I wonder what is so bad about pure CSS. Don't get me wrong - I do appreciate projects like these. -- You received this message because you are subscribed to the Google Groups Clojure group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups Clojure group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Garden, Thorn - Looking for contributors
Greetings everyone, About a year ago I began working on Garden and in the short time the library has been around it's grown a bit. Although many folks seem to be interested in it, there's certainly not as much adoption of the library as I'd like to see. Sass, Less, and (god help us) pure CSS still appear to be the default choices for many people writing web applications in Clojure. This is something I'd like to change... but I need *your* help! No, no. Put down the phone. Don't look for a KickStarter URL. It's nothing like that. How you can help Garden I'm looking for individuals who are interested in the following: - improving the compiler code - improving/extending existing API's - building an interface to the CSSOM I'm also open to good 'ol fashioned suggestions, pain points you've experienced using the library, or flat out letting me know what it would take to get you to choose Garden over the alternatives for your next project. How you can help Thorn Thorn is very young project and has no official release yet. So what is it? At the moment it's the beginnings of a Sass Parse Tree transformer; something that will take CSS/SCSS/Sass code and give you Garden code. There's a lot of fabulous libraries available in Sass and I'm sure it's a big factor when choosing how to go about CSS generation. I'm looking for individuals who are interested in the following: - accurately transforming CSS/SCSS/Sass to real Clojure code targeting Garden - accurately transforming Less to real Clojure code targeting Garden Why? I deeply believe that being able to author CSS in Clojure or ClojureScript is a key piece to having an extremely compelling story for web application development in Clojure. Being able to *program* CSS and not just *preprocess* is a big advantage over existing tools. Being able to use all of Clojure everywhere has astounding possibilities. If any of this sounds interesting to you please get in contact with me or reply here. I will also be in San Francisco tomorrow until Tuesday for Clojure/West if you'd like to discuss these items in person. Truly, Joel -- You received this message because you are subscribed to the Google Groups Clojure group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups Clojure group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
