asp.net ean 13

asp.net ean 13

asp.net ean 13

asp.net ean 13

asp.net ean 13

asp.net ean 13,

asp.net ean 13,

asp.net ean 13,
asp.net ean 13,
asp.net ean 13,
asp.net ean 13,

asp.net ean 13,
asp.net ean 13,
asp.net ean 13,
asp.net ean 13,
asp.net ean 13,
asp.net ean 13,

asp.net ean 13,
asp.net ean 13,
asp.net ean 13,
asp.net ean 13,
asp.net ean 13,
asp.net ean 13,
asp.net ean 13,
asp.net ean 13,
asp.net ean 13,
asp.net ean 13,
asp.net ean 13,
asp.net ean 13,
asp.net ean 13,
asp.net ean 13,
asp.net ean 13,
asp.net ean 13,
asp.net ean 13,
asp.net ean 13,

asp.net ean 13,
asp.net ean 13,
asp.net ean 13,
asp.net ean 13,
asp.net ean 13,
asp.net ean 13,
asp.net ean 13,
asp.net ean 13,
asp.net ean 13,
asp.net ean 13,
asp.net ean 13,
asp.net ean 13,
asp.net ean 13,
asp.net ean 13,
asp.net ean 13,
asp.net ean 13,
asp.net ean 13,
asp.net ean 13,
asp.net ean 13,
asp.net ean 13,
asp.net ean 13,
asp.net ean 13,
asp.net ean 13,
asp.net ean 13,
asp.net ean 13,
asp.net ean 13,
asp.net ean 13,
asp.net ean 13,
asp.net ean 13,
asp.net ean 13,
asp.net ean 13,
asp.net ean 13,
asp.net ean 13,
asp.net ean 13,
asp.net ean 13,
asp.net ean 13,
asp.net ean 13,
asp.net ean 13,
asp.net ean 13,
asp.net ean 13,
asp.net ean 13,
asp.net ean 13,
asp.net ean 13,
asp.net ean 13,
asp.net ean 13,
asp.net ean 13,
asp.net ean 13,
asp.net ean 13,
asp.net ean 13,

The code creates an XmlTextWriter object by passing the path of the destination XML file to the constructor. Then a FileStream is created for reading data from the image file. The contents of the file are read by using the Read() method of the FileStream class, which accepts three parameters: the byte array to read the data into, the start index in the byte array from where the writing should start, and the length of data to read. The XmlTextWriter then starts writing the document. It first writes the XML processing instruction and the <imagefile> element. The <imagefile> element has two attributes: filename and size. The filename attribute stores the complete path of the image file that is being serialized as XML. The size attribute contains the size of the source image file. Image files contain nontextual data. You have a couple of options when you want to serialize nontextual data into XML files. You can use either hexadecimal encoding or Base64 encoding for the serialization. In our example, we use Base64 encoding. To write data into Base64 format, the XmlTextWriter class provides a method called WriteBase64(), which accepts three parameters: a byte array that contains the nontextual data, the index of the byte array from which the writing should start, and the length of data to write. The WriteBase64() method writes the supplied byte array as a Base64 string inside the destination XML element. Figure 3-17 shows how the XML file looks after serializing an image file.

The MAXIMIZED window state is for portlets that are the focus of the portal page there probably are not any other portlets on the page, and the user has probably selected this portlet to work with from the main page. If we had an e-mail portlet, when the user clicked the new messages link the portlet was displaying in the NORMAL window state, the e-mail portlet would expand to MAXIMIZED, and display 20 e-mail subject headings from the user s inbox.

var SilverlightControl; var theTextBlock; function handleLoad(control, userContext, rootElement) { SilverlightControl = control; theTextBlock = SilverlightControl.content.findName("txt"); theTextBlock.addEventListener("MouseLeftButtonDown", "txtClicked"); } function txtClicked(sender, args) { theTextBlock.Text = "Hello to you too!"; }

The MINIMIZED window state is for portlets that are not currently being displayed in the portal page, or may be displayed in a very small area of the page. For instance, a portal that is displaying a portlet in the MAXIMIZED window state might display

Figure 3-17. Image file serialized in Base64 format Now that you know how to write nontextual data by using XmlTextWriter, you re ready to see how to use XmlTextReader to read the document back.

As you can see in the handleLoad function, the findName method was called to get a reference to the TextBlock (called txt). This reference was then manipulated by adding an event handler to it.

4

The Click event handler of the Validate Document button contains the code shown in Listing 3-10.

This method allows you to create a new object for a specific purpose. In version 1.0 of Silverlight, only one object is supported: the Downloader object. The Downloader object allows you to download additional elements using asynchronous downloading functionality. It is very similar in scope to Ajax. It supports a number of properties, methods, and events that allow you to handle the download.

the other active portlets in the MINIMIZED state along the bottom edge of the portal page, like the Microsoft Windows taskbar. This behavior is up to the portal vendor to determine, and your portal may have settings to customize the minimization behavior. Our e-mail portlet might just display one line, saying 7 new messages or a similar message. Setting the portlet title to something descriptive can also be useful for portlets that display only their title.

You will need to add a <custom-window-state> element to the portlet.xml deployment descriptor for your portlet to support any portal-specific window states. For instance, your portlet may support a ONE_LINE window state that displays only one line of content, or it could support a dock window state, where each portlet renders a fixed-width, fixed-height window of content.

The Silverlight control provides a Downloader object (created using the createObject method) that allows you to get additional application assets in an asynchronous manner.

Listing 3-10. Reading Base64 Data private void button2_Click(object sender, EventArgs e) { XmlTextReader reader = new XmlTextReader(textBox2.Text); reader.WhitespaceHandling = WhitespaceHandling.None; while (reader.Read()) { if (reader.NodeType == XmlNodeType.Element) { if (reader.Name == "imagefile") { int length = int.Parse(reader.GetAttribute("size")); string filename = reader.GetAttribute("filename"); byte[] data = new byte[length]; string str = reader.ReadElementString(); byte[] imagedata = Convert.FromBase64String(str); MemoryStream ms = new MemoryStream(); ms.Write(imagedata, 0, imagedata.Length); Image image = Image.FromStream(ms); pictureBox1.Image = image; ms.Close(); } } } } The code creates an instance of the XmlTextReader class by passing the XML document we just created. It then starts reading the document. If the element name is imagefile, the code reads the two attributes filename and size. Based on the value of the size attribute, a byte array is created with that much capacity. The contents of the <imagefile> element are read by using the ReadElementString() method.

The portlet can determine which window state the portlet is currently being displayed in with the getWindowState() method on the PortletRequest interface. The getWindowState() method returns a WindowState object that represents either one of the standard window states or a custom window state:

It supports the following properties:

public WindowState getWindowState()