Thread:Pecoes/@comment-4674838-20121105085352/@comment-3508190-20121105131124

My own CSS testing and developing experience has always been very messy. For starters I use two editors: Dreamweaver (because it makes editing CSS very convenient) and Komodo (which is a programmer's editor and unlike Dreamweaver never gets in the way of writing stuff).

And then I do a lot of ad-hoc testing and modifying in Firebug. It's this part that makes things messy. Dreamweaver and Komodo have no problem working on the same file. Whenever I switch to either of them the changes I save in the other are already there. But Firebug! Oh Firebug! I have searched for an addon that would give me same convenience but haven't found one yet.

Ideally all changes would be recorded, extracted from the page and saved to a local file. Doesn't happen. I have to copypaste (and even that's tricky) every change from Firebug to Komodo/Dreamweaver. If there's one part of my workflow that desperately needs improving it's that. What I'd need is a tool like Acebug - but for CSS.

So what does that mean for PortableCSSPad? It does a lot of things very nicely. It's got a nice immediacy to it. It does however add a fourth tool to my already broken workflow and would break it further, because it doesn't make Firebug superfluous.

I think I've said it before: You could do a lot more good if you would get involved with Firebug itself. Firebug - for all its imperfections - already has a metric ton of tools you will find a bit hard to replicate in your PortableCSSPad.

If you do decide to get involved in Firebug, I might actually join you! :)