On Thu, Jul 29, 2010 at 21:28, Nathan Weizenbaum <[email protected]> wrote:

> Mislav, I'm curious why you chose to use RSpactor rather than FSSM, which
> has built-in support for Linux.
>

I've looked into fssm used by Sass/Compass, but it's still tied to
RubyCocoa, meaning it needs system ruby on the Mac. We've done some work on
RSpactor to use FSEvents directly without the need for RubyCocoa, meaning it
can be installed on any ruby. When this and Linux support is released,
RSpactor will have a slight advantage over fssm. But the real reason why I'm
sticking to RSpactor is that I have bigger plans for it. I might rename my
fork, though, since it's getting further and further away from official
version(s?).

As for polling on Windows, I don't plan to support it because I don't
believe it can work for a huge project. Polling several .sass files can
scale, but for using LiveReload and auto-testing you have to poll for
hundreds of files, and that just eats away the CPU and hard drive life.


> Using the middleware means that the user doesn't have to manually start an
> extra script, and that they're guaranteed to see the latest CSS after a
> refresh


There might have been a misunderstanding here. I love the Sass::Plugin::Rack
middleware. What I was saying is that the brittle solution for LiveReload is
the middleware *reordering* you were discussing in this thread. If the
server handles static files on its own (like Apache), the direct request to
a .css file will never hit the ruby app, and all the middleware magic you
did here to support direct requests to stylesheets is useless. The true
solution for LiveReload is my script: the same process that handles
websocket connection for the browser also listens to change events on the
filesystem *and* compiles Sass.

-- 
You received this message because you are subscribed to the Google Groups 
"Haml" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to [email protected].
For more options, visit this group at http://groups.google.com/group/haml?hl=en.

Reply via email to