> 1. Going back and forth from code to visual editor with randomly > delete chunks of code, add properties to selectors you didn't intend, > and other oddities. Reproducible always. > 2. The live preview is extremely finicky about when it updates. It > usually only updates when you press the delete key.
Seriously though, using a visual editor and an IDE internal rendering engine for CSS is IMHO a losing battle from the start. Your visitors will see your CSS in a browser, so it is best to also test it in browsers. IMHO a good editor only needs to provide colour coding, some handy keyboard shortcuts and auto-completion. Personally I use Homesite 5.0 for everything and I extended it with own scripts for certain tasks. -- Chris Heilmann Blog: http://www.wait-till-i.com Writing: http://icant.co.uk/ Binaries: http://www.onlinetools.org/ ______________________________________________________________________ css-discuss [EMAIL PROTECTED] http://www.css-discuss.org/mailman/listinfo/css-d IE7b2 testing hub -- http://css-discuss.incutio.com/?page=IE7 List wiki/FAQ -- http://css-discuss.incutio.com/ Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
