4 ms·

Don't get us wrong, we love Firebug, but it is kind of a pain to then take the changes you made, copy them out, paste them somewhere else, and then deploy it. B

by tghw 15y ago

Don't get us wrong, we love Firebug, but it is kind of a pain to then take the changes you made, copy them out, paste them somewhere else, and then deploy it. Backfire makes that easier, which is good, but you still don't have SASS and Compass, which I find makes working with CSS much nicer. In a static environment, you can just compile the SASS to CSS before you deploy, or you can use WebPutty and have us host it for you.

jwdunne 15y ago
WebPutty is really cool, by the way. I'm currently having a play with it and it's funny but I have some suggestions: A firebug inspired element inspector may be a good thing. I think jumping straight to the line of CSS rather than the separate, filtered window would be a great idea. I'd really love that. Another thing, but less important, would be auto-complete. Either that or ways to expand ZenCSS abbreviations. This would push my productivity to the moon. Another thing I was thinking of hacking on to Firebug (when I find out how) is selector hinting. The way this would work is, when you type a selector, the available ones are given to you, much like method hints in IDEs. This would be very useful to me at least. There have been many times when I've needed to know a particular hierarchy/id name/class name and found myself having to reference elsewhere. To host CSS would be a social/pointy-haired-boss issue but I could make necessary recommendations. In any sense, I love the work that has been done. This is my more constructive feedback :)
- tghw 15y ago
  Thanks for the suggestions! We've considered embedding Firebug Lite, since it gets you most of the inspect stuff you'd want for CSS editing. We may still add it. Autocomplete is also high on the list of features, we just ran into some problems with CodeMirror 2.

4 ms·

Don't get us wrong, we love Firebug, but it is kind of a pain to then take the changes you made, copy them out, paste them somewhere else, and then deploy it. B

by tghw 15y ago

jwdunne 15y ago
WebPutty is really cool, by the way. I'm currently having a play with it and it's funny but I have some suggestions: A firebug inspired element inspector may be a good thing. I think jumping straight to the line of CSS rather than the separate, filtered window would be a great idea. I'd really love that. Another thing, but less important, would be auto-complete. Either that or ways to expand ZenCSS abbreviations. This would push my productivity to the moon. Another thing I was thinking of hacking on to Firebug (when I find out how) is selector hinting. The way this would work is, when you type a selector, the available ones are given to you, much like method hints in IDEs. This would be very useful to me at least. There have been many times when I've needed to know a particular hierarchy/id name/class name and found myself having to reference elsewhere. To host CSS would be a social/pointy-haired-boss issue but I could make necessary recommendations. In any sense, I love the work that has been done. This is my more constructive feedback :)
- tghw 15y ago
  Thanks for the suggestions! We've considered embedding Firebug Lite, since it gets you most of the inspect stuff you'd want for CSS editing. We may still add it. Autocomplete is also high on the list of features, we just ran into some problems with CodeMirror 2.