XStandard XHTML (Strict or 1.1) WYSIWYG Editor

XStandard - Do it right. The rest will follow.

XStandard Upgrade Guide

Upgade To Version 2.0

API Changes

  • ModeChange() event has been renamed to ModeChanged()
  • ButtonClick() event has been renamed to ButtonClicked()
  • The following API have been removed:
    • Proxy
    • EnableProxy
    • EnableProxyAuthentication
    • Toolbar
    • Expand
  • The following API have been added:
    • ProxySetting
    • ProxyServer
    • ContextMenuActivated()
    • ContextMenuClicked()
    • ClearContextMenu()
    • ToolbarWysiwyg
    • ToolbarSource
    • ToolbarPreview
    • ToolbarScreenReader
    • ExpandToolbarWysiwyg
    • ExpandToolbarSource
    • ExpandToolbarPreview
    • ExpandToolbarScreenReader
    • ToolbarEffect

The behavior of Debug has changed. When set to yes, the editor will write to a log file all HTTP communication. This log file can be accessed from the Debug tab in the About dialog box. Do not enable this setting unless you need to debug HTTP communication.

Hooking Into JavaScript Events

The following code shows how to hook into JavaScript events.

  1. <script type="text/javascript">
  2. //<![CDATA[
  3. function xsButtonClicked(id, button, state) {
  4. alert('Editor: ' + id + '; function: xsButtonClicked(); button: ' + button);
  5. }
  7. function xsContentChanged(id) {
  8. alert('Editor: ' + id + '; function: xsContentChanged()');
  9. }
  11. function xsModeChanged(id) {
  12. alert('Editor: ' + id + '; function: xsModeChanged()');
  13. }
  15. function xsContextMenuActivated(id) {
  16. alert('Editor: ' + id + '; function: xsContextMenuActivated()');
  17. document.getElementById(id).ClearContextMenu();
  18. document.getElementById(id).AddToContextMenu('a', 'My item a', '');
  19. document.getElementById(id).AddToContextMenu('b', 'My item b', '');
  20. document.getElementById(id).AddToContextMenu('c', 'My item c', '');
  21. document.getElementById(id).AddToContextMenu('d', 'My item d', '');
  22. document.getElementById(id).AddToContextMenu('e', 'My item e', '');
  23. }
  25. function xsContextMenuClicked(id, menu) {
  26. alert('Editor: ' + id + '; function: xsContextMenuClicked(); menu: ' + menu);
  27. }
  28. //]]>
  29. </script>

Customization Files

The following customization files have changed:

  • buttons.xml
  • icons.xml
  • preview.xsl
  • screenreader.xsl
  • localization.xml

Please note that the editor ships with the default version of these customization files already built-in. Reference external customization files only if you have modified them.

In buttons.xml, the "indent" button is now used for inserting a tab character in View Source. If you need the previous functionality of this button, you can define a new button in buttons.xml file with a different ID. For example:

  1. <style>
  2. <id>p-indent</id>
  3. <label>Indent paragraph</label>
  4. <elt>p</elt>
  5. <attr>
  6. <name>class</name>
  7. <value>indent</value>
  8. </attr>
  9. <icon>indent</icon>
  10. </style>

In buttons.xml, the "validate" button was previously a generic button used to generate an event. In version 2 it is a predefined button used in View Source mode.

In buttons.xml, button ID "line" has been renamed to "separator".

XStandard In Desktop Applications

Because of API changes, some development environments will require that the editor be removed from the project and then added back in. Visual Studio.NET developers can follow these steps:

  1. Open your project
  2. Remove the editor control from the form(s)
  3. Right-click on the project and select Properties
  4. Select the References tab
  5. Remove both references to the XStandard editor
  6. Close your project
  7. Remove AxInterop.XStandard.dll and Interop.XStandard.dll from your project's bin folder
  8. Remove everything from your project's obj folder
  9. Re-open your project
  10. Add the XStandard control to your form(s)
  11. Double-click on the XStandard editor control (this will create a new event handler)
  12. Re-create all event handlers and move your existing code into the new handlers

Also, XStandard is no longer dependent on MSXML 4. This library does not need to be distributed as part of XStandard install.

XStandard In Web Applications

The best way to install/upgrade XStandard is through EXE for Windows or DMG for OS X.

Some Web browsers support auto-install and auto-upgrade. See Web Integration FAQs for details. Microsoft IE 7 has a bug with auto-install, please see Knowledge Base for a workaround. Version 2.0.0.0 CAB file for IE is available from:

http://xstandard.com/download/XStandard.cab

ASP.NET developers can download the new XStandard.WebForms.dll from ASP.NET example. Please note, this DLL is now offered in ASP.NET 1.1 and 2.0.

Web Services

It is recommended that you upgrade to the latest version of Web services. Download them from:

The new Web services are compatible with XStandard version 1.7.1.

Installer Changes

On Windows, XStandard version 2 will be installed in "C:\Program Files\XStandard". The version 2 installer will remove any previous version of the editor installed in "C:\XStandard".

Navigation

XStandard works for ...

AT&T, IBM, Microsoft, Xerox, Siemens, Philips, American Express, BP, HarperCollins Publishers, Penton, Colgate

What's New In XStandard Version 2.0

  • Support for OS X
  • Keyboard accessible interface
  • Find / replace
  • Support for JavaScript events
  • Enhancements to image and attachment libraries
  • Enhancements to table creation
  • Support for authoring definition lists
  • Ability to save images from the editor to My Computer

Full details on all new features

Most Popular FREE Downloads

  1. XStandard WYSIWYG Editor
  2. HTTP component
  3. ZIP component
  4. Image size component
  5. Base64 component