Forgive my noob-ness but what is the difference between the WebDataGrid and the WebGrid?
Same for the WebDataTree and the WebTree.
Hello,
In a nutshell, WebDataGrid and WebDataTree are both built on top of our Aikido framework. Aikido is our own asp.net control framework that lets us build lighter, faster web conrols and uses ASP.Net AJAX for all ajax communication between client/server. You can read more about it here :
https://es.infragistics.com/help/aspnet/web-whats-new-in-2012-volume-1#wdg_whdg_excel_style_filtering
All the newer controls that we've been building for past year and a half are all based on top of this framework. We will be re-writing some of our existing controls and moving others over to our Aikido framework in the upcoming releases.
Hope this helps.
Taz.
For new screens when should one use the WebGrid vs WebDataGrid?
I've got screens built on the WebGrid now, should I invest the time to change them? Is there any way it's as simple as replacing the control on the page? Does all the AJAX behind the scenes including client side javascript and servers side events, methods and properties?
Thanks,
Frank
Hello Frank,
This is a very good question, and I am sure other folks might be interested to know it as well. To answer your question, can one simply replace a WebGrid out of their forms and place the WebDataGrid and it will work and behave just like the WebGrid? The answer is No. It all depends on how much work is being done within the WebGrid a part from displaying data. Just so that you know, when we were working on the WebDataGrid, we did want to have an easier transition path, if possible for users, but it turned out to maintain the ease of use and light architecture, we had to implement it differently.
So, I'd recommend you start off by checking the WebDataGrid features and see if they fulfill the grid requirements that you have on your pages. Once you know they do, you should then use the WebDataGrid for any future pages that you build, or any new applications you write. If there is a feature like Outlook GroupBy that the WebDataGrid doesn't support at the moment, and you need to have it on your page, then you can still use the WebGrid.
Finally, for the pages that has the WebGrid already and now you want to convert them to use WebDataGrid, then it can be done on a grid by grid basis, taking one at a time, hooking it up to your datasource, enabling the behaviors you want, and implement client and server activities.
I hope this explains what you were looking for.
Regards,
Thanks Taz, it does answer a lot of my questions. Maybe just a question or two more......
I've read some of the high level literature on the WebDataGrid. A few questions that aren't 100% clear.
Editing - can you edit and update using the WebDataGrid? Use Combo boxes?
You mentioned the Outlook Group By as not being supported. It my understanding that having multiple levels of data (bands) in the grid is also one of the features that are not supported.
Would it be a fair characterization that if your need is to use it like a basic spreadsheet, then WebDataGrid is a good solution. If some of the more wiz bang stuff like multi-level data, multi-level forms and grouping are needed, best to go with the WebGrid.
Frank,
For your combo box question, take a look at the following post:
http://forums.infragistics.com/forums/t/16126.aspx
At this moment, your assesment is correct that the WebDataGrid only supports flat data and for hierarchical data or GroupBy, WebGrid is the way to go. As the WebDataGrid is adapted and we get feedback/suggestions, we will be evaluating features that will go in the grid in future releases.
Is there some kind of decision guide or feature comparison between the UltraWebGrid and the WebDataGrid? That would make it easier to figure out whcih one to use and if one should be converted. Also, a conversion guide would be helpful to have a step by step path on conversion.
At the moment, we do not have such a comparison between the two or a conversion guide, but thanks for sharing your input with us. We will work on creating such a guide that will help differentiate the two on a feature level so that it is easier to see the key differentiators between the two grids .
In the mean time, if you are looking for anything specific, please feel free to post on the WebDataGrid forums and one of us should be able to get back to you.