Hacker News Reader

Comment by dsmithn | Hacker News Reader

From my understanding, the point of the project is to allow developers to edit css and see the results realtime, without having to save, switch windows from their CSS editor to their web browser and refresh the window. Or without having to edit the css in realtime by using Firebug, then edit those changes back into your actual file.

They also give you the option of hosting your CSS file on their servers, which is why you'd need the link to that CSS file.

It's all explained on their website which you might not have read/understood, or maybe I am missing something.

As a web developer working on quite a few projects, this tool seems great, although I can't have them hosting CSS for internal projects.

View on HN

I did read through the site, and though I did not download the tool and try it out yet, the site seems to be catering to an individual who is used to SSHing in to / FTPing up to a site and hitting refresh (I did this when I was first learning about the web way back when as well, and I can appreciate the productivity gain here).

The hosting of your CSS files on their servers is also not suited for a development environment that has more than 1 environment, as I would not want to be editing files that are on a live server on a regular basis without first making those changes locally (and possibly checking them into an SCM of some sort first) because my css would quickly become out of sync across environments.

May I ask, the projects that you work on, do you have more than 1 environment that you use and do you collaborate with any other developers on these projects?

If you try it out, you'll see that there are two modes, Preview and Published. Your changes don't go to anyone else until you are done with them, so we won't serve up half-baked CSS while you're still working on it. Once you're done, you hit Publish and only then is it live.

They specifically say there are two annoying issues this solves: 1. having to"CTRL-S–ALT-TAB–CTRL-SHIFT-R–JOY!", and 2. editing in Firebug "then trying to extract those tweaks back out of Firebug and into your website’s CSS files".

As far as working on teams, they're "thinking about how to expose your CSS in a versioned way so that you can keep it in Mercurial (with Kiln!), or Git, or whatever other version control software you might be using". Perhaps you're right, it's better to wait until that is implemented if you have that kind of setup.

EDIT: I've started testing it, and you can add other admins and editor users for sites, very nice.

Maybe this isn't obvious, but its a webapp. While technically "download" is still appropriate, I suspect you misinterpreted how it works.

Love the humor and simplicity of this product, but I can't get it to show me the CSS unless I add yet-another <script> and <link> tag to my source.

http://i.imgur.com/eKKxY.png

Seems like a Web Putty browser plugin would help preserve the "local transparent editing a la Firebug" use case. Transparent meaning, no edits to your existing HTML required to demo different CSS stylings. Or am I misunderstanding this?

Reply on news.ycombinator.com