ASPNET Tutorials
ASPNETUsing Proper Interfaces in ICallbackEventHandler
ICallbackEventHandler is a very important indicator in an Ajax based program as it activates or more specifically chooses the control to be transformed into a target. This is a special trick since controls are the ones who can activate the changes in the program.
But with ICallbackEventHandler, it has been chosen to receive changes. That means the control is now the third party or the medium for another control. Instead of triggering a response, ICallbackEventHandler gives controlled response.
In this article, we take a look at some of the most popular ICallbackEventHandler. Optimized for any major type of browsers, developers should be able to easily implement them. Each of them has different functions so it’s best to be familiar with all of them.
GridView Class When activating this type of interface, developers should be able to create good looking tables. Think of it like the Excel program where you can easily sort the information. That means you’ll be able to make some changes in the table and subsequently, sort the information in this Ajax based program.
In a single page, developers should also create multiple tables without the trouble of code overlapping. Aside from easily creating tables, you’ll be able to manipulate them so that they would be interacting. Even the appearance of the tables, including the colors and styles, could be changed.
DetailsView Class – This ICallbackEventHandler interface could be easily integrated with GridView Class. Although it works almost the same as the previous interface, the program is more focused on the records. This interface looks for information in the server related to the information needed and shows them efficiently in controls.
The best thing about DetailsView is that it can be integrated different data sources. SQLDataSource is a popular data source which binds easily with DetailsView Class. Aside from records, other information – even commands could easily be integrated with DetailsView Class. That means, developers could integrate not only information to the table but also additional commands if they want to do something about the record that they have just found.
TreeView Class – Simply put, TreeView lets developers see how the program is built in terms of hierarchy. TreeView Class makes it easier to understand the important programs that were implemented. As the name suggests, the program is implemented in a tree structure. This is probably the most important ICallEventHandler interface since it practically strings everything together.
Instead of interacting with data or records, TreeView interacts with SiteMapDataSource control. That makes it possible for TreeView to display everything in one setting. This interface is very dynamic since the page changes dramatically each time new information is provided. There’s also a check box where you can ask for information easily.
AjaxWith.com Offers
Sponsored Links
