The Zoople HTML5 editor for ActiveX is an HTML editor that can be used in any 32bit COM-based development environment. It can be used in VB6, VFP, Office / VBA applications.

An HTML 5/CSS 3 editor ActiveX control that developers can use to manage HTML rich-text in their applications. A valid CSS rules string can apply most CSS3 stylings in the same manner as you would to CSS on a webpage.

It can be used in VB6, Office / VBA, and other environments that support 32-bit ActiveX controls.

The Zoople HTML Editor is an ActiveX upgrade for existing nBit customers. Existing nBit HTML Editor license holders get a 35% discount on the total purchase price. This does not apply to source codes licenses. To receive a discount on your order, please email us with the information about your current license.

The Inline Spelling Checker ActiveX DLLL is also available as an optional product. Spell checker allows you to spell-check as you type and auto-correct as your type. It also spell-checks the entire control text with or without a pop-up spelling corrections dialog.

Zoople HTML5 Editor ActiveX DLL Great Features:

The WYSIWYG editor's feature-rich user interface includes;

• Text formatting and alignment
• HTML Table handling, including row and column management
• Images management
• CSS3 visual builder
• optional source markup editing
• Full language localization of the entire control's user interface
• This includes tooltips, menus, and forms
• Includes language file examples for (English, German, French, and Spanish)

Developers can also;

• Directly access the HTML DOM and DOM events like mouse clicks, key down events, etc...
• Retrieve the currently selected HTML element as an IHTMLElement
• Iterate through the DOM tree to find and test for specific parent elements
• Intercept clipboard functionality
• Execute their formatting commands on the edited document
• Implement custom dialogs for images, hyperlinks, and other URLs
• Implement "spell-as-you-type" functionality with auto-correction, error highlighting, and an error checking discussion (see below)