I am aware of bugs in this Sugar but as I now use Coda 2 instead of Espresso 2 I no longer have the time or motivation to update it. Please feel free to fork and fix bugs yourself, I may find time to merge pull requests, or you could maintain your own branch.
This Sugar is incomplete. It's better than nothing. Here is what is currently supported:
- Use of .scss file extension or .css.scss extension to trigger the Sugar
- CSS (plain and simple) - this is inherited from the default CSS Sugar
- @include selector
- @mixin definition
- @warn directive
- @debug directive
- @if @else if @else @for @while statements
- $variable use, $variable definitions at root level
- !default suffix
- functions (the syntax is already a part of CSS)
- Nested selectors (only up to 5 levels deep, and only root level selectors show up in the navigator ATM)
- Download the zip
- Extract said zip
- Rename folder to .sugar
- Double click the .sugar file
- Restart Espresso - voila!
I'm just a programmer and designer who loves Espresso and Sass. There [was] no Sass Sugar for Espresso in active development, and the one/two I found were incomplete. This Sugar is arguably more incomplete, but I aim to change that.
If you want to help, that would be great. I have no experience with collaborative development or GitHub, but lets give it a shot!
Basic CSS structure and functionality is already implemented by the Default CSS Sugar, so why reinvent the wheel? We include the default CSS Syntax, then build on it using SyntaxInjections. We shouldn't need to touch the Syntax file often, use SyntaxInjections where possible. I have left some of the original CSS Sugar commented out purely for reference.
Aim to get the Syntax complete first, then work on Itemizers to get the Navigator working right. Once these core basics are done, finally we can add the fancy stuff like CodeSense.
- Try the Espresso IRC room - ##espresso
- Message me on GitHub
- Tweet to me @sibrow
- Email me... actually I have enough Russian brides as it is, sorry