User (Old forums)MemberMarch 16, 2007 at 10:56 amPost count: 23064
Can i just say that this grid is really an excellent piece of software engineering, and something that microsoft should have implemented from the start!
How many people at xceed did it take to produce this component? And how long?
Imported from legacy forums. Posted by phoenix (had 3238 views)User (Old forums)MemberMarch 16, 2007 at 12:27 pmPost count: 23064
I was reading the what’s new tab (at <a href=”http://xceed.com/Grid_WPF_New.html”>http://xceed.com/Grid_WPF_New.html</a>) and it said:
“First commercial release, January 25, 2007. This is the world’s first commercially released data grid for Windows Presentation Foundation. Over <b>11,000 hours of work</b> were put into this initial version.”
Doesn’t say how many people, but wow at 11,000 hours of work!
Imported from legacy forums. Posted by vdo (had 433 views)Odi [Xceed]SpectatorMarch 16, 2007 at 1:32 pmPost count: 426
Thanks for the great comments. We indeed logged 11,000+ hours of work (design, implementation, styling, testing, samples, documentation) on v1.0 of the WPF data grid by the time it was released in January 2007. I’m not at liberty to say how many people it took to develop the grid, but I can tell you that it was our largest component development effort in our 12+ year history of making components. Our WPF team has since grown even larger.
>>…and something that microsoft should have implemented from the start!
Well, I’m certain they still feel the need to develop one, and will do so. The good news is, developers don’t have to wait anymore. In fact, it probably isn’t a good idea to ever use the default Microsoft grid. Here are the top 10 reasons why:
1.Xceed DataGrid for WPF is almost certain to go far beyond the bare essentials offered by any free Microsoft data grid. One reason for this is that companies like Xceed exist solely to produce components. As a result, the entire development team focuses on just that kind of software and on what a given component needs to be first in its class.
2. If you look at what happened with Microsoft’s .NET grid control (Windows Forms), you’ll notice that the .NET 1.1 grid was superceded by the .NET 2.0 DataGridView. With the new grid, you had to relearn a completely new object model and rewrite your code if you wanted to use it. On the other hand, if you look at what happened with updates to Xceed’s data grid (now at v3.5), the updates simply extended and improved on the original, with only minor breaking changes in its 5-year history. Intelligent choices during the initial design phase of Xceed’s Windows Forms grid meant that it was extensible—and extensible in the right ways—from the start. The same care was taken with Xceed DataGrid for WPF.
3. Commercial components almost always incorporate support for new interface styles much sooner than Microsoft does. Microsoft’s own components only started supporting the Office 2003 style in .NET 2.0, a couple of years too late. As Microsoft introduces new styles, you’ll either have to wait for Microsoft or someone else to style and code it, or do it yourself. Using Xceed’s DataGrid for WPF, you’ll have new styles ready to use right away.
4. The technical support offered with Xceed’s components is far more targeted and can make all the difference on the road to becoming proficient. And unlike with Microsoft’s support, there are no $245 single-call expenses: Xceed’s Vanguard subscription currently costs only $400 and gives you a year’s worth of priority support as well as frequent updates with advanced features.
5. Xceed DataGrid for WPF has a constantly and quickly evolving upgrade path: we’re well on our way with v1.1 and portions for v1.2 are also being worked on. With our Windows Forms grid, Xceed had released 8 major updates in the time it took Microsoft to improve their original .NET data grid by releasing DataGridView!
6. Microsoft itself uses Xceed grids in certain commercial and internal .NET applications! For example, Xceed Grid for .NET is used extensively in Microsoft Office Accounting Professional 2007. Xceed’s grid, chart and zip products have all the technical qualities Microsoft themselves internally require: the components are threat modelled, conform to FxCop rules, support accessibility, etc.
7. Typically, the first version of a Microsoft-made data grid lacks many important features, including fixed headers and footers, fixed columns, unbound support, row grouping, master-detail support, printing, input validation, individually extensible grid elements, and more. Xceed DataGrid for WPF v1.0 already has many of these features, and will have many more by the time Microsoft releases the first version of their grid (so far, no previews or news when that may be).
8. Becoming productive with Xceed DataGrid for WPF is easy because it comes with a wide variety of sample applications and includes excellent documentation, and there are already 700 posts in the product’s forums since its release less than 2 months ago.
9. When it will eventually be made available, Microsoft’s grid control for WPF will be new, with an unproven track record and an unknown potential for problems. By that time, Xceed’s datagrid for WPF will have undergone plenty of revisions, and have been used in the field by many customers.
10. Xceed’s data grid is available now, and from comments such as yours, it seems to be well received. Why wait?
Imported from legacy forums. Posted by Odi [Xceed] (had 458 views)
- You must be logged in to reply to this topic.