Technical Considerations - The Concept Explained

True WYSIWYG - server document synchronization

The HTML5 Web Editor consists of two parts: The ASP.NET server control Web.TextControl that provides the client-interface and user experience and the TX Text Control Web Server running as a Windows Service hosted on a Web server. The TX Text Control Web Server engine is used to synchronize the document with the server in order to provide a consistent WYSIWYG text rendering.

Zero footprint - no plug-ins

The client side control is completely based on HTML5 and Javascript and doesn't require any client-side plug-ins. No browser or system security settings are required to run the control. The end-user does not need to confirm any downloads or settings and requires only an HTML5-enabled browser such as Firefox, Chrome, Safari or Internet Explorer.

Users want to seamlessly access and share content with others without any limitations when it comes to devices, hardware or software. A zero footprint editor addresses those requirements using the client-server visualization and synchronization architecture and uses the standard, modern browsers to enable editing in real-time.

Supported file formats

In contrast to HTML-based editors, the documents do not need to be converted to HTML for editing. HTML is limited and doesn't provide page-oriented features such as headers and footers or sections. Using the TX Text Control HTML5 Web Editor, documents of all supported formats such as DOC, RTF, DOCX, HTML or PDF can be directly loaded and edited. It gives end-users a consistent, MS Word-like interface for all document types and platforms. The HTML5 Web Editor provides the same user experience like TX Text Control for other platforms including Windows Forms and WPF. This enables developers to provide the same look and feel for Windows and ASP.NET Web applications.

Security considerations - Secure your documents

Security is a major concern when editing documents on the Internet. Web.TextControl supports the Secure Sockets Layer (SSL) to provide communication security. Additionally, thanks to the client-server visualization and synchronization architecture, the document is never available client-side. If not required, the user has no access to the content of the document and the document doesn't exist client-side. This enables developers to provide a secure interface to manipulate highly confidential documents in browsers without sending those documents and the content using the Internet.