.NET/Java PDF, Tiff, Barcode SDK Library

At the time of this writing, Microsoft does not produce a Silverlight plugin for Linux. However, an open source project called Moonlight offers a Linux-compatible version of Silverlight. This is based on the Mono project, an open source version of C# and the .NET Framework that can run on various non-Microsoft systems, including Linux. Microsoft has provided some assistance to the Moonlight project to help its developers achieve compatibility with the Microsoft Silverlight plugin. However, be aware that the Moonlight plug-in has historically lagged behind Microsoft s as we write this, Moonlight s current official release is two major version numbers behind Microsoft s. If you need to support Linux desktop machines with a Silverlight-based web application, this lag will limit the features you can use.

how to insert barcode in excel 2007, barcode activex control for excel 2007, free barcode addin for excel 2010, barcode inventory software excel, create barcode labels in excel 2010, create barcode in excel 2007 free, barcode in excel vba, excel barcodes 2010, excel barcode generator download, how to create barcodes in excel 2010,

Despite the very different environments in which WPF and Silverlight applications run, they have a great deal in common. Both use a markup language called Xaml to define the layout and structure of user interfaces. Their APIs are sufficiently similar that it is possible to write a single codebase that can be compiled for either WPF or Silverlight. There are critical concepts, such as data binding and templating, which you need to understand to be productive in either system. It s not accurate to say that Silverlight is a subset of WPF. However, this doesn t stop people from saying it; even Microsoft sometimes makes this claim. It s strictly untrue: WPF has many features that Silverlight does not and Silverlight has a few features that WPF does not, so neither is a subset of the other. But even if you allow a slightly woolly interpretation of the word subset, it s a misleading way to describe it. Even where both Silverlight and WPF offer equivalent features they don t always work in the same way. A few minutes with a decompilation tool such as Reflector or ILDASM makes it abundantly clear that WPF and Silverlight are quite different beasts on the inside. So if you are contemplating building a single application that works both in the browser as a Silverlight application and on the desktop as a WPF application, it s important to understand the point in the following warning.

While it is possible to write a single codebase that can run as both WPF and Silverlight code, this doesn t happen automatically. Silverlight code is likely to need some modification before it will run correctly in WPF. If you have existing WPF code, significant chunks of it may need rewriting before it will run in Silverlight.

Codebases that run on both WPF and Silverlight tend to use conditional compilation they use the C# preprocessor s #if, #else, and #endif directives to incorporate two different versions of the code in a single source file in the places where differences are required. Consequently, development and testing must be performed on Silverlight and WPF side by side throughout the development process.

The views and the standard model are flexible. You might not like some details in the application, so let s start looking at these details. You can start by setting some descriptive text in the headers: insert QStandardItems into the model by using setHorizontalHeaderItem(int, QStandardItem*) and setVerticalHeaderItem(int, QStandardItem*). Listing 5-5 shows the lines added to the main function to add horizontal headers. Listing 5-5. Adding headers to the standard item model model.setHorizontalHeaderItem( 0, new QStandardItem( "Name" ) ); model.setHorizontalHeaderItem( 1, new QStandardItem( "Phone number" ) );

In practice, it s not common to need to write a single body of code that runs in both environments. It might be useful if you re writing a reusable user interface component that you plan to use in multiple different applications, but any single application is likely to pick just one platform either WPF or Silverlight depending on how and where you need to deploy it. In this chapter, the examples will use Silverlight, but WPF equivalents would be very similar. We will call out areas in which a WPF version would look different. We will start by looking at one of the most important features, which is common to both WPF and Silverlight.

You can also implement this functionality in JavaScript by using the client-side control libraries in Atlas. You do this by creating Atlas controls that reference the underlying HTML controls, as well as using some new controls that you haven t seen before those that represent the bindings themselves. The best way to understand this is to examine the script itself in detail. First you need to create the controls that represent the checkboxes and the text box: var textBox = new Sys.UI.TextBox($('textBox')); var checkBoxBoolean = new Sys.UI.CheckBox($('checkBoxBoolean')); var checkBoxDisabled = new Sys.UI.CheckBox($('checkBoxDisabled')); Next you create the binding. This is a control in the Web namespace. You create it using the following code: var binding_1 = new Web.Binding(); Next you need to set up the properties for the binding, setting up the dataContext, dataPath, local property, transformer argument, direction, and transform type: