![]() background: url("./img/beers/porter.png") no-repeat background: url("./img/beers/pilsner.png") no-repeat background: url("./img/beers/stout.png") no-repeat In LESS you can write a basic logic statement using a ‘guarded mixin’: when > 40%). While this is a nice thought for easing users into writing it, there are a few issues which make it a lot less fun to work with than Sass: Logic statements ![]() LESS aims to be as much like CSS in style, syntax and structure. This means you can easily harness all the power of your favorite framework without having to deal with the mess of using multiple tools. Compass also lets you add an external framework like Blueprint, Foundation, or Bootstrap on top.Compass has some really awesome features like dynamic sprite-map generation, legacy browser hacks and cross-browser support for CSS3 features. There are libraries available to LESS users, but nothing really comes close to Compass, which is regularly maintained and contributed to by a huge community. Sass users can utilize the awesome power of the Compass library.Like LESS, Sass comes with lots of very handy functions built-in, including color manipulation, mathematics, and parameter lists. guarded mixins for conditionals, self-referencing recursion for loops). LESS can do these things but in an inefficient and counter-intuitive way (ie. Sass lets you write reusable methods and use logic statements ie.Sass is the next level, a tool for the slightly more experienced front-end developer. Looking back, I like to imagine LESS as the training wheels for beginners, or perhaps a gateway-drug into preprocessed CSS. …Until I discovered the truly awesome power of Sass and Compass. ![]() ![]() Compared to CSS, everything about LESS was very easy and friendly, I was quite enjoying LESS for a while… It’s very similar to plain CSS, so writing it is intuitive. LESS is great for beginners: it’s really easy and quick to set it up. If you are interested, I’ve also written about how to get started using Sass and the problems with pre-processors.īefore I begin my highly opinionated tirade, let me just mention that I learned LESS first. In this article I’ll explain why Sass really is the best and why you should start using Sass if you haven’t already. It's the same thing with any other vendor library in Joomla.The Sass versus LESS argument has been done to death. I still don't understand the security argument. We have to have the most secure tools for our end-users to customize stuff In this case node-sass is the "bad guy" -) I only see conflicts when, for example, one compiler doesn't resolve paths like the other one. I've mentioned that already years ago when the first J4 release came out but closed the issue frustrated -)įrom my point of view the SCSS files should be inside the template folders and not in /media/ because we would have then again a restricitive core binding to version x.outdated.2ĪND: This discussion is again a mixture of professors and users needs -) PHP compiling is fine for most users if the compiler is well maintained. The only point where I agree in this discussion is that the core templates should contain all SCSS files after build so that you can run a SCSS compiler without issues over them. The mentioned framework is not mine but I saw how bad and confusing the idea is to bomb the users with mio of SCSS color settings via template styles -) Amd I saw how frustrating it is when a framework (or Joomla) dictates the Bootstrap version (the mentioned framework has changed that with their last release (not sure)) or if the compiler is not up-to-date and fails with newer SCSS possibilities. I'm using my own tools (node, PHP, Prepros), just sometimes, and set up my SCSS directories on my own from scratch. How do you secure your ScssPhp files? they need to be secured right?
0 Comments
Leave a Reply. |