NOTE: If you are a developer, please use a private wiki based on foswiki/trunk on a daily base ...or use
trunk.foswiki.org to view this page for some minimal testing.
Use
Item9693 for docu changes for 1.2 and 2.0.
Item9303: HTML2TML removes JQuery chili classes
| Priority: |
CurrentState: |
AppliesTo: |
Component: |
WaitingFor: |
| Enhancement |
Closed |
Extension |
WysiwygPlugin |
|
JQueryPlugin is now part of the standard Foswiki installation and it comes with the
chili jQuery plugin, which is activated using a set of
classes.
However, a roundtrip-edit through the wysiwyg editor removes those classes.
The
JQueryChili documentation states that the class should be applied to a verbatim block. This is good practice, but the plugin will work on a
pre block, too, and so
HTML2TML should also support these classes for blocks that are not verbatim.
--
MichaelTempest - 11 Jul 2010
To do: add unit tests
--
MichaelTempest - 11 Jul 2010
Also todo:
- Give TMCE the ability to apply these styles
--
MichaelTempest - 18 Jul 2010
Ah - I added a unit test for <verbatim class="tml"> under
Item2254.
And we can now apply these styles via the context menu. Hmmm. It ought to be possible to turn the VERBATIM entry in the format menu into a sub-menu. I must figure out how to do that. Problems:
- The list for formats is a preference and it does not (yet) support nested menus, and
- It is not clear if the editor should extract the list of classes from the preference, or if it should see the TMLverbatim enty in the preference and turn that into a sub-menu, or some other way. The first way looks promising.
--
MichaelTempest - 26 Jul 2010
It isn't possible to add a sub-menu in the format list, because the format list is a listbox and not a menu
I think this needs another control. And the editor should warn if any of the chili-highlighting styles are used but the topic doesn't contain
%JQREQUIRE{chili}%. I am loathe to add chili-highlighting-VERBATIM entries to the format list until there is a way to add
%JQREQUIRE{chili}% easily. I am going to leave this as-is. It might be best to extend the TMCE GUI to do chili-stuff with a plugin.
--
MichaelTempest - 01 Aug 2010