UltimateSpell from Karamasoft helps you add a Microsoft Word®-like spell checker to your ASP.NET website or CMS product in just a few clicks. Includes Word -like Inline Spelling, Word -like Spell Dialog and Life-Saver Samples.

1. Word -like Inline Spelling — Spell check as you type in any editable area by underlining misspelled words with a red squiggly line. Drag-and-drop onto your web form in Visual Studio, and run.
2. Word -like Spell Dialog — Display a traditional spell check dialog box to correct spelling mistakes sentence-by-sentence. Spell check 1500 words per second using the provided API.
3. Life-Saver Samples — Use the provided C# and VB samples as your templates. Copy the most appropriate sample into your web application, and go live as quickly as possible.
4. All .NET Editions in One — Native builds in .NET 1.1 (Visual Studio 2003), .NET 2.0 (Visual Studio 2005) and .NET 3.5 (Visual Studio 2008) provided in one package.

Top 10 Features of Karamasoft UltimateSpell for ASP.NET

1. Word®-like Spell Checker — Spell check as you type in any editable area by underlining misspelled words with a red squiggly line. You can right-click on a misspelled word and select a suggestion from a context menu.
2. Spell Check Dialog Box — Word®-like spell check dialog box to display one spelling mistake at a time, and select one of the suggestions from a listbox. Display text sentence-by-sentence in order to understand the context.
3. Grammar Check Dialog Box — Grammar check dialog box to display grammar errors one at a time sentence-by-sentence. Requires Microsoft Word 2003 or 2007 installed on the server. Recommended for intranet use only due to the Local System requirements of the IIS application pool. Supports .NET 2.0+.
4. Show Synonyms — Show the synonyms of a word by right-clicking on it and selecting the Synonyms option in the popup context menu. Supports .NET 2.0+.
5. High Performance — Spell check very long text areas without compromising any performance hits. Send small portions of the text to the server as needed, while the user spell checks through the text.
6. Fast Spelling — Spell check 1500 words per second using the provided server-side API. Use the same fast spelling engine for inline spelling, dialog box or API.
7. Auto Correct — Automatically correct your spelling errors as you type. This feature fixes your spelling mistakes if it finds only one suggestion just like in Microsoft Word®.
8. Auto Find — Automatically find and spell check all editable controls, or specify a comma separated list of control ids to spell check.
9. Look Up Meaning — Look up the meaning of a suggested word in an online dictionary that you can configure in the language XML file.
10. 34 Dictionaries — Use any of the 34 dictionaries available on our website, or use your own dictionary text file that contains one word per line.
11. Custom Dictionaries — Add words to your custom dictionaries, and cache them as regular dictionaries. You can use a server-based custom dictionary and a regular dictionary at the same time.
12. Medical Dictionary — Use the open-source MeDic dictionary as your regular or custom dictionary, or append the content of the MeDic text file to the end of the English dictionary, and use the combined one.
13. Multi-Language — Display different wordings in the spell check dialog box based on your language by configuring the language XML file.
14. Spelling Options — Lots of options to change the behavior of the spell checking engine either on the server-side, or on the client-side.
15. Cache Dictionary — Automatically caches both regular and custom dictionaries for fast interaction and data retrieval.
16. Selected Area Only — Select a piece of text to spell check by using your mouse or keyboard. You can spell check only the selected area instead of the whole text.
17. Control Suggestions — Specify the maximum number of suggestions to be returned by the spelling engine for each spelling mistake.
18. Keep Ignoring — If you click Ignore All to ignore all occurences of a word it will keep ignoring them until you refresh the page.
19. PostBack on OK — Return to server when the user clicks the OK button on the spell check dialog box bypassing a changed flag. You can see any changes made to the original text during spell checking.
20. Inside Other Controls — Insert the UltimateSpell control into other server controls such as a datagrid or a user control.
21. Custom Style — Change the style of the spell button, misspelled word style and spell check dialog box based on your design preferences.
22. AJAX Enabled — Spell check very long text by sending small blocks of text to server using AJAX techniques without refreshing the page.
23. Server-Side API — Use the spell checking engine from inside ASP.NET web applications and web services, or Windows Forms .NET applications.
24. Client-Side API — Open the spell check dialog box from any client-side action by calling the UltimateSpellClick() method and passing the ClientID of the UltimateSpell control as an argument.
25. Windows Forms Support — Use the Windows Forms samples in C# and VB with full features and user interface. Spell as you type feature is only supported in ASP.NET.
26. UltimateEditor & UltimateSearch — Built-in integration with our ASP.NET rich text editor and ASP.NET search engine products.
27. Compliancy — XHTML 1.0 Transitional compliant.
28. AJAX Support — Microsoft ASP.NET AJAX UpdatePanel, Karamasoft UltimateAjax.
29. Cross-Browser Support — IE5+, NS7+, Firefox 1.0+, Mozilla 1.0+, Opera9+, Safari 2.0+.
30. System Requirements — Windows 2000/2003/2008/XP/Vista, IIS 5.0+, ASP.NET 1.1/2.0/3.5.

Please visit http://www.karamasoft.com/UltimateSpell/Features.aspx for more information and to download a trial version.

With the release of Outlook 97, Microsoft introduced to the masses an entirely new way in which to deliver information to end-users within a grid control. Component vendors such as us then released components which allowed developers to build Windows® and ASP.NET applications that mimicked the capabilities of Outlook 97’s grid. Over the last 10+ years, countless individuals have come to rely on the grouping/sorting/summary computation capabilities of this new grid metaphor on the Windows and ASP.NET platforms.

The Power of an Outlook® Style Grid
The real strength of the Outlook style grid lies in its ability to organize information for the end-user and report on that information in an effective manner. In a traditional 2 dimensional grid, a user would not have the luxury to analyze the information displayed on screen. Assume for a moment that a grid is used to display sales information. Old style 2-D grids do not allow the user to group sales information by region and to better understand the data being presented to them. But when using an Outlook style grid, the user is free to group and summarize information by any column…giving them the productivity tools needed to get their job done instantly without generating complex sales reports.

Size Matters
The UI power available in an Outlook® Style grid, however, comes at a cost. That cost is dataset size. Large datasets in an ASP.NET and Windows Forms application impact the usability of the application. When it comes to this modern grid UI, users will invariably want to analyze information and they will rarely understand why a grid performs well with a 100 records and fails with 100,000 records. To illustrate, let’s continue with our previous example. Assume a developer builds a web or Windows UI that displays sales data within a grid control and during testing with 100 sales records, the web server (or Windows client machine) and the components used to build the application perform admirably. The developer then delivers the solution to market and the customer is elated by the new UI.

As the customer begins adding information to the database and the dataset size grows, problems take shape. Grouping, summary computation, sorting, and navigation speed start to bog down. The problem worsens over time and eventually the developer is left with only a single option – to restrict the number of records being rendered on screen.

The developer then delivers a modified solution to the customer and the customer asks a very logical question…Why am I not able to group and summarize sales information for my business over the last year? So what if my database has 500,000 records in it? Why can’t I just see the information on screen without having to wait 2 minutes to get incorrect results?

Compromise is Not the Answer
Outlook style grids are extremely powerful but this power can only be realized if the grid control can consume data effectively. If this is not true…if the grid should only be used to display limited datasets, then why bother using an Outlook style grid?

When we chose to write our ASP.NET and Windows Forms grid, foremost in our minds was performance and optimum memory use against large datasets. Our reasoning was simple – whether a grid displays 1 record or a million, the server and client should respond instantly and give the end-user the means with which to operate his business without unwanted roadblocks and hurdles.

Let the Database Server Do What it Does Best
No matter how well one designs a data processing engine, it will never do its job well if one fails to recognize that database specific operations ought to be executed on the database server. No matter how ingenious the algorithms – no matter how brilliant the technology…if the grid is forced to manage data itself, you can bet that a large dataset will eventually bring the web server or the Windows client to its knees and make the application totally unusable.

Don’t Kill the Web Server and Windows Client
The obvious question one might ask at this point is why – why should a large dataset, hundreds of users, and the need to group/sort/navigate records throughout the business day impact the application in such a massive way. The answer is simple: With ASP.NET and Windows, most grid controls need the entire dataset to be loaded and processed for every operation…be it a trivial operation such as record navigation from one page to the next or complex operations such as data grouping. Yes, it’s the web server that is forced into this position by competing grid controls and it is the web server and or Windows client that has to allocate the necessary resources to keep the application running.

At the end of the day, that’s why developers resort to filtering result sets – they need the web server or Windows client to function and not fail.

Enough with Crippling Limitations
The new ASPxGridView and XtraGrid Suite confront the limitations we’ve outlined head-on and have been engineered to free you from the hassles you otherwise would be forced to workaround.

Instead of reading the entire dataset from the data server and then managing data within the grid, the ASPxGridView and XtraGrid Suite simply display data that has already been grouped or sorted on the data server. This is possible because of our specially designed data provider included within the suites. This provider can produce smart queries so that all the grid needs to do is download records to be displayed within the current page. If you have 100,000 records in your data source and want to display 10 records on the page, the grid will need to download only 10 records rather than the 100,000 records required with each postback or callback when using competing grid controls. This means that with the ASPxGridView or XtraGrid Suite, what was once simply impossible with competing grids (but entirely needed by end-users) can now be easily accomplished.

Figure 1

See it for Yourself
You don’t have to take our word for it. To see how all of this works, review our online 300,000 Records demo and compare results with your current ASP.NET grid control.

Figure 2

Seeing is Believing
For a detailed tutorial and explanation of the mechanics involved, please review the following video

Reproduced with permission from DevExpress

In this code snippet, you will learn how to add a choice component using Java language

/*<applet code = "Mycombo.class"

width = 250 height = 250></applet> */


//Compilation: javac Mycombo.java

//Execution: appletviewer Mycombo.java


import java.awt.*;

import java.applet.*;

import java.awt.event.*;


public class Mycombo extends Applet implements ItemListener

{

TextField t1;

Choice c1;


public void init()

{

c1 = new Choice();

c1.addItem("India");

c1.addItem("USA");

c1.addItemListener(this);

add(c1);


t1 = new TextField(25);

add(t1);

}


public void itemStateChanged(ItemEvent e)

{

String s = (String)e.getItem();

if(s == "India")

{

t1.setText("Capital is NewDelhi");

}

else if (s == "USA")

t1.setText("Capital is washington");

}

}