Code Behind File:
protected void GridView1_RowCommand(object sender, GridViewCommandEventArgs e)
{
if(GridView1.EditIndex == -1) return;
FileUpload fileUpLoad = GridView1.Rows[GridView1.EditIndex].FindControl("FileUpload1") as FileUpload;
string fileName = fileUpLoad.FileName;
string fullPath = Path.GetFullPath(fileName);
fileUpLoad.SaveAs(fullPath);
}
The following code shows to hide "Login" if users are already logged in and hide "Logout" if users are not logged in from the menu.
1 protected void Menu1_DataBound(object sender, EventArgs e)
2 {
3 Menu menu = (System.Web.UI.WebControls.Menu)sender;
4 MenuItem menuToRemove = null;
5
6 if (HttpContext.Current.User.Identity.IsAuthenticated)
7 {
8 foreach (MenuItem smn in menu.Items)
9 {
10 if (smn.Text == "Login")
11 {
12 MenuItem parent = smn.Parent;
13 if (parent != null)
14 {
15 parent.ChildItems.Remove(smn);
16 }
17 else
18 {
19 menuToRemove = smn;
20 }
21
22 }
23 }
24 if (menuToRemove != null)
25 {
26 menu.Items.Remove(menuToRemove);
27 }
28 }
29 else
30 {
31 foreach (MenuItem smn in menu.Items)
32 {
33 if (smn.Text == "Logout")
34 {
35 MenuItem parent = smn.Parent;
36
37 if (parent != null)
38 {
39 parent.ChildItems.Remove(smn);
40 }
41 else
42 {
43 menuToRemove = smn;
44 }
45
46 }
47 }
48
49 if (menuToRemove != null)
50 {
51 menu.Items.Remove(menuToRemove);
52 }
53 }
54
55
56 }
The following codes are the examples to get the control out from the templatefield of Detailsview:
TextBox UserNameBox = DetailsView1.FindControl("UserName") as TextBox;
Label ErrorLabel = DetailsView1.FindControl("ErrorLabel") as Label;
The following code may handle the exception when insert the duplicate records
protected void SqlDataSource1_Inserted(object sender, SqlDataSourceStatusEventArgs e)
{
if (e.Exception != null)
{
//handle error or display message on label or something here
}
}
(FROM: http://www.eclipsepluginsite.com/jface.html) Working With JFace Viewers
You can see that we have used String Literals "A1" and "A2" respectively while creating a row in table. If you think from object oriented perspective it is a severe limitation. In object oriented world we talk in terms of Objects. In order to build above table we will have to get Strings out of those objects and then supply it to Table to form every single row. Isn’t there a way in which we can simply map objects to tables so that table can itself use those objects and populate itself? This is where JFace viewers step in to provide OO wrappers around their associated SWT widgets. JFace provides two types of Viewers, Text Viewers and List Viewers. First we will discuss about list viewers. JFace list viewers, such as TableViewer and TreeViewer, allow you to directly use your business objects (Employee, Customer, User, Business etc.) without. The trick is to provide adapters for things such as retrieving an item's name/label OR for retrieving an Tree parent's children (tree widget). So we will talk about these adaptors first before moving onto implementing Table/Tree Viewers. A label provider maps an element of the viewer's model to an optional image and optional text string used to display the element in the viewer's control. The two most frequently used label providers are ILabelProvider and ITableLabelProvider In order to display elements name and label we can use getImage and getText methods provided by ILabelProvider Similarly in case of ITableLabelProvider, in order to display label image and label text for any column in a table we can use getColumnImage and getColumnText. We can use setLabelProvider() method to attach/associate provider with the viewer. A content provider is another common adapter type used in list viewers. This provider is used to feed the actual content to the viewer. Viewer then uses its internal logic to display these input elements with its internal controls. The two most frequently used content providers are IStructuredContentProvider and ITreeContentProvider. These adapters provide convienient methods to retrive child elements for a given element. We can use setContentProvider() method to attach/associate provider with the viewer. A intial domain/business model of the application can be associated with the viewer with the help of setInput() method. A viewer sorter is a adapter which is called by viewer before the elements/contents are displayed to the user. We can use this provider to sort the elements which are provided by the content provider. We can use setSorter() method on the viewer to attach sorter. 4. Viewer Filters ProvidersAs the name suggests a viewer filter is used to filter out some of the elements from original list of elements provided by the content provider. For example: Original list of Employees consist of employees with two type of roles Admin, Non admin. We can use filters to display only admin role users. We can attach viewer filter by using the setFilter() method on the viwer itself. The TableViewer class acts as a OO wrapper around the Table widget. Table Viewer is capable of displaying data in rows and cloumns with the help of adapters like label provider and content provider. Table Viewer provides many useful APIs, Please refer to online Eclipse Platform API Specification Following example creates a table viewer
In Above listing we are creating table viewer Then we are creating two columns namely "Hello" and "Bye" The header of each column is set using setText() method. There after label provider and content providers are being attached with the viewer. Following listing shows how the label provider looks like
Tree Viewers The treeViewer class acts as a OO wrapper around the Tree widget. Tree Viewer is capable of displaying data in hierarchical manner with the help of adapters like label provider and content provider. Tree Viewer provides many useful APIs, Please refer to online Eclipse Platform API Specification The following listing creates a tree viewer
In above code listing we are creating the tree viewer. There after we are configuring label and content adapters. Following listing shows the rest of code:
|
2009 ·Coding Life by TNB
