I got an enhancement request from a user if it’s was possible to validate if the tinyMCE control had some text.
Because validation is implemented as a core property on XPage Controls this was a quick fix.
One Tip i can give when creating your own custom controls is when binding computed properties, set the property how the compositeData property should bind to compute at page load, if the data shouldn’t update.
Some properties of controls require this. I don’t know if this is a bug or if it’s this is meant to work like this. 😉
I also built an XPage using the Form Table control to display how the validation looks like.
Check out the new version of the Tiny Mce custom control –> openntf project page
Version 1.1 of the TinyMce custom control for XPages is released today.
This version contains a fix so the 64K limit is now fixed and also a new option
TinyMcePath is added to be able to add a url that is server wide. And to simplify upgrade of the editor.
Url to the control at openntf.org
I have created a Tinymce integration custom control for XPages.
Why is this a good thing?
Well this means that you can edit richtext in XPages both on the web, the Notes Client and it works with IPhone,IPad with IOS5.
You do not need to rely on when a new version of Domino is released. New versions of Tinymce is released more often than Domino releases.
It has alot of features that the Domino RT editor don’t. The custom control is lacking one thing in this version but I believe that this can be done in the future and that is image upload support. Another thing that is giving me a headache is Backend Richtext support and this 64K. If I add html using Richtextitem.appendtext the help states that it will automatically add a paragraphs if the content is larger than 35K. What happends it cuts the appended text at 64K 🙁
2011 and we have restrictions in Domino that is from 1995, Please IBM build a RichText version 2 and it don’t have to be compatible with version 1 so we can drop all these restrictions.
It’s released here at openntf.org