On Sunday, 23 November 2014 at 19:36:16 UTC, Jacob Carlborg wrote:
> For more D features I would add a thin layer on top of the raw bindings. Like creating wrappers for functions accepting C strings and have them accept D strings instead.
Yes, I think, there should be more layers, more D-ish constructions, but on top of binding, not inside it. I think, it could be more useful for someone who is not satisfied by existing wrappers.

On Monday, 24 November 2014 at 00:40:39 UTC, Colden Cullen wrote:
> On Saturday, 22 November 2014 at 12:32:50 UTC, Lodin wrote:
>
> This looks great! I plan on using it to build a diet plugin, just like Martin's coffee-script plugin[1]. Any chance you could register it on the Dub Registry[2] though? It would make using this a lot easier.
>
> [1] https://github.com/MartinNowak/diet-coffee
> [2] http://code.dlang.org/
Of course, I want to register it, but I think it should be a part of Derelict Project, not unofficial binding. What should I do to realize it?

And one thing about the diet plugin. I plan to make thin wrapper around binding to simplify using. Something like `sassc` which allows using libsass from console with options. Of course, it should be useful like a library too. Is the diet plugin a same thing? Or should it be the next layer around wrapper?

On Monday, 24 November 2014 at 17:32:36 UTC, Lodin wrote:
> Of course, I want to register it, but I think it should be a part of Derelict Project, not unofficial binding. What should I do to realize it?
>
> And one thing about the diet plugin. I plan to make thin wrapper around binding to simplify using. Something like `sassc` which allows using libsass from console with options. Of course, it should be useful like a library too. Is the diet plugin a same thing? Or should it be the next layer around wrapper?

I can't help you with getting it included in Derelict, but I think Mike Parker[0] is probably the one to talk to.

I think the diet plugin would serve best as a layer on top of your wrapper. It's scope is limited to taking inline sass, as well as paths to sass files, compiling them, and including the result on the HTML page. If you could make that process easier with a wrapper, it would make the plugin much simpler.

[0] https://github.com/aldacron

So I did it. Sorry for make you waiting for such a long time.

Short info:
- Git: https://github.com/Lodin/sassed
- Tested on: Ubuntu 14.04, DMD 2.066.1.
- Known bugs: segfault after program ends. It does not happen in all cases, and as I know does not affect compilation result. Trying to catch it.
- Documentation: DDOC and Git Readme.md

P.S. As before, if I done something wrong (including bad interface or not effective code) please tell. I'll be happy to learn doing it in the right way.

Major update for DerelictSASS and Sassed due to C API change in libsass.

DerelictSASS - v2.0.0
https://github.com/Lodin/DerelictSASS
There are complete interface change: as I know, previous libsass C API does not work anymore, and new API was written.

Sassed - v0.2.0
https://github.com/Lodin/sassed
It is updated to new DerelictSASS version and has some new features such as sass compile error and success handlers. Also segfault bug was fixed.