Page tree
Skip to end of metadata
Go to start of metadata

EditLive for ASP.NET has two editing modes:

  1. "Normal" mode. In this mode, an "EditLiveJava" server control represents an editor.
  2. "Inline Editing" mode. In this mode, there is one EditLiveJava control 

Converting each mode requires different steps as described below. If you encounter any issues, feel free to contact Tiny support.

Converting "normal" mode

Converting "normal" mode involves replacing the EditLive distribution with the Textbox.io distribution, and converting each "EditLiveJava" control to a "Textboxio" control.

Steps:

  1. Remove the EditLive distribution and .net DLLs from your project.
  2. Add the textbox.io JavaScript distribution and .net DLLs to your project, per the Getting Started guide.
  3. In each page containing EditLive, change your "register" directive from:

    <%@ Register Assembly="EditLiveJavaControl" Namespace="EditLiveJavaControl" TagPrefix="elj" %>
    to

    <%@ Register Assembly="TextboxioControl" Namespace="TextboxioControl" TagPrefix="textboxio" %>

     
  4. Change your <elj:EditLiveJava ...> controls to <tbio:Textboxio...>

  5. Convert the properties of this tag, as follows. If there is no equivalent Textbox.io property, just remove the property.

 

EditLiveJava control propertyTextboxio control propertyNotes
Cookie- 
DebugLevel- 
DownloadDirectoryScriptSrc

These properties are slightly different

  • DownloadDirectory is the folder containing editlivejava.js, e.g. "editlive/"
  • ScriptSrc is the full path to textboxio.js e.g. "textboxio/textboxio.js"
FocusOnLoad- 
HttpLayerManager- 
InputCharacterEncoding- 
JREDownloadURL- 
LoadClass- 
LocaleLocaleEditLive's Local property is a Locale object, whereas Textbox.io's property is a string.
OnInitComplete-Textbox.io's JavaScript SDK does have a loaded event, but it is not available in Textbox.io for ASP.NET.
OutputCharacterSet- 
Preload- 
ReadOnly- 
InlineEditing- 
BaseURL-Textbox.io's JavaScript SDK has a "basePath" config setting, but its meaning is very different.

ConfigurationFile,

ConfigurationText

Toolbar, ExtraConfiguration

There is no direct translation here. You will need to look at the customisations you've made to your EditLive configuration XML file and how they are best implemented in textbox.io.

In particular, look for any custom toolbar items. See toolbar in the Textbox.io JavaScript documentation.

ContentContent

Textbox.io only works with HTML body content, whereas EditLive may use body content or a full HTML document.

ReturnBodyOnly,

SetBodyOnly

- 
StylesDocumentStyles 
UserName- 
HeightHeight 
WidthWidth 

 

Converting "Inline Editing" mode.

Converting Inline Editing mode is a little more complicated than "normal" mode. Each EditableSection control is replaced by a Textboxio control, and some settings need to be moved from the EditLiveJava control to the Textboxio control, before deleting the EditLiveJava control.

 

  1. Remove the EditLive distribution and .net DLLs from your project.
  2. Add the textbox.io JavaScript distribution and .net DLLs to your project, per the Getting Started guide.
  3. In each page containing EditLive, change your "register" directive from:

    <%@ Register Assembly="EditLiveJavaControl" Namespace="EditLiveJavaControl" TagPrefix="elj" %>
    to

    <%@ Register Assembly="TextboxioControl" Namespace="TextboxioControl" TagPrefix="textboxio" %>

  4. Change your <elj:EditableSection ...> controls to <tbio:Textboxio...>. Use the conversion table below.

  5. Add/convert the following settings from your EditLiveJava control to your Textboxio controls
    1. ScriptSrc
    2. Locale
    3. ConfigurationFile/ConfigurationText
    4. DocumentStyles
  6. Remove your EditLiveJava control

 

EditLive EditableSection control propertyTextboxio Control PropertyNotes
Class- 
ContentContent 
DivStyle- 
Enabled- 
HeightHeight 
WidthWidth 
  • No labels