Xml form HTML Editor control change.

Question

Hi,
Is it possible to change External weblink control property of HTML Editor used in xml form builder.?
As of now this control gives 2 options to provide external weblink (1.Open in active window ,2.open in new window).I want to add open in same window as top.
Can anyone give some useful information ?
Thanks and Regards,
Jack.
Note: Points will be awarded for useful answers.

Answer 1

Hi jack men,
If you are still interested in a solution to your problem...
We just hit upon the same problem. I found out that XMLForms reference htmledit4.js in their <XMLForm-Name>Edit.xsl, so you have to adapt that one.
I saved htmledit4.js and renamed it to htmledit5.js so that I can change the HTMLEditor settings only for my XMLForm (and not for e.g. SAPNewsForm).
I changed the entry in my XML-Form Editor settings XSL to reference the new JavaScript file:
[code]<xsl:value-of select="$xmlformsroot"/>/htmledit/htmledit5.js</xsl:if>[/code]
Then I copied the method body of htmledit3.js (the standard htmleditor JavaScript file) to htmledit5.js and adapted it to just show the two tragets of <i>self</i> and <i>top</i>.
The method to display link properties is: <b>htmlb_hed_makeWebLinkDialog</b>
Find this method in both files. Then find in htmledit3.js the beginning of the target window selection-box:
[code]sSizerHtml += "<SELECT id=htmlb_hed_link_launch_mode class=\"urDdlWhlSml\">";[/code]
the following lines of code determine the selectable values.
You will notice that htmledit4.js misses a few entries. Just copy all or the ones you need.
For your convenience I show my code here:
[code]  sSizerHtml += "<td>";
  sSizerHtml += "<span style=\"font-size:1em;\">";
  sSizerHtml += "<SELECT id=htmlb_hed_link_launch_mode class=\"urDdlWhlSml\">";
//-- target=_blank
  sSizerHtml += "<OPTION value=\"_blank\" ";
  if(modOpenMode==1) sSizerHtml += "selected";
  sSizerHtml += ">";
  sSizerHtml += txtMap["TXT_HTMLB_HED_BLANK"]; 
  sSizerHtml += "</OPTION>";
//-- target=_parent --
  sSizerHtml += "<OPTION value=\"_parent\" ";
  if(modOpenMode==2) sSizerHtml += "selected";
  sSizerHtml += ">";
  sSizerHtml += txtMap["TXT_HTMLB_HED_PARENT"]; 
  sSizerHtml += "</OPTION>";
//-- target=_search--
  sSizerHtml += "<OPTION value=\"_search\" ";
  if(modOpenMode==3) sSizerHtml += "selected";
  sSizerHtml += ">";
  sSizerHtml += txtMap["TXT_HTMLB_HED_SEARCH"]; 
  sSizerHtml += "</OPTION>"; 
//--target=_self
  sSizerHtml += "<OPTION value=\"_self\" ";
  if(modOpenMode==4) sSizerHtml += "selected";
  sSizerHtml += ">";
  sSizerHtml += txtMap["TXT_HTMLB_HED_SELF"]; 
  sSizerHtml += "</OPTION>";
//-- target=_top
  sSizerHtml += "<OPTION value=\"_top\" ";
  if(modOpenMode==5) sSizerHtml += "selected";
  sSizerHtml += ">";
  sSizerHtml += txtMap["TXT_HTMLB_HED_TOP"]; 
  sSizerHtml += "</OPTION></SELECT></span>";
  sSizerHtml += "</td>";
  sSizerHtml += "</tr>";[/code]
I didn't check yet if a new generation of the XMLForms Project in the XMLFormsBuilder overwrites the changes in the XMLFormsEdit.xsl, however I guess so. A better way would be to adjust the JavaScript reference in some other configuration file that I haven't found yet, until then just adapt the XSL everytime...
If Carsten Buechert contacted you regarding the exchange of the whole control, I would be interested myself as well.
Cheers
Kilian