STYLE_ constants obeyed

[jamierumbelow]

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?

[akhleung]

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.

[HamptonMakes]

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

On Tue, May 1, 2012 at 6:05 AM, Jamie Rumbelow <
reply@reply.github.com

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

[MrBenGriffin]

We also would like to see compressed!

[akhleung]

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

[akhleung]

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

[paramdhal]

Not working for me. Getting an empty output

[akhleung]

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

[paramdhal]

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

[akhleung]

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.

[craigbarnes]

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

[akhleung]

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!

[paramdhal]

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

[akhleung]

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.

[paramdhal]

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

[akhleung]

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

[paramdhal]

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

[am11]

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.

[HamptonMakes]

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.