Alan asks the CSS Guy what I use for CSS editing
Alan asks:
What software do you use for CSS editing?
I use BBEdit. When I was on a PC, I used Homesite. At the root of it, I just need some color coding and line numbers to keep me sane, but the extra features of BBEdit, like the grep search, can come in handy.
I use those not just for CSS, but for HTML as well. I have found that it fits my work flow best.
I remember when Dreamweaver started supported CSS in preview mode, and quickly requested that my employer purchase it. After a few weeks, I realized that it wasn't getting the job done. I like to see how my changes affect different browsers, and Dreamweaver's preview pane can't do that. Plus, I find it's just as easy to switch from text editor to browser as it is to switch from coding view to preview mode on Dreamweaver. (Split view? No thanks.)
For a while I used TopStyle as well, and for the same reasons that I stopped using Dreamweaver, I eventually abandoned it.
On the rare occasions I need to make a complicated table, I use Dreamweaver.
I see new things come out, like TextMate, and more recently, Coda, and wonder if it would be worth the jump. I intend to try TextMate soon, but will probably not use Coda for the same reasons mentioned above. (I like playing with their web page, though.)
So, to add to my answer, I use BBEdit and various browsers.
I had a tough time getting IE7 to browse local files, so I enabled the Mac's apache web server and keep most of my projects within browsable directories. That way all browsers can get to it. The webserver also comes in handy when playing with AJAX, as you can't just browse a local file and have the the xmlhttprequest object work (found that out the hard way - rookie mistake).
So, to be even more complete, I use BBEdit, various browsers, Parallels, and Apache. Hope that helps.
Comments (11)
Silus Grok said:
This post seems timely, given Panic's CODA software being unveiled yesterday... I'd love to see what you think of CODA after you've had a chance to play with it.
I, too, use BBEdit ( in conjunction with Transmit ) for all my site-coding needs, but am thoroughly intrigued by CODA.
# April 24, 2007 11:48 AM
CSS Guy said:
@Silus:
I tried Coda, (if you call 30 minutes trying), and quickly abandoned it. I realize there is a learning curve with any new app, but I could tell that this wouldn't work for me. It's makes everything so gosh-darn pretty, and well, that's part of the reason I don't like it. I prefer editing my CSS file as strings of text rather than clicking buttons and select boxes.
I have no need of terminal (makes me wonder - should I?). I don't use FTP at all for development since my MacBook Pro has a webserver on it to development from. Even the preview option in Coda is representative only of Safari (or other webkit-based browsers), so I still would have to keep a Firefox and IE window open.
I'm sure it will work for many, especially those who are just starting to set up their toolkits. And hey, with the free trial, there's little reason not to see if it fits. I think it's worth the download just to see the special effects on the website when clicking the "download" link.
# April 24, 2007 1:00 PM
Lasse said:
You should really give CSSEdit from MacRabbit a try! I have been using it for a couple of months, and I am addicted to the flexibility and the instant preview. The link is http://macrabbit.com/cssedit/
# April 24, 2007 4:07 PM
Lasse said:
And by the way: I just realized today that you can easily remove the input panel and switch to text-only mode.
# April 24, 2007 4:08 PM
Simon said:
I too use CSSEdit, and find it to be really useful.
I also downloaded Coda and tried it, but (as Steven from Panic admitted) I am unable to preview PHP code reliably on my local webserver. It is darned pretty, and when my boss buys me a copy of Dreamweaver CS3, no doubt I'll love that as much as version 8!
# April 26, 2007 8:02 AM
CSS Guy said:
@Lasse and Simon:
It sounds like I should give CSSEdit a look.
# April 26, 2007 8:49 AM
michael said:
I'll give a third vote for CSSEdit. I use mostly the code view but love the new version's preview/x-ray capability. Click on any page element and you get a DOM tree with element classes and id's. And it occasionally nice to have the hand holding option for selectors that I don't use often. I figure the $29 it costs is no more than a good reference book.
But I use it as backup, mostly for debugging. As a learning tool the wizard mode is probably wonderful. Once one learns the basics, though, strait code is faster to crank out. So why not stay with one tool? You didn't specifically say that in your article but I'm reading it between the lines. Hope that's not taking too much liberty.
I recently made the switch from BBBEdit to TextMate. This is a tougher call. I miss some of BBEdit's utilities but code faster with TextMate.
# April 26, 2007 10:06 AM
Roger said:
I use Dreamweaver and BBEdit. Depends on the project.
And just so we all need to test these things on other browsers... I've been using www.browsercam.com.
It's amazing how screwed up a site can be in IE in different windows versions.
# April 26, 2007 1:36 PM
bezalel said:
Unfortunately, CSSEdit is for MAC only. :/ Dreamweaver is not the pioneer nowadays, you are right. I use Style Master. Has anyone tried it?
# June 18, 2007 6:31 AM
fractionofawhole said:
Dreamweaver CS3 for me. Strictly code view because as pointed out the preview view isn't all that great and doesn't represent all browsers. I also use BBedit on my Mac at times though it's very rare. It mainly just sits there and takes up space in the dock.
# September 20, 2007 5:20 PM
topstyle orphan said:
When I switched back to mac I had a spending freenzy and bought both bbedit, cssedit and textmate.... I prefer textmate but it does'nt preview very well.
the best I ever have used remains Topstyle and it doesn't run on a mac :-(.
# May 7, 2008 4:32 AM