nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

VisualFormat Vs. TinyMCE

FurnaceFace

Okay, so I've done some research on the support site and read the manuals. What I've come up with is a pro/con list for VisualFormat and TinyMCE.

Anything missing? Agree/disagree? I think this list will be useful for people in the future when it comes time to discuss why one should be chosen over another.

Thanks,
/FF

Find more posts tagged with

Comments

nico

How well does the ms word cleanup work on tinymce? It sucks in VF, has been an ongoing headache.

Image 2.png

carnix

In the visualformatconfig.xml file (iw-home/httpd/iw/conf/), do this:



<standard autoclean="true" publish="xhtml" publishviewassource="true" continueparagraph="false">
<style publishstyles="false" href="[eWebEditProPath]/ektnormal.css" equivClass="strict" wrapstylewithdiv="false" preservewordstyles="false" preservewordclasses="false"></style>

Setting the preserv* attributes in the style element to false, and using xhtml pretty much cleans everything right up. We use Office 2003 here, and pasting directly in from Word results in all the office-ish tags and classes being stripped and the formatting being converted to standard HTML. There are other configurations you can do as well, like stripping our tags to remove markup imposed formating (if you're strict about xhtml -- VF isn't)

-mike

FurnaceFace

hmmm guess people haven't had much experience with using both editors...
Well hopefully what I've put up is useful for others in the future..

Thanks for the tip Carnix/mike

/FF

patrickm

Great list, would be nice for you to formalist it into the KB article. I've alot of experience with VF customisations, IMHO that's it's most important selling point. If, as a company, you've invested time into developing reusable components for VF, there really isn't any point in changing to TinyMCE as it's not compatible with VF solutions.

nico

So lame that TinyMCE doesn't have spell check functionality built in. That totally defeats the purpose of not having a local install required solution. Not only that, spell check is an add on that costs additional, thats the final straw I'm going back to VisualFormat.

Adam Stoller

So lame that TinyMCE doesn't have spell check functionality built in. That totally defeats the purpose of not having a local install required solution. Not only that, spell check is an add on that costs additional, thats the final straw I'm going back to VisualFormat.

Hmm - I think of this as one of the better reasons to use a Mac (though I suppose there might be something similar for Windows too) - It doesn't matter what application I use, I get dynamic spell checking all the time ...
(Enter Nipper stage left, to add his $0.02 regarding my use of a Mac :-)

nipper

(Enter Nipper stage left, to add his $0.02 regarding my use of a Mac :-)

No I was not planning to say anything, my kids love the mac. Smiley Very Happy

carnix

Kids always love the Mac -- they don't know any better Smiley Tongue

Firefox has a spell checking extension that works on all forms. There are free spell checkers out there in open source land for web-forms -- designed for the multiudes of WYSIWYG editors used in the various CMS products (Mambo, Drupal, PHP- and PostNuke, Typo3 etc). Not that's I'm saying those are any good (they are and they aren't, it depends on the needs of the site), but only that they are all freeware, and all have WYSIWYG editors that plug-into textareas are fairly functional and some even have spell checking capability.

I tried to integrate one that was cross-browser compatible (important because my TeamSite userbase is split between IE and FireFox users -- and I already had to hack FormsPublisher to make it even display in FF 2 (v. 6.7.1). I couldn't figure it out, but this was back in TS 5.5, so maybe it's easier now.

Interwoven should implement a cross-browser WYSIWYG solution -- they are cross-platform in everything else and all their other plugin solutions are in Java (the various instantiations of LaunchPad, I mean). Seems reasonable they would use a Java based solution for WYSIWYG if they don't want to build it in ECMAScript (which they should) -- I never understood the Ektron thing.

-mike

carnix

So, after reading and posting to this thread I took the comparison paper mentioned above, and with it in mind, implemented a side by side test of these two editors for our web content crew here to get their feedback.

Universally, no one here used the spell check within TeamSite, everyone edited in MS Word and then pasted into TeamSite. So the spell check rationale for VF was mute right away. (Besides, we mandate FireFox for all web development staff as the default browser, and it has a build-in spell check for text areas anyway).

I found that TinyMCE handles the MS Word character to HTML Entity conversion just fine when directly pasting in from Word (we use 2003 here), so those left and right quotes, the apostrophes, mdashes, all those are handled fine, and without all of the really bad additional mess.

So, after doing side by side testing, the result was a unanimous approval to move from VF to TinyMCE, so that's what we've done! I heavily modified the toolbar line, since most of those tools weren't necessary for our users. I left only basic bold/underline/italic, along with lists, the html source button and just a couple others. When people are using Word, its doesn't matter anyway, and more advanced components are built by our web developer staff instead, and placed in page content boxes via widgets rather than placing raw HTML in the WYSIWYG editor boxes... so TinyMCE has actually emerged as the unlikely winner in CARE's little Battle of the WYSIWYG Editors.

In addition, I did some work yesterday on fixing those conversions using the FormAPI and have found some success, I'll post it here... I would LOVE to hear people's suggestions for improvement, this is only a first crack, but it seems to be working fairly well (note, these are connected to fields that do NOT have TinyMCE attached to them, this actually broke when I tried to do that, and its not really necessary for fields using TinyMCE anyway):


function init(){
//These are metadata fields that should only be in plain text, and cannot contain double quote characters.
 IWEventRegistry.addItemHandler("/Meta Data/Values/meta_description", "onItemChange", FilterToText);
 IWEventRegistry.addItemHandler("/Meta Data/Values/meta_title", "onItemChange", FilterToText);
 IWEventRegistry.addItemHandler("/Meta Data/Values/meta_primary_keyword", "onItemChange", FilterToText);
 IWEventRegistry.addItemHandler("/Meta Data/Values/meta_secondary_keyword", "onItemChange", FilterToText);
 IWEventRegistry.addItemHandler("/Meta Data/Values/meta_tertiary_keyword", "onItemChange", FilterToText);
 IWEventRegistry.addItemHandler("/Meta Data/Values/meta_additional_keywords", "onItemChange", FilterToText);


//These are web content fields that should have 'risky' characters converted to HTML entities.
 IWEventRegistry.addItemHandler("/Header Information/Headline", "onItemChange", FilterToHTML);
 IWEventRegistry.addItemHandler("/Header Information/Sub-Headline", "onItemChange", FilterToHTML);
 IWEventRegistry.addItemHandler("/Header Information/Image Credit", "onItemChange", FilterToHTML);
 IWEventRegistry.addItemHandler("/Header Information/Image Caption", "onItemChange", FilterToHTML);

}

/*

 The following two functions are really heavy handed.  I had some problems
 witting them in OO ways, something about the FormAPI seemed to interfere
 when I started using encapsulation.  Perhaps because everything in here is
 already encapsulated in some other way, who knows.  Doesn't matter this works
 just as well.

 Since, in general, these two functions perform identical tasks, just the
 replacement string varies, it might be better to use a single function with
 some sort of toggle mechanism to determine whether to use plain text or entity
 conversion.

 Also, an easier way to maintain a list of risky characters to convert (well, their
 Unicode notations anyway) and their entity/plain text conversions would be really
 appropriate.  In the long run expanding this to include non-English characters is
 an absolute goal for this tool.

*/


function FilterToText(ThisItem){
 InputString = ThisItem.getValue();

  var objRegex = new RegExp('\u2019', "g"); //MS Word aposterphe
  InputString = InputString.replace(objRegex, "'");

  objRegex = new RegExp('\u2014', "g"); //MS Word long dash
  InputString = InputString.replace(objRegex, "--");

  objRegex = new RegExp('\u2013', "g"); //MS Word short dash
  InputString = InputString.replace(objRegex, "-");

  objRegex = new RegExp('\u201C', "g");//MS Word left double quote
  InputString = InputString.replace(objRegex, "''");

  objRegex = new RegExp('\u201D', "g");//MS Word right double quote
  InputString = InputString.replace(objRegex, "''");

  objRegex = new RegExp('\u00A9', "g");//Copyright symbol
  InputString = InputString.replace(objRegex, "(c)");

  objRegex = new RegExp('\u00AE', "g");//Registered trademark symbol
  InputString = InputString.replace(objRegex, "(r)");

 ThisItem.setValue(InputString);
}

function FilterToHTML(ThisItem){
 InputString = ThisItem.getValue();

  var objRegex = new RegExp('\u00A9', "g");
  InputString = InputString.replace(objRegex, "&copy;");

  objRegex = new RegExp('\u00AE', "g");
  InputString = InputString.replace(objRegex, "&reg;");

  objRegex = new RegExp('\u2013', "g");
  InputString = InputString.replace(objRegex, "&ndash;");

  objRegex = new RegExp('\u2014', "g");
  InputString = InputString.replace(objRegex, "&mdash;");

  objRegex = new RegExp('\u2019', "g");
  InputString = InputString.replace(objRegex, "&rsquo;");

  objRegex = new RegExp('\u201C', "g");
  InputString = InputString.replace(objRegex, "&ldquo;");

  objRegex = new RegExp('\u201D', "g");
  InputString = InputString.replace(objRegex, "&rdquo;");

 ThisItem.setValue(InputString);
}

IWEventRegistry.addFormHandler("onFormInit", init);

Adam Stoller

So, after reading and posting to this thread I took the comparison paper mentioned above, and with it in mind, implemented a side by side test of these two editors for our web content crew here to get their feedback.

Universally, no one here used the spell check within TeamSite, everyone edited in MS Word and then pasted into TeamSite. So the spell check rationale for VF was mute right away. (Besides, we mandate FireFox for all web development staff as the default browser, and it has a build-in spell check for text areas anyway).

I found that TinyMCE handles the MS Word character to HTML Entity conversion just fine when directly pasting in from Word (we use 2003 here), so those left and right quotes, the apostrophes, mdashes, all those are handled fine, and without all of the really bad additional mess.

So, after doing side by side testing, the result was a unanimous approval to move from VF to TinyMCE, so that's what we've done! I heavily modified the toolbar line, since most of those tools weren't necessary for our users. I left only basic bold/underline/italic, along with lists, the html source button and just a couple others. When people are using Word, its doesn't matter anyway, and more advanced components are built by our web developer staff instead, and placed in page content boxes via widgets rather than placing raw HTML in the WYSIWYG editor boxes... so TinyMCE has actually emerged as the unlikely winner in CARE's little Battle of the WYSIWYG Editors.

In addition, I did some work yesterday on fixing those conversions using the FormAPI and have found some success, I'll post it here... I would LOVE to hear people's suggestions for improvement, this is only a first crack, but it seems to be working fairly well (note, these are connected to fields that do NOT have TinyMCE attached to them, this actually broke when I tried to do that, and its not really necessary for fields using TinyMCE anyway):
function init(){
//These are metadata fields that should only be in plain text, and cannot contain double quote characters.
 IWEventRegistry.addItemHandler("/Meta Data/Values/meta_description", "onItemChange", FilterToText);
 IWEventRegistry.addItemHandler("/Meta Data/Values/meta_title", "onItemChange", FilterToText);
 IWEventRegistry.addItemHandler("/Meta Data/Values/meta_primary_keyword", "onItemChange", FilterToText);
 IWEventRegistry.addItemHandler("/Meta Data/Values/meta_secondary_keyword", "onItemChange", FilterToText);
 IWEventRegistry.addItemHandler("/Meta Data/Values/meta_tertiary_keyword", "onItemChange", FilterToText);
 IWEventRegistry.addItemHandler("/Meta Data/Values/meta_additional_keywords", "onItemChange", FilterToText);


//These are web content fields that should have 'risky' characters converted to HTML entities.
 IWEventRegistry.addItemHandler("/Header Information/Headline", "onItemChange", FilterToHTML);
 IWEventRegistry.addItemHandler("/Header Information/Sub-Headline", "onItemChange", FilterToHTML);
 IWEventRegistry.addItemHandler("/Header Information/Image Credit", "onItemChange", FilterToHTML);
 IWEventRegistry.addItemHandler("/Header Information/Image Caption", "onItemChange", FilterToHTML);

}

/*

 The following two functions are really heavy handed.  I had some problems
 witting them in OO ways, something about the FormAPI seemed to interfere
 when I started using encapsulation.  Perhaps because everything in here is
 already encapsulated in some other way, who knows.  Doesn't matter this works
 just as well.

 Since, in general, these two functions perform identical tasks, just the
 replacement string varies, it might be better to use a single function with
 some sort of toggle mechanism to determine whether to use plain text or entity
 conversion.

 Also, an easier way to maintain a list of risky characters to convert (well, their
 Unicode notations anyway) and their entity/plain text conversions would be really
 appropriate.  In the long run expanding this to include non-English characters is
 an absolute goal for this tool.

*/


function FilterToText(ThisItem){
 InputString = ThisItem.getValue();

  var objRegex = new RegExp('\u2019', "g"); //MS Word aposterphe
  InputString = InputString.replace(objRegex, "'");

  objRegex = new RegExp('\u2014', "g"); //MS Word long dash
  InputString = InputString.replace(objRegex, "--");

  objRegex = new RegExp('\u2013', "g"); //MS Word short dash
  InputString = InputString.replace(objRegex, "-");

  objRegex = new RegExp('\u201C', "g");//MS Word left double quote
  InputString = InputString.replace(objRegex, "''");

  objRegex = new RegExp('\u201D', "g");//MS Word right double quote
  InputString = InputString.replace(objRegex, "''");

  objRegex = new RegExp('\u00A9', "g");//Copyright symbol
  InputString = InputString.replace(objRegex, "(c)");

  objRegex = new RegExp('\u00AE', "g");//Registered trademark symbol
  InputString = InputString.replace(objRegex, "(r)");

 ThisItem.setValue(InputString);
}

function FilterToHTML(ThisItem){
 InputString = ThisItem.getValue();

  var objRegex = new RegExp('\u00A9', "g");
  InputString = InputString.replace(objRegex, "&copy;");

  objRegex = new RegExp('\u00AE', "g");
  InputString = InputString.replace(objRegex, "&reg;");

  objRegex = new RegExp('\u2013', "g");
  InputString = InputString.replace(objRegex, "&ndash;");

  objRegex = new RegExp('\u2014', "g");
  InputString = InputString.replace(objRegex, "&mdash;");

  objRegex = new RegExp('\u2019', "g");
  InputString = InputString.replace(objRegex, "&rsquo;");

  objRegex = new RegExp('\u201C', "g");
  InputString = InputString.replace(objRegex, "&ldquo;");

  objRegex = new RegExp('\u201D', "g");
  InputString = InputString.replace(objRegex, "&rdquo;");

 ThisItem.setValue(InputString);
}

IWEventRegistry.addFormHandler("onFormInit", init);

While there is likely some syntactic issue with the following (i.e.: completely untested) - I believe you could use something like this:[html]var map = new Array();
map['\u2019'] = new Array("'", "’");
map['\u2014'] = new Array("--", "—");
map['\u2013'] = new Array("-", "–");
map['\u201C'] = new Array("''", "“");
map['\u201D'] = new Array("''", "”");
map['\u00A9'] = new Array("(c)", "©");
map['\u00AE'] = new Array("(r)", "®");

function FilterToText(ThisItem){
InputString = ThisItem.getValue();
for (i = 0; i < map.length; i++) {
InputString = InputString.replace(/map/g, map[0]);
}
ThisItem.setValue(InputString);
}

function FilterToHTML(ThisItem){
InputString = ThisItem.getValue();
for (i = 0; i < map.length; i++) {
InputString = InputString.replace(/map/g, map[1]);
}
ThisItem.setValue(InputString);
}[/html]and then extend the map as you need to without having to modify the functions.

CrosstabAlternatingRowHighlight.rptdesign

carnix

Yes, that's much better. I thought of that but the array syntax didn't pop in my head and I had other things to do Smiley Happy

The only trick is... what happens if I want to expand it for more characters. I mean, I'd like to extend this for use with Spanish and French (at least) if not also German language characters. We don't have just a huge amount of call for that, but particularly with names of people, we have ran into the issue before.

Hard coding a new Array object for every character is fine for a few (such as it is now), but when you get into the hundreds the overhead could cause some problems... or maybe not, I won't know till I give it a go, I guess. This is a really good start though, thanks so much! You know, it really amazes me someone hasn't already worked up a good solution to this, I mean, isn't Word encoding a problem for other people too? Seems like it would be...

carnix

Ok, after some tinkering with it, this is what I got to function within the FormAPI. It didn't like having any code outside of functions (again, I think this is probably because everything in the use script gets evaluated as methods within a larger javascript class, I haven't really dig into it, and probably won't...... but that seems the most likely explanation anyway) and oddly I couldn't get the Perlish slash syntax to work at all when assigning the actual regex. Strange, but the JavaScript object syntax works fine.

I have some other things to do now, so I'm going to put off testing performance when you have a large set of items to check for (Spanish characters for example). When I do, I'll post results here.


function GetMap(){
 var Map = new Array();
   Map[0] = new Array('\u2019',"'","’");   //Word aposterphe
   Map[1] = new Array('\u2014',"--","—");  //Word long dash
   Map[2] = new Array('\u2013',"-","–");   //Word short dash
   Map[3] = new Array('\u201C',"''","“");  //Word left double quote
   Map[4] = new Array('\u201D',"''","”");  //Word right double quote
   Map[5] = new Array('\u00A9',"(c)","©");  //Copyright
   Map[6] = new Array('\u00AE',"(r)","®");   //Registered Trademark
   Map[7] = new Array('\u2026',"...","…"); //Word Ellipsis 
 return Map;
}

function FilterToText(ThisItem){
 var CharMap = GetMap();
 InputString = ThisItem.getValue();
 for (var i = 0; i < CharMap.length; i++){
  var objRegex = new RegExp(CharMap[0], "g")
  InputString = InputString.replace(objRegex,CharMap[1]);
 }
 ThisItem.setValue(InputString);
}

function FilterToHTML(ThisItem){
 var CharMap = GetMap();
 InputString = ThisItem.getValue();
 for (var i = 0; i < CharMap.length; i++){
  var objRegex = new RegExp(CharMap[0], "g")
  InputString = InputString.replace(objRegex,CharMap[2]);
 }
 ThisItem.setValue(InputString);
}

thereIsNoSpoon

...Besides, we mandate FireFox for all web development staff as the default browser

Wow - Lucky you - The organization I work for mandates IE and always will because the upper management for the IT group doesn't quite realize how out of touch IE is with web standards. Smiley Wink

Let's put it this way, I suspect that the upper management would probably vote in favor of OOXML becoming a standard if given the chance.

That being said, good info Carnix/Ghoti - I will take advantage of this fine work.

carnix

I mandated FireFox for the Web Team. The standard for the organization is IE of course. Pffft. Smiley Happy

Anyway, ok, so I added a whole pile of new characters to the array, ran some functional tests and it didn't seem to drag much at all. Here it is. I'm thinking about posting this as a KB, but I've never done that before, so I'm not really sure of the protocols... Think that would be a good/useful idea?

function GetMap(){
/* used http://www.digitalmediaminute.com/reference/entity/index.php as reference */
 var Map = new Array();
   Map[0]  = new Array('\u2019',"'","&rsquo;");
   Map[1]  = new Array('\u2014',"--","&mdash;");
   Map[2]  = new Array('\u2013',"-","&ndash;");
   Map[3]  = new Array('\u201C',"''","&ldquo;");
   Map[4]  = new Array('\u201D',"''","&rdquo;");
   Map[5]  = new Array('\u00A9',"(c)","&copy;");
   Map[6]  = new Array('\u00AE',"(r)","&reg;");
   Map[7]  = new Array('\u2026',"...","&hellip;");
   Map[8]  = new Array('\u00A1',"","&iexcl;");
   Map[9]  = new Array('\u00B0'," degrees","&deg;");
   Map[10] = new Array('\u00BF',"","&iquest;")
   Map[11] = new Array('\u00A1',"","&iexcl;")
   Map[12] = new Array('\u00C0',"A","&Agrave;");
   Map[13] = new Array('\u00C1',"A","&Aacute;");
   Map[14] = new Array('\u00C2',"A","&Acirc;");
   Map[15] = new Array('\u00C3',"A","&Atilde;");
   Map[16] = new Array('\u00C4',"A","&Auml;");
   Map[17] = new Array('\u00C5',"A","&Aring;");
   Map[18] = new Array('\u00C7',"C","&Ccedil;");
   Map[19] = new Array('\u00C8',"E","&Egrave;");
   Map[20] = new Array('\u00CA',"E","&Ecirc;");
   Map[21] = new Array('\u00CB',"E","&Euml;");
   Map[22] = new Array('\u00CC',"I","&Igrave;");
   Map[23] = new Array('\u00CD',"I","&Iacute;");
   Map[24] = new Array('\u00CE',"I","&Icirc;");
   Map[25] = new Array('\u00CF',"I","&Iuml;");
   Map[26] = new Array('\u00D0',"D","&ETH;");
   Map[27] = new Array('\u00D1',"N","&Ntilde;");
   Map[28] = new Array('\u00D2',"O","&Ograve;");
   Map[29] = new Array('\u00D3',"O","&Oacute;");
   Map[30] = new Array('\u00D4',"O","&Ocirc;");
   Map[31] = new Array('\u00D5',"O","&Otilde;");
   Map[32] = new Array('\u00D6',"O","&Ouml;");
   Map[33] = new Array('\u00D8',"O","&Oslash;");
   Map[34] = new Array('\u00D9',"U","&Ugrave;");
   Map[35] = new Array('\u00DA',"U","&Uacute;");
   Map[36] = new Array('\u00DB',"U","&Ucirc;");
   Map[37] = new Array('\u00DC',"U","&Uuml;");
   Map[38] = new Array('\u00DD',"Y","&Yacute;");
   Map[39] = new Array('\u00DF',"B","&szlig;");
   Map[40] = new Array('\u00E0',"a","&agrave;");
   Map[41] = new Array('\u00E1',"a","&aacute;");
   Map[42] = new Array('\u00E2',"a","&acirc;");
   Map[43] = new Array('\u00E3',"a","&atilde;");
   Map[44] = new Array('\u00E4',"a","&auml;");
   Map[45] = new Array('\u00E5',"a","&aring;");
   Map[46] = new Array('\u00E7',"c","&ccedil;");
   Map[47] = new Array('\u00E8',"e","&egrave;");
   Map[48] = new Array('\u00E9',"e","&eacute;");
   Map[49] = new Array('\u00EA',"e","&ecirc;");
   Map[50] = new Array('\u00EB',"e","&euml;");
   Map[51] = new Array('\u00EC',"i","&igrave;");
   Map[52] = new Array('\u00ED',"i","&iacute;");
   Map[53] = new Array('\u00EE',"i","&icirc;");
   Map[54] = new Array('\u00EF',"i","&iuml;");
   Map[55] = new Array('\u00F0',"o","&eth;");
   Map[56] = new Array('\u00F1',"n","&ntilde;");
   Map[57] = new Array('\u00F2',"o","&ograve;");
   Map[58] = new Array('\u00F3',"o","&oacute;");
   Map[59] = new Array('\u00F4',"o","&ocirc;");
   Map[60] = new Array('\u00F5',"o","&otilde;");
   Map[61] = new Array('\u00F6',"o","&ouml;");
   Map[62] = new Array('\u00F8',"o","&oslash;");
   Map[63] = new Array('\u00F9',"u","&ugrave;");
   Map[64] = new Array('\u00FA',"u","&uacute;");
   Map[65] = new Array('\u00FB',"u","&ucirc;");
   Map[66] = new Array('\u00FC',"u","&uuml;");
   Map[67] = new Array('\u00FD',"y","&yacute;");
   Map[68] = new Array('\u00FF',"y","&yuml;");
 return Map;
}

function FilterToText(ThisItem){
 var CharMap = GetMap();
 InputString = ThisItem.getValue();
 for (var i = 0; i < CharMap.length; i++){
  var objRegex = new RegExp(CharMap[0], "g");
  InputString = InputString.replace(objRegex,CharMap[1]);
 }
 ThisItem.setValue(InputString);
}

function FilterToHTML(ThisItem){
 var CharMap = GetMap();
 InputString = ThisItem.getValue();
 for (var i = 0; i < CharMap.length; i++){
  var objRegex = new RegExp(CharMap[0], "g");
  InputString = InputString.replace(objRegex,CharMap[2]);
 }
 ThisItem.setValue(InputString);
}

nipper

I mandated FireFox for the Web Team. The standard for the organization is IE of course. Pffft.

Anyway, ok, so I added a whole pile of new characters to the array, ran some functional tests and it didn't seem to drag much at all. Here it is. I'm thinking about posting this as a KB, but I've never done that before, so I'm not really sure of the protocols... Think that would be a good/useful idea?

Yes that would be a good idea. Put one together and email it to Will Anglin, there is a thread in the suggestion box on this topic.

carnix

I submitted it via the website, but couldn't submit the code as an attachment, so I had to convert the & into & instead... hope that doesn't screw anyone up Smiley Happy

(Had to do the same thing to post the code here too, so probably it'll be ok).

GRD

I like TinyMCE primarily because of the small footprint, however, there are two nasty bugs that have been confirmed by IWOV support and may influence your decision to implement TinyMCE in your solution. System is TeamSite 6.7.1 on Windows, however, I suspect all platforms will behave the same.

I see nothing about these in the latest patches, as of patch #1825.

1) TinyMCE cannot insert anchor tag links in IE6/IE7.

When inserting a hyperlink to an anchor tag in TinyMCE, e.g. "#apple", the resulting href "#apple" is replaced with "/iw-cc/command/".

2) TinyMCE Editor does not support setValue() method

The TinyMCE editor does not support the setValue() FormAPI method, but instead returns a Javascript error, "Error: 'editor_id' is undefined."

-Greg

carnix

Yes indeed, I've noted both those bugs as well. We generally don't use anchors like that, so that isn't an issue. It is a darn shame about the setValue formAPI function not working however. The script above works great everywhere except textareas where TinyMCE is enabled.

The workaround I've been toying with is to have another small textarea field inside the DCT with the "FilterToHTML" version enabled. Then, our editors first paste their MS Word content into that field, click out of it (to engage the filter) then click back in it, CTRL-A, CTRL-C and then CTRL-V into the TinyMCE field. Since we're not using any other FormAPI tricks for that particular field, this works ok. Not optimal, but what can you do, it's TeamSite Smiley Happy

-mike

test.xml

Test.rptdesign

XML DS error.jpg

scandorph

Both those bugs are fixed in SP1.

FurnaceFace

Scandorph,

Do you eat TinyMCE for breakfast everyday? Smiley Wink

Thanks for ALL the replies on the posts. Good to know that things are being addressed. I had opened a ticket with IW about 5 months ago and they told me that they had no intention of updating TinyMCE for SP1 so the decision was made to go with Visual Format as TinyMCE had too many issues with it.

I liked it but based on that information, we decided to go with VF as it was mature and fairly stable.

Sounds like they did do a lot for TinyMCE in SP1 - maybe I can use it for future implementations.

Thanks again,
/FF

Untitled.png

Hans

Anyway, ok, so I added a whole pile of new characters to the array, ran some functional tests and it didn't seem to drag much at all. Here it is...

The script looks great, thanks for posting. But (naturally) there's something I'm not getting - for special chars e.g. copyright, N-dash etc. you need entities to ensure consistent browser display, but why bother for basic accented characters? Shouldn't they display properly if correct charset is specified in document??

We are using a script that cleans up input to 3 different levels depending on which onItemChange function specified,
- text only
- text + inline html only
- text + generic html (xhtml 1.0 transitional)

Also standardizes some typographic stuff and cleans up garbage Word code where VF left off.

Same basic script attached, use JS for DCTs or Perl module for TPLs or workflows.

Hans

Janeh

We have use VF as Tiny MCE does not offer Section 508 settings for accessible tables. - or does anyone know any different.

Captain_Moor

Okay, so I've done some research on the support site and read the manuals. What I've come up with is a pro/con list for VisualFormat and TinyMCE.

Anything missing? Agree/disagree? I think this list will be useful for people in the future when it comes time to discuss why one should be chosen over another.

Thanks,
/FF

Hey thanks, its always nice to read someone elses impression of applications such as these.

Good Work!!