A Spell checking Control/Component by Keyoti

Quick designer based usage with the flexibility of code-behind access

RapidSpell Web provides a spelling component to add spell check functionality to your web applications, by simply adding the Web Control to an aspx page (Web Form) or directly accessing the classes in a code behind page. There are no programming skills required to use RapidSpell Web, because of it's strong visual designer (VS) design time support, making this ASP.NET spell checker control accessible to ASPNET page designers.

The UI provides all the usual features, add (to user dictionary), change, change all, ignore, ignore all, and smart suggestions. The user dictionary is stored on the server and can be unique per user, or shared amongst groups. The spell checker UI features an advanced preview pane to interactively highlight errors (with no post back), and accepts manual corrections.

Comprehensive text box support (plain, rich, custom) - Interactively checks any server or client side text boxes: , any Html text box component and 3rd Party controls, such as Dart's PowerWEB TextBox, 'pinEdit' from Pintexx, 'HtmlTextBox' and more. The custom client side interface mechanism allows interaction with practically any component, for example flash based text boxes.

Inline (as you type style) document highlighting - The RapidSpellWInline control provides Windows style in-text-box highlighting, with editable text box support for modern browsers and static 'overlay' support for older browsers.

Open API, for customization and non GUI usage
The open API allows customizations to be made to behavior, eg;

User dictionary behavior - eg. change the way the user dictionary is persisted (databases, Cache etc)
Parser behavior - eg. use UI as an offensive language checker

Flexibility - It is easy to use RapidSpell Web as a Web Control in an aspx page or programmatically in code behind, either way full customisation of style, layout and properties is possible. Using a simple HTML template mechanism it is also possible to layout the spell checker as you wish, including branding.

No post-back interface - All dictionaries (main and user's) are stored on the server, yet the user's spell checking experience is not hampered by any post-backs to the server, because there are none. User dictionaries can be stored on a database (examples provided).

Customizable dictionaries - Dict Manager, allows RapidSpell Dict files to be customized and created from other word lists, using the free 'Dict Manager' tool distributed with the product.

Popup or in page spell checking modes - RapidSpell Web provides two distinct spell checker controls; RapidSpellWebLauncher functions in one of two modes, 'popup' - which open's a small console window with the spell checker in it or in 'separate' - which loads the spell checker in the main window on a separate page, there are no restrictions with either of these modes.

Validator Control behavior - All of the included spell checker controls can be enabled as Validators, which perform validation of spelling in text boxes before allowing data to be saved. For example; when the form is posted back, the RapidSpellWebLauncher or RapidSpellWInline control will check for errors, if there are errors the user is prompted (in the validation summary) to run a spell check.

Decoupled checker engine - RapidSpell Web has a decoupled checker engine, which allows (via an interface definition) the use of any core spell checker class or other type of text parser to be used with the interface. This allows complete customization of the engine (including for tasks other than spell checking, such as offensive word checking) and the interface.

Sessionless - high performance - Works without session variables, making it possible to use RapidSpell Web with server clusters/farms. The single request architecture keeps server load down, and is possible through our high performance suggestions algorithm

Web forms or code-behind
Use the control from the designer or directly in the code-behind.

Customizable layout
Every aspect of the appearance (text, layout, and style) can be customized through simple properties.

File/DB user dictionaries
Open API allows the user dictionaries to be stored in any fashion desired - default is server file based, however this can be overridden for database, or application cache usage for example.