STYLE_ constants obeyed about libsass HOT 18 CLOSED

Yes, all the output styles will be implemented. It's currently a low priority compared to other features such as full interpolation and selector inheritance.

from libsass.

Awww, we didn't mean to ruin your excitement.

On Tue, May 1, 2012 at 6:05 AM, Jamie Rumbelow <
[email protected]

wrote:

I got all excited about adding different output styles to my libsass
binding to discover that only SASS_STYLE_NESTED is working!

Are there still plans to make the other style constants work?

---

Reply to this email directly or view it on GitHub:
#15

from libsass.

We also would like to see compressed!

from libsass.

I'll be getting this feature in by the end of the month!

from libsass.

Added support for compressed output styles. Please give it a try!

from libsass.

Not working for me. Getting an empty output

from libsass.

Can you provide more details on how you're invoking LibSass? It's been working for us.

from libsass.

Using SassC
as in
./bin/sassc [input file]

from libsass.

Oh, the SassC command-line tool is still hard-coded to use the nested style (haven't had time to update that yet!). To use the compressed style, you currently have to set the flag in the C interface when invoking LibSass as a library.

from libsass.

I'm just working on sassc flag handling now. Is it ok to use getopt or does it need to be Windows friendly?

from libsass.

Hmm ... preferably Windows-friendly, but that's less of a priority than keeping the core library itself portable. So I'd say go ahead and use getopt if it makes things much easier and more robust. Thanks for the help!

from libsass.

Sorry if i being a bit dense - dont have much experience with C

Changed the sassc.c file line 16 to ctx->options.output_style = SASS_STYLE_COMPRESSED;

Then ran make

Output is now empty

from libsass.

Have you updated the libsass submodule? Try going into the libsass subfolder and run git pull. Then back out and do a make clean and make.

from libsass.

That did it! Thanks for the help...
Seems to be working well

from libsass.

No problem! And let me know if the styles don't look right!

from libsass.

Will be testing tomorrow. Ill let you know if there any problems!

from libsass.

Isn't expanded and nested somewhat redundant?

Supposedly, nested produces the following output:

a > b > c {
    declaration }
    a > b > c > d {
        declaration1;
         declaration2; }

and the expanded is supposed to be:

a > b > c
{
    declaration;
}

a > b > c > d
{
    declaration1;
     declaration2;
}

Then there might be a requirement which begs another kind of nested expansion:

a > b > c
{
    declaration;
}

    a > b > c > d
    {
        declaration1;
        declaration2;
    }

So, wouldn't it make sense to have just two styles: expanded (which is nested-expansion; unobtrusive, well-formatted and nested) and compact (minified flavor)? Perhaps, expanded can be aided by another option --indent, which is the base indentation in case of multi-nesting (normally its 2 or 4).

On a related note, both kind of outputs should get the _detailed_ source maps pinpointing the location for each source-to-source artifacts (exactly how lessc does it), as opposed to the mere hints -- not capturing the details to full extent / depriving consumers of implementing some extraordinary features. See #324.

from libsass.

We are trying to match the styles produced by the Ruby implementation. I'm going to close this since the issue is actually about the constants, not compatibility with Ruby sass.

from libsass.