I've just discovered this stunning set of tools and I'm more than impressed.
I've been trying to get some more mature display technologies in place where I am for a little while now. Our data display paradigm is an XML data islands approach with paginated tables providing a view over the data.
There are three things I need to understand before I can start showing proof of concepts of this technology:
2) Hidden Columns - Usually, the table is displayed to allow the user to make a choice and take the selected item off to a further page to work on it. This is done through a value stored in the first cell of each row. That column is hidden. For a direct translation, I'd be looking to mimic that behaviour using the AW Grid (although to be honest, I think there are other ways to achieve the same aim). Can we hide columns? If so, how does this affect column numbering?
3)ID Values - Related to point 2. Can rows have arbitrary values associated with them (that are not contained in the visible cells)? If so, how is this currently handled when using XML data islands?
I'm still ploughing on through the documentation so I might end up answering my own questions but if anyone out there already knows I'd appreciate the heads-up.
And again, nice work on these components.
Monday, October 17, 2005
Okay, I've just found the paging example. Cool. I know page-fu.
Monday, October 17, 2005
Obviously, I can see a key line with regards to displaying the data:
You can place that code anywhere on the page, and the grid control will be affected by it. In this example, I have 2 hidden columns, indeces 0 and 1. The other styles are used to size the other columns to the desired width. I used those for CompanyID and ContactID in a CRM application.
Wednesday, October 19, 2005
My life is complete... almost. And the answer was staring me in the face!
In my own hand-rolled table control I was of course using display:none to hide columns, rows and table bodies. I think in this case I was simply trying to look into the API and find the "hide this column flag". If only I'd looked at the style block I already had in the page...
Anyway, thanks for the tip. Given that I can now page through an xml data island, hide the "ID" column(s) and preserve some multi-select functionality I have the tools I need to improve the presentation (and speed I think) of the app I work on.
One last thing, in our current setup, users select multiple rows by checking a checkbox in the first column. I'd like to be able to retain that functionality so as to better sell the transition.