> On Feb 12, 2017, at 9:21 AM, Alain Couthures
> wrote:
>
> Thank you very much for all these explanations!
>
> The proposed patch will be integrated in rev. 640.
Thank you! You should have a pull request in your queue for
xphoneforms at github, which may (or may not) simplify the
change.
>
Thank you very much for all these explanations!
The proposed patch will be integrated in rev. 640.
I have been able to build my own test form (I first forgot to add the
custom button names in "toolbar" and I had to replace the 2 "<"
with "<" in the "insertElem" function).
--Alain
Le 2/7/20
Thank you, Michael. You've done us a great service by documenting this in
an exemplary fashion. The metadata department at my library is currently
planning a markup project for which this should come in quite handy. I look
forward to making use of your work.
Tim
--
Tim A. Thompson
Metadata Librar
> On Feb 6, 2017, at 8:04 PM, Conal Tuohy wrote:
>
> I noticed this para seemed odd:
> https://en.wikibooks.org/w/index.php?title=XSLTForms/TinyMCE&action=edit§ion=14
>
> XSLTForms 638 supports both version 3 and version 4 of TinyMCE; the minimal
> example of TinyMCE given on the AgenceXML we
I noticed this para seemed odd:
https://en.wikibooks.org/w/index.php?title=XSLTForms/TinyMCE&action=edit§ion=14
XSLTForms 638 supports both version 3 and version 4 of TinyMCE; the minimal
> example of TinyMCE given on the AgenceXML web site uses XSLTForms 4.0.28.
Did you mean, at the end of that
I’ve written down what I think I have learned in the last few days
about using TinyMCE from XSLTForms, in the XSLTForms wikibook:
https://en.wikibooks.org/wiki/XSLTForms/TinyMCE
If any readers find errors there, please fix them or tell me so I can
fix them.
The section on custom buttons may ex
