ComponentOne Silverlight FlexGrid 使用教程与示例

5星 · 超过95%的资源需积分: 10 62 浏览量更新于2024-07-27 2 收藏 1.38MB PDF 举报

"Silverlight的FlexGrid使用文档，包含详细例子" ComponentOne的FlexGrid是针对Silverlight开发的一个强大且灵活的网格控件，它提供了丰富的功能，用于在Silverlight应用程序中展示和操作数据。FlexGrid允许开发者创建具有复杂布局、多列、排序、过滤和编辑功能的数据表格，适用于各种业务应用需求。 FlexGrid的主要特性包括： 1. **高度可定制化**：FlexGrid允许开发者自定义列的宽度、类型和显示方式。可以设置列头的样式、单元格的模板，甚至可以添加自定义的编辑器和验证规则。 2. **多层数据绑定**：FlexGrid支持多种数据源，包括数组、集合、ObservableCollection以及任何实现INotifyPropertyChanged接口的对象。它可以动态地根据数据源的改变来更新显示。 3. **数据操作**：提供排序、过滤、分页、剪切、复制、粘贴和拖放功能，方便用户对数据进行操作。同时，这些操作可以通过编程方式控制，以适应特定的业务逻辑。 4. **性能优化**：FlexGrid采用虚拟化技术，只渲染屏幕上可见的行和列，提高了在大量数据下的性能表现。 5. **行和列冻结**：用户可以选择将重要的列或行固定在屏幕的一侧，以便在滚动时保持可见。 6. **分组和汇总**：FlexGrid支持数据的分组和汇总功能，可以快速对数据进行统计分析。 7. **打印和导出**：FlexGrid能够将网格内容导出为Excel、PDF或其他格式，同时也支持预览和打印功能。 8. **触摸友好**：对于触屏设备，FlexGrid提供了优化的触摸操作支持，使得在移动设备上使用也十分便捷。 9. **国际化的支持**：FlexGrid可以轻松地处理多语言环境，支持各种语言的列头和提示。 10. **API和事件**：FlexGrid拥有丰富的API和事件模型，开发者可以通过编程的方式实现对网格的深入控制和扩展。使用FlexGrid，开发者可以快速构建出功能强大的数据管理界面，而无需花费大量的时间和精力去编写底层的交互逻辑。同时，ComponentOne作为控件供应商，提供了完善的文档和示例代码，帮助开发者快速上手并解决实际问题。购买和保修方面，ComponentOne提供90天的产品质保，如果原始光盘（或磁盘）在购买后90天内出现制造缺陷，用户可以免费更换。90天后，如果需要更换，只需支付25美元的邮费和处理费。此外，ComponentOne的商标和服务标志均受到法律保护，所有其他商标均为各自所有者的财产。

Using FlexGrid for Silverlight

This document introduces the C1FlexGrid control for Silverlight and WPF. The control was introduced in the V2/2010

release of the corresponding ComponentOne Studios and has been substantially improved since then.

Overview

ComponentOne has a powerful DataGrid control for Silverlight and WPF. The DataGrid control has an object model

based on Microsoft's DataGrid control, which makes it easy for developers to migrate to the ComponentOne grid when

they need additional power and features such as built-in filtering, grouping, and much more.

So why add are we adding a new grid to the equation? There are two answers to that question:

1. The C1FlexGrid is one of the most popular and powerful grids for WinForms platform. We have a huge

number of users who rely on the C1FlexGrid's simple and flexible object model, and on its unique features that

include unbound mode, flexible cell merging, multi-cell row and column headers, and so on. Many of these

users requested a Silverlight/WPF version of the C1FlexGrid, and we are happy to comply.

2. The grids are very different. The C1FlexGrid is a simpler, smaller, lighter, grid. The DataGrid control is a

full-featured control with many features that are not available in the C1FlexGrid, including built-in grouping

UI, hierarchical support and more. You can pick the best grid depending on your application's requirements.

The C1FlexGrid is light in size (the Silverlight version is only about 100k) and also in dependencies (none other than

the basic .NET assemblies for the corresponding platform). Despite its small size, the grid does include all the features

you would expect from a professional grid and a few more (great speed, excel-style editing, easy styling, multi-cell row

and column headers, cell merging, and much more).

The C1FlexGrid is available for Silverlight and for WPF. This article describes the control and illustrates by walking

you through a comprehensive sample that covers most of the functionality in the control. The sample is called

MainTestApplication.

There are two versions of the sample, one for Silverlight and one for WPF. They share most of the code, which illustrates

how easy it is to develop desktop (WPF) and web (Silverlight) versions of applications using a single code base.

Most pages in the MainTestApplication application show two grids side by side. The grid on the left is always a

C1FlexGrid. The one on the right is the Microsoft grid (DataGrid in the Silverlight version WPFToolkit grid in the

WPF version). The Microsoft grids are shown only for comparison.

Creating the C1FlexGrid

Adding a C1FlexGrid control to your application requires the exact same steps as adding any custom control. There's

nothing special about the C1FlexGrid in this regard. You start by adding a reference to the C1FlexGrid assembly to

your project, and then add the control using XAML:

<UserControl x:Class="MainTestApplication.MainPage"

xmlns:c1="http://schemas.componentone.com/winfx/2006/xaml"

<c1:C1FlexGrid/>

</Grid>

</UserControl>

Of course, you can also create the C1FlexGrid in code if you prefer:

var fg = new C1.Silverlight.FlexGrid.C1FlexGrid();

LayoutRoot.Children.Add(fg);

Populating the grid

Once you have added the grid to your application, you will normally populate it using the ItemsSource property (like

most other grids). The ItemsSource property expects an object that implements the IEnumerable interface, but in most

cases you will work at a slightly higher level and use an object that implements the ICollectionView interface.

The ICollectionView interface is the main data-binding interface in Silverlight and WPF (in WinForms, that role was

played by the IBindlingList interface).

ICollectionView is a rich interface. In addition to enumerating the data items, it provides sorting, filtering, paging,

grouping, and currency management services.

Silverlight provides a PagedCollectionView class that implements the ICollectionView interface. The

PagedCollectionView constructor takes an IEnumerable object as a parameter and automatically provides all

ICollectionView services. WPF provides similar classes, such as ListCollectionView.

For example, to display a list of customer objects in a C1FlexGrid Silverlight application, you would use code such as

this:

List<Customer> list = GetCustomerList();

PagedCollectionView view = new PagedCollectionView(list);

_flexGrid.ItemsSource = view;

You could also bind the grid directly to the customer list, of course. But binding to an ICollectionView is usually a

better idea because it retains a lot of the data configuration for the application, and that can be shared across controls.

If many controls are bound to the same ICollectionView object, they will all show the same view. Selecting an item in

one control will automatically update the selection on all other controls. Filtering, grouping, or sorting will also be

shared by all controls bound to the same view.

The code above causes the grid to scan the data source and automatically generate columns for each public property of

the items in the data source. Automatically created columns can be customized using code, you may disable the

automatic column generation altogether and create the columns yourself, in code or in XAML.

For example, the XAML below disables the automatic column generation and specifies the columns in XAML instead:

<fg:C1FlexGrid x:Name="_flexiTunes"

AutoGenerateColumns="False" >

<fg:C1FlexGrid.Columns>

<fg:Column Binding="{Binding Name}" Header="Title"

AllowDragging="False" Width="300"/>

<fg:Column Binding="{Binding Duration}"

HorizontalAlignment="Right" />

<fg:Column Binding="{Binding Size}"

HorizontalAlignment="Right" />

<fg:Column Binding="{Binding Rating}" Width="200"

HorizontalAlignment ="Center" />

</fg:C1FlexGrid.Columns>

</fg:C1FlexGrid>

This is similar to the XAML you would use to accomplish the same task using the Microsoft DataGrid or the original

ComponentOne DataGrid controls:

<ms:DataGrid Name="_msSongs"

AutoGenerateColumns="False" >

<ms:DataGrid.Columns>

剩余62页未读，继续阅读

yang406952967

粉丝: 2
资源: 22

ComponentOne Silverlight FlexGrid 使用教程与示例

C1.Win.C1FlexGrid.2.dll

ComponentOne Studio for Silverlight 2013 v1 2/3

Silverlight 常用dll

ComponentOne Studio for Silverlight 2013 v1

ComponentOne OLAP for Silverlight2012 v3 2/3

ComponentOne OLAP for Silverlight2012 v3 3/3

ComponentOne Studio for Silverlight 2012 v3 2/3

ComponentOne Studio for Silverlight 2012 v3 1/3

ComponentOne OLAP for Silverlight2012 v3 1/3

ComponentOne 2012 V2 Studio for Silverlight 3/3

最新资源