I think I'm going to look into it.
One solution would be to retrieve all non-specific-TAG related CSS selectors every time you change the theme or just change the CSS theme file AND save those values in a _javascript_ style file to be included before TinyMCE own files.
Regarding your concerns with loose selectors:
How many times do anyone change the theme or the CSS file?
Only a few times I think.
And if you change a theme and forgot to include in the new CSS your own made CSS selectors then you shouldn't have touched the CSS in the first time, should you? ;-)
Best,
Lopo
2005/12/6, Andy Skelton <[EMAIL PROTECTED]>:
On 12/6/05, Humaneasy Consulting <[EMAIL PROTECTED]> wrote:
> Is it too hard to have a pulldown menu with all the general classes (not A,
> Hx or any other associted with a specific HTML tag) so that we can add them
> as we wich?
That's easy. The hard part is knowing which classes are supported by
which theme stylesheets. Not all themes include CSS selectors for a
class named "capitular."
Then, if you switch themes, your classes might do something undesired
in the other theme but now they're coded into the post so... too bad.
If you want to flesh out the scheme and code to do something like
this, including a way for theme authors to get their special classes
into a dropdown in the editor, please do so. If you need more plugin
hooks in the core, please ask for them right away.
Andy
_______________________________________________
wp-testers mailing list
[email protected]
http://lists.automattic.com/mailman/listinfo/wp-testers
_______________________________________________ wp-testers mailing list [email protected] http://lists.automattic.com/mailman/listinfo/wp-testers
