Thanks for replying to my first question and for the sample. I found out where I was going wrong and could correct it. The grid shows up correctly in IE now.
I am evaluating your components for our use so I will probably have more questions - here’s the first of them 
1. In terms of functionalty - are there any disadvantages of loading data via html vs xml? I understand that the first process will be a bit slow while displaying the page for the first time - but after that will they both be equivalent?
2. Is there a way of loading a grid by providing a url that returns a html page which contains only a plain table? (Or lists for that matter - for treegrid)
Thanks,
Tushar
- In terms of functionalty - are there any disadvantages of loading data via html vs xml?
Starting from dhtmlxgrid 1.6, both ways of loading support all main modes ( which means paging and smart rendering can be used with HTML datasource as well, which allow to load big datasets in such way )
The possible disadvantage of HTML datasource
- not all XML attributes can be mapped to HTML ( for example rowspans will not work while loading from HTML )
- dynamic loading not supported
- in case of complex modes, the init code may look more cryptic than in case of loading from XML
- treegrid can’t be loaded from HTML
After initial data parsing grid will work absolutly equally for both ways of data loading.
>> Is there a way of loading a grid by providing a url that returns a html page which contains only a plain table
There is no such built-in method, but it can be done with some custom coding - if this requirement is critical in your case, we can provide some kind of sample
this refers to: dhtmlx.com/docs/products/kb/inde … 290&a=7797
Yes, could you please provide a sample. I am using the Seaside framework within SmallTalk. This framework renders html only by default and it would be easier to integrate dhtmlx thru html…
The html that seaside produced is xhtml - will that help?
Thanks,
Tushar