Another feasability question:
How feasable would it to be to add a preference that allows you to specify which of your installed markup plugins is used by the built-in compose button shortcuts (such as the 'url', 'i','b' and 'u' buttons).
What I'm running into is when using the 'user trust' plugin on a multiuser blog, users that haven't reached a level of trust worthy of HTML access are pushing the buttons and getting posts filled with unrendered HTML. Having the buttons default to bbcode would be the ideal fix for this situation.
I can see how this would be a useful feature to have, but don't know if a plugin is really the best way to do it. Would adding the ability to each individual markup plugin be required in addition to one in which you would make the setting? Or would skipping the plugin and making it a core feature be the way to go?
markup plugins vs. compose buttons
-
garvinhicking
- Core Developer
- Posts: 30022
- Joined: Tue Sep 16, 2003 9:45 pm
- Location: Cologne, Germany
- Contact:
Re: markup plugins vs. compose buttons
Well, this could be possible, but would be a bit hard to code to decide which markup code is used.
What you can do is to enhance the emoticonchooser plugin to contain your own markup plugin code, or create a special plugin that just adds buttons to the editor; the emoticonchooser is a very good starting point for such a plugin!
Best regards,
Garvin
What you can do is to enhance the emoticonchooser plugin to contain your own markup plugin code, or create a special plugin that just adds buttons to the editor; the emoticonchooser is a very good starting point for such a plugin!
Best regards,
Garvin
# Garvin Hicking (s9y Developer)
# Did I help you? Consider making me happy: http://wishes.garv.in/
# or use my PayPal account "paypal {at} supergarv (dot) de"
# My "other" hobby: http://flickr.garv.in/
# Did I help you? Consider making me happy: http://wishes.garv.in/
# or use my PayPal account "paypal {at} supergarv (dot) de"
# My "other" hobby: http://flickr.garv.in/