eop.setParam("java_arguments", "-Dsun.java2d.d3d=false");

Make sure to change the name of editor object as appropriate for your integration. This call needs to occur before the "loadEditor()" method is called to have any effect.

There are no known side-effects to setting this parameter in Java versions before 7.

For more information about the new "Mixed Code Verification" feature please visit the Java website at:http://java.sun.com/javase/6/docs/technotes/guides/jweb/mixed_code.html.

This error (see screenshot above) only appears in conjunction with signed applets on systems with Windows Vista where onlince certificate validation is enabled. To solve this issue, you should disable this option. To do so, open the Java Control Panel, and go to Adanced / Security and make sure the checkbox next to "Enable online certificate validation" is not checked (see screenshot below).

Note: this option can be safely enabled on non-Vista systems. Furthermore, this option is turned off by default in most Java installations.

1. First of all, we recommend you clearing the cache of your proxy server (if any), of your browser as well as of the Java VM.

2. Additionally, you could use the "preloadJVM" function in order to improve the editors loading time. This function preloads the JavaVM in a page before the page containing the applet is loaded. Thus, loading the applet the first time should already be significantly faster. You can find a sample implementation in our samples index page. Please take look at the source code, it is also included in the installation package.

For more information about the "preloadJVM" function please review the Integration Manual Chapter 3.2 JavaScript API.

3. An other possibility to speed up the edit-on Pro loading process is to minimize the HTTP Connections required. Therefore please take a look at the "Minimize HTTP Connections" sample which resides in the /samples/minimizehttp directory. This sample demonstrates how to reduce the amount of HTTP requests during the loading of the applet.

• Paste: Inserts the content of the clipboard in HTML format including style information.
   
• Paste With Filter: Inserts the content of the clipboard in HTML format without styles.
   
• Paste Plain Text: Inserts the content of the clipboard without any formatting or styles.
   
• Paste With Style Sheets: Inserts the content of the clipboard in HTML format with styles contained in an embedded style sheet. Imported styles will be merged with existing style sheets.

You can configure the "Paste Special" dialog within the config.xml file by setting the prompt attribute of "true". If set to true, the "Paste Special" dialog will be opened and present the selection of the paste types whenever content is pasted from MS Word.

Of course, it is possible to specify a PASTE action which will be selected by default.

1. In order to adjust the keyboard shortcut (Strg+ V), which executes the PASTE action by default, please specify the following setting within your uiconfig.xml file, e.g.:

<uiconfig>
    <actions>
        <action id="PASTEPLAINTEXT">
            <shortcut id="control V"/>
        </action>
    </actions>
...
</uiconfig>

For more information please review the edit-in Pro Integration Manual at "Shortcut"

2. In order to adjust the drag and drop option, please use this setting, e.g.:

<uiconfig>
    <actions>       
        <dragndropaction actionid="DRAGNDROPPLAINTEXT" />
        <action id="PASTEPLAINTEXT">
            <shortcut id="control V"/>
        </action>
    </actions>
...
</uiconfig>

3. In order to adjust the "Paste" button within the editors toolbar, please change the following setting accordingly, e.g.:

<uiconfig>
...
    <toolbar collapse="false">
        <button actionid="PASTEPLAINTEXT" />
...
</uiconfig>

JSP code in comments:

<!-- <%= myVariable %> -->

JSP in a CDATA section:

<![CDATA[<%= myVariable %>]]>

In both of these examples, the JSP code represented will be executed correctly. The only drawback to this is that any code that should be displayed in the browser will not be displayed, as the output of those JSP scripts will still remain in comments, e.g. the first script would evaluate to

<!-- the value of the variable myVariable -->

whereas the second would evaluate to

<![CDATA[ the value of the variable myVariable ]]>

Content edited with edit-on Pro would have to be preprocessed and postprocessed if the comments or CDATA sections are not acceptable.

...

eop.setStandAloneHeight("600");

eop.setStandAloneWidth("400");

...

The unit of the values is px.

For more information please review the edit-on Pro Integration Manual.

For more information please review the edit-on Pro Integration Manual.

Depending on the operating system of your client machine, there are different possibilities in order to solve this problem:

• Windows:
  The only solution currently known to us is to deinstall Abdlock.
• Linux:
  After activating the "Obj-Tabs" of Adblock, edit-on Pro should work properly.

<config>

   <advanceddialog enabled="false" />

...

</config>

You will find more information in the edit-on Pro Integration Manual.

First possibility:

• When loading a document that contains unknown XML tags the editor switches to source view and opens a prompt which describes warnings and errors within the document (including the unknown XML tags)
  
• It is not possible to switch to WYSIWYG view until the user corrects the errors and removes the unknown XML tags.

For introducing this editor behavior you have to set following definitions into your config.xml file used:

<cleanupprocess cleanuponload="auto" cleanuponsave="auto" dropillegaltags="false" />

<documentvalidation enabled="true" validateonsave="false"  overridedoctype="true" />

Second possibility:

• When loading a document that contains unknown XML tags these unknown tags will be ignored from the CleanUp process and the document validation. This means the tags stay within the source code and the document becomes rendered in WYSIWYG view.
  
• For displaying the unknown tags in WYSIWYG view you should enable the P mode within your toolbar.
  
• Using this method it's not possible to validate documents against a DTD.

For introducing this editor behavior you have to set following definitions into your config.xml file used:

<cleanupprocess cleanuponload="auto" cleanuponsave="auto" dropillegaltags="false" />

<documentvalidation enabled="false" validateonsave="false"  overridedoctype="true" />

Before you start to update, make sure to have made a backup copy of the ./eopro directory of your current installation.

In order to update your installation, we recommend you to overwrite all old files.

It is especially important that all contents of the ./eopro directory (including sub folders) and the main editor resources which are "edit-on-pro-5.jar" and "editonpro.js" are overwritten with the according files/directories of the new release package.

To fully benefit from the new features and improvements of the latest release version of edit-on Pro, it might be necessary that you modify your existing config.xml, uiconfig.xml or JavaScript integration code.

For more information on the availability of new features and configurations, please review the Release Notes (readme.txt) and the Integration Manual.

Some configuration settings and APIs might be deprecated now. Although they still exist in the latest release package but their use is not recommended anymore because they will most probably no longer be available in future releases.

...

<autosave

  enabled="true"

  method="filesystem"

  destination="c:\folder\myfile.htm"

  interval="300"

/>

...

So the content of the editor will be saved in certain intervals (unit in seconds).

For more information please review the edit-on Pro Integration Manual.

The first step is to activate the HTTP POST upload mechanism for images, multimedia objects and documents in the "config.xml" file, e.g.:

...

<filemanagement>

      <file type="image" baseurl="http://www.myserver.com/"

       autoupload="true"

       onuploadfinished="uploadStatusReport">

       <http url="http://www.myserver.com/upload.php" />

      </file>

      <file type="object" baseurl="http://www.myserver.com/"

       autoupload="true">

       <http url="http://www.myserver.com/upload.php" />

      </file>

      <file type="document" baseurl="http://www.myserver.com/" >

       <http url="http://www.myserver.com/upload.php" />

      </file>

 </filemanagement>

...

Then you have to specify a server-side script which manages the file upload. By uploading files using the HTTP POST upload mechanism (see above), every file will be kept in a form field called "uploadfile". To make sure that the file was uploaded successfully, the server-side script must return "OK" resp. "Failed" if not.
Below please find a sample for the image upload:

...

 <?php

 $filename = $_FILES["uploadfile"]["name"];

 $tmp_name = $_FILES["uploadfile"]["tmp_name"];

 if(file_exists($filename)) {

       while(file_exists($filename)) {

          $ext = strchr($filename,".");

          $pos = strpos($filename,".");

        $filename = substr($filename,0,$pos)."$".$ext;

       }

 }

 if($fp = fopen($tmp_name,"rb")) {

       $file = fread ($fp, filesize($tmp_name));

       fclose($fp);

 } else

       die("Failed");

 if($fp = fopen($filename,"wb")) {

       fwrite($fp,$file);

       fclose($fp);

 } else

       die("Failed");

 echo "OK";

 echo "|http://yourserver.com/eop4".$filename."|";

 ?>

...

For more information please review the edit-on Pro Integration Manual, chapter "2.9. Managing embedded files".

1. You can edit an existing dictionary file of edit-on Pro

- or -

2. You can set the <addspellcheckwordurl> tag within the config.xml file for adding words to the "server side user dictionary", which will always be utilized together with the editor's standard spelling checker dictionary during the spell checking process

- or -

3. You can add words to the "local user dictionary" on the client machine

1. Edit a default dictionary file
In this case you have to "unjar" the corresponding JAR archive which you will find in the "./eopro/lex" folder (e.g. "americanenglish.jar"). After unpacking, you can open the directory "./sc/lex" (in this case: ./americanenglish/sc/lex" which contains the "userdic.tlx" file among others. In order to edit it, you have to open the file with any text file editor (e.g. Notepad). You can then add any words to the dictionary file separated by a hard line-break.

2. Use the <addspellcheckwordurl> property to add words to the "server-side user dictionary"
Another possibility is to set the <addspellcheckwordurl> tag within the config.xml file. By doing so, you can press the "Add word" button within the editor's spell checker dialog to add a word to the spelling checker's user dictionary using a server-side script (e.g. PHP/JSP/ASP,etc.) that writes the custom word to the user dictionary file.

In this case you have to use a "config.xml" file of the edit-on Pro samples package which you will find in the "./samples" folder (e.g. "./samples/general-api") of the unzipped edit-on Pro installation package. By opening the file with any text editor, you can set the <addspellcheckwordurl> XML node within the <spellingcheckers> element, e.g.:

...
<spellingcheckers>
  ...
  <addspellcheckwordurl url="http://myserver.com/adword.php" />
  ...
</spellingcheckers>
...

You will find more information in the edit-on Pro Integration Manual, chapter 3.1. Configuration file.

3. Add words to the "local user dictionary" on the client machine
It's also possible to add words to the "local user dictionary". To do so, you can simply use the context menu of the editor. These words will then saved in a TLX file (depending on the language, e.g. "americanenglish.user.tlx") located in the ".realobjects" folder within the USER_HOME directory.

Please note: As the "local user dictionary" is located on the client machine, it is stored locally and NOT on the server. Thus this dictionary is available for the user on this machine only.

Below you will find a summary of the available options using WebDAV.

1. Documents

Uploading HTML documents to the WebDAV server
Using the "Upload Document" dialog, you can select the directory on your WebDAV server where your current HTML document should be uploaded to.

Inserting HTML documents into edit-on Pro
By clicking on "Open URL" within the "File" menu, you can load your document.

2. Images and multimedia objects

Uploading images and/or multimedia objects to the WebDAV server
Within the "Upload Objects" or "Upload Images" dialog, you can upload images or multimedia files to your WebDAV server. It is also possible to use the "Upload Objects and Images" dialog. (see also the multimedia support and automatic image upload feature description)

Inserting images or multimedia objects into edit-on Pro
In order to insert images or multimedia objects from the WebDAV server, you have to use the "Insert Image" resp. "Insert Object" dialog. Within these dialogs, you have to chose the "Browse Image Repository" resp. "Browse WebDAV directory" button.

3. Hyperlinks

Inserting hyperlinks to uploaded files
You can insert hyperlinks to files which are already uploaded to the WebDAV server. In order to do so, you have to open the "Insert Hyperlink" dialog and to click on the "Browse WebDAV directory" button.

For further information about uploading and inserting files using WebDAV please review the edit-on Pro Integration Manual, chapter 2.9 "Managing embedded files". There you will find the instructions for how to enable WebDAV dialogs, to configure the toolbar and to activate WebDAV support within the "config.xml" file.

Accepting the certificate grants edit-on Pro certain rights on your machine, e.g. inserting images from you local hard drive. After confirming this security check with the "Always"-button, your browser will store the applet's certificate on your machine and will not prompt for the security message again. Please keep in mind, the prompted message is displayed through the browser's standard security dialog. It is not an error message!

When the edit-on Pro certificate has expired a message is displayed in the browser's security dialog, asking the user to again grant certain rights to the editor applet.

Actually, this does not mean that the digital signature for the edit-on Pro applet is not valid anymore. It only means that the certificate can not be used anymore to digitally sign the applet. The expiration of the certificate does not affect the functionality of the editor in any way.

However, in order to avoid that the security dialog shows the expiration of the applet's certificate, we recommend to work with the latest edit-on Pro version, which is always signed with a valid certificate.

You can download the latest version from our download area.

The manual gives you an overview of the user interface, the keyboard shortcuts and standard editor functions (as i.e. context menu and toolbar icons). In addition it explains how to upload images and how to use the document structure dialog.

Integrators/developers of course can modify the help files according to the individual requirements of their installation. Upon request RealObjects will also provide the related DocBook files and style sheets.

Activating the "Copy to Clipboard" button will place information about your system and your edit-on Pro configuration on the clipboard. It can then be pasted to any other application, e.g. notepad.

You can find more information about defining JavaScript actions within the Integration Manual, Chapter 2. Advanced Integration, 1. Custom actions.

For more info see http://www.apple.com/support/downloads/javaupdate142.html

For an overview of all system requirements, please review the System Requirements page.

Additionally, the latest JRE improves the performance and stability of the applet in comparison to older versions.

For an overview of the system requirements, please see the System Requirements page.

Using the following JavaScript work-around it is possible to set the focus back into the form field which was edited before initializing edit-on Pro but it won't be possible to continue typing during the editor's loading process:

1. Define a global JavaScript variable "editedField"

 <script type="text/javascript" language="javascript">

 // global variable editedField

 var editedField;

 </script>

2. Use edit-on Pro's JavaScript API method "setOnDataLoaded"

• The function referenced within this API method will be called right after inserting content into the editor using e.g. setHTMLData or setHTMLDataFromURL
• The referenced function will set the focus back to the previously edited form field

 <script type="text/javascript" language="javascript">

 // applet configuration

 eop = new editOnPro(898, 400, "eop4_inst1", "myId", "eop");

 .....

 // the method "setOnDataLoaded" calls the JS function setFocusOnField()

 eop.setOnEditorLoaded("loadContent");

 eop.setOnDataLoaded("setFocusOnField");

 .....

 eop.loadEditor();

 </script>

3. Set up a JavaScript function saveFieldName(field)

This function should store the name of the previously edited form field (currentFormField) within the global variable editiedField

 <script type="text/javascript" language="javascript">

 function saveFieldName(currentFormField)

 {

  editedField=currentFormField;

 }

 </script>

4. Set up another JavaScript function "setFocusOnField"

This function should return the focus to the form field stored in the variable "editedField"

 <script type="text/javascript" language="javascript">

 function setFocusOnField(editedField)

 {

  document.forms["yourform"].elements[editedField].focus();

 }

 </script>

5.  Define the "onblur" attribute for the HTML form fields contained in your website.

Setting this attribute will call the JavaScript function "saveFieldName(field)" after the focus has been requested by edit-on Pro. Example:

<html>

.....

 <textarea name="mytextarea" onblur="saveFieldName('mytextarea');"></textarea>

.....

</html>

If you are placing multiple instances of the edit-on Pro editor on your page, you should make sure the JavaScript library is only included once for the whole page and not once per edit-on Pro instance.

 The Universal Selector:

* {font-size:large}

Matching Descendants, e.g.:

div i { color:red; }

Attribute Selectors, e.g.:

p { font-weight:bold; font-family:Tahoma,sans-serif; font-size:14pt; }

p[align] { color:red; }

p[align=center] { color:blue; text-align:left; }

td[abbr~=Berlin] { background-color:#FFFF00 }

*[lang|=en] { background-color:#FF0000; color:#FFFFFF; }

Class Selectors, e.g.:

h1.background { background-color:#FFFF00 }

ID Selectors, e.g.:

p#883 {font-weight:bold} 

BTW, we experienced this with our online demo by using a real Japanese workstation. By running edit-on Pro with Japanese characters from a Windows client three cases might arise.

Note: In any of the following cases you have to set edit-on Pro's character encoding to "UTF8", see also integration manual (chapter 3, encoding). Furthermore it is necessary to set following META definition into the web page which contains the editor in order to use the browsers correct character encoding:

<meta http-equiv="Content-Type" content="text/html;charset=utf-8">

a) You are using a non-Japanese OS/machine without Japanese character support installed. In such a case you will not be able to edit or view Japanese text within the editor. Within the WYSIWYG view you will only see rectangles or other typesets, but no Japanese characters. You will not even be able to view the text in your standard browser and most likely the OS/browser requests the OS installation CD-ROM.

b) On a system with a non-Japanese default input language, e.g. English, it is neccesary to perform the following steps on the client system in order to display Japanese character sets within edit-on Pro.

System specific settings on Windows:

• Open the 'Regional Options' Dialog within Windows's control panel
• Within the option 'Language Settings for the System' additionally check Japanese (could require separate installing / reboot of the system)
• Now it should be possible to enable the Microsoft Japanese IME in the 'Input Locales' and input Japanese character into non-Java applications like Wordpad etc.

c) You are using a Japanese OS/machine with a Japanese keyboard etc. Now edit-on Pro will fully support Japanese characters. You can edit/type any Japanese text within the WYSIWYG view, save the document in a HTML file and re-open it.

body { font-family:SansSerif; }

or / and:

p { font-family:SansSerif; }

For embedding CSS styles / stylesheets into the editor you could use the applet's setStyleSheet / setStyleSheetURL / addStyleSheet JavaScript API methods.

More details on these JavaScript APIs can be found within our Integration Manual at the chapter JavaScript API / Java API.

XHTML 1.0 Transitional DTD

edit-on Pro is fully XHTML 1.0 Transitional compliant as the applet validates contents against the the official W3C XHTML 1.0 Transitional DTD.

Custom DTD

edit-on Pro allows you to use custom DTDs in order to limit the set of elements and attributes in your documents or in order to add custom attributes and elements. However, this will only have an effect on the content that is imported into the editor, i.e. when the content is imported, the editor will parse it and remove any attributes or elements not allowed according to the specified DTD.

XHTML 1.0 Strict DTD

edit-on Pro is NOT XHTML 1.0 Strict compliant out-of-the-box, but it is possible to achieve this compliance with some customization. Unfortunately, using another DTD than a subset of the XHTML 1.0 Transitional DTD or an extended version of this DTD is not recommended at the moment, as this will cause problems when cut and paste or drag and drop of content is used, because of the mechanism the editor uses to reinsert the content. Actually, when cut and paste or drag an drop is used, a document fragment will be exported to the clipboard, and will again be validated when it is imported. Now this is what causes problems, as XHTML 1.0 Strict for example does not allow textual content inside the body element.

For more information about using DTDs please refer to the integration manual (chapter 7, Using Custom DTDs) and the online Custom DTD Sample

<presetsymbols>

<symbol entity="&#913;"/>

<symbol entity="&#914;"/>

</presetsymbols>

You can add additional symbols to the dialog by adding additional entities through the use of "symbol" elements.

The configuration files included within the installation/samples package are UTF-8 encoded. edit-on Pro will compare the character encoding of these files with their XML headers' encoding information, which is by default:

<?xml version="1.0" encoding="UTF-8"?>

In case the XML files' encoding isn't UTF-8 the applet will request the according file for a second time as it will re-check the character encoding.

You can avoid multiple loading of the configuration files by editing and saving them as UTF-8 documents in common text / XML editors (e.g. Windows Notepad, jEdit, etc.).

In order to preserve only your custom tags and custom attributes you must perform the following steps:

1. Create a custom DTD containing your tags and attributes
   To create a custom DTD containing custom tags and attributes, you can use the xhtml1-transitional.dtd contained in the doc/resources folder of the edit-on Pro installation package as basis for your modifications.
   For more information about how to customize a DTD, please review the edit-on Pro integration manual, chapter 7.2 Defining Custom Tags
   
   
2. Load the custom DTD into edit-on Pro
   You must load a template referring to the modified xhtml1-transitional.dtd before loading any other content. To do so, use the method setTemplateURL() in the page loading the applet.
   
   Example:
   
   eop.setTemplateURL("template.xhtml");
   
   For more information about how to customize a DTD, please review the edit-on Pro integration manual, chapter 7.1 Specifying a custom DocType
   
   
3. Load a style sheet for advanced features
   In case you want to use advanced features such as readonly tags, you must load a corresponding style sheet. This style sheet must contain the appropriate styles for your custom tags.
   
   For more information about how to customize a DTD, please review the edit-on Pro integration manual, chapter 2. edit-on Pro CSS extension

A sample which demonstrates the use of custom tags and attributes is included in the edit-on Pro installation package in the folder /samples/customdtd and is also available online at edit-on Pro Custom DTD Sample.
Please also read the samples readme.txt file as it provides some further information.

To avoid the verification of the POST request you can turn it off by adding the following line to your code: <%@ Page Language="C#" validaterequest="false" %>

cleanuponsave="auto" dropillegalattributes="false" dropillegaltags="false" />
....

If you do not want edit-on Pro to remove your custom tags and attributes, but to remove all other tags and attributes which aren't included in the XHTML Transitional DTD, you must create your own DTD containing your custom tags and attributes, see FAQ

• Editor size and color
• Pull down menus
• Context-sensitive menus
• Keyboard shortcuts for all editor actions
• Enable/disable toolbar buttons
• Tool-tips
• Language (English, German, French and Spanish is already included)
• Tab panel and status bar placement
• Enable/disable "Source View"
  

This can be conveniently done through two clearly structured XML configuration files, uiconfig.xml and config.xml.

The editor allows to group icons and menus using separators, change the toolbar order or replace the standard icons by your own icons with different sizes and styles. With these flexible options, you can enforce corporate design standards of the editor appearance and guarantee seamless integration into your application.

It is also possible to include custom toolbar buttons and custom dialogs which, for example, enable the interaction with server side applications such as databases, image repositories, etc.

For more information see also the Customization page.