On 4-Nov-2008, at 12:00, Roland Küffner wrote: > I'm not sure if the implementation of such a feature could be done > that easily as one would have to implement the whole logic behind CSS. > BBEdit is a text editor not a rendering engine (it uses Webkit for > it's preview) and such page rendering features might steer the ship > into unknown waters (e.g.: how should such a parser handle invalid but > common CSS hacks?) So my (outside) guess is, that you shouldn't hold > your breath for this to come to BBEdit.
It doesn't have to be that robust. Just a simple coloring for tags it THINKS aren't used. that at least gives you someplace to start. It can be rather frustrating trying to go through doing finds trying to see which, if any, styles are orphaned. > Fortunately there are more adequate tools for your problem. In case > you don't know it, the Firefox extension Dust-Me Selectors does > exactly what you are looking for: http://www.sitepoint.com/dustmeselectors/ Yep, but even then, you are bouncing back and forth. It's not that much more useful than a find in BBEdit. -- "Katrina, $4 gas, a trillion dollar war, rising unemployment, deregulated housing market, global warming...NO MORE!" http://is.gd/2mxY --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "BBEdit Talk" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/bbedit?hl=en If you have a specific feature request or would like to report a suspected (or confirmed) problem with the software, please email to "[EMAIL PROTECTED]" rather than posting to the group. -~----------~----~----~----~------~----~------~--~---
