I may want to store thousands of rows of 200 bytes or so each. Is this an issue (codewise)?
In limiting testing I got it to work well (pretty and everything!) with smaller sets of data and under Mozilla Firebird. Could not get it to work yet (identical page and data) under I.E.
Under any circumstances this project rocks!
For higher volumes of data it is necessary to implement selective rendering and probably paged data retrieval. Then you can go up to 10000-100000 rows. It may also require different approach to sorting (re-request properly sorted data from the server/database). Some of that will be implemented before the final release but its difficult to give any more details now.
I'm not sure what I'm going to do about it yet since my application needs to handle very wide datasets (I'm already paging the rows). If anyone else has overcome this hurdle I'd love to know how.
I switched to the JS array and while I notice an improvement in speed in general, IE 5.5 has trouble with a smaller dataset (63 columns). It renders the grid but then it sits there for a few minutes (I stopped watching after 2 full minutes) before it returns control. With Firefox and the larger dataset (150 columns) I don't even get prompted to cancel the script like I was before. So, the improvement is there and it's noticeable but it seems I'm worse off than before with IE 5.5 and wide datasets. Unfortunately, my target audience is IE 5.5 (corporate browser standard - ugh) so I am still stuck with this issue.
I'm curious, what is the widget doing after it displays the grid but before it returns control and displays the scrollbars? That seems to be the choke point, at least visually.
I can make my JS available if anyone wants to run tests.
Great product, though. I'm thoroughly impressed!
A page with just the grid (63 columns) yields better yet still unsatisfactory results - over 1.5 mins on the P2 and a little over 1 min on the P3. I'm not using any tables in my layout, the bulk of my page is the grid with a few navigation lists. Setting the grid size explicitly to 800x400 (using css) yields minimal, if any, improvement.
What I find odd is that the page will display very quickly with the viewable region but then there is a long delay before it finishes. As if it knows how much is visible and will display that portion while it finishes what's not immediately viewable. My users will not be satisfied to wait even 20 seconds for the grid to display, much less 2 minutes. They will have to live without the nice features of your grid for now.
I appreciate your efforts. Thanks! =)
On my P2 400MHz laptop using Firefox 1.0PR, the grid containing a very wide dataset renders in 8 seconds compared to 108 seconds using IE5.5 on the same computer. I guess that illustrates the deficiencies in IE's rendering engine? ;-)
This topic is archived.
Back to support forum
Version 2Looking for AW 2.6 ?
The old site is here.