> I saw the previous messages about the lack of individual row rendering 
> in qx.ui.table. I worked out a solution which I'm asking if it is worth 
> creating a patch:
> 
> 1) Make the tablePane accessible through qx.ui.table.Table (eg. through 
> getTablePane(metacolumn))
> 
> 2) Isolate the color and backgroundcolor style assignments to the row 
> elements into a method (ie. _rowStyleFunction). This will currently just 
> work for qx.ui.table.TablePane.USE_ARRAY_JOIN == false.
> 
> 3) Make this function setable through ie. table.Pane.setRowStyleFunction 
> by creating a property named rowStyleFunction of type function.
> 
> 4) Create a function which has the following format:
> 
> function(rowElem,cellInfo,tableModel) {
> }
> 
> Now you can style the rows depending on row values etc.
> 
> What do you think about that.
> 
> BTW: What is the fastest rendering model? Divs and nodeValue? Divs and 
> arrayJoin?

The right cell rendering strategy is not yet found. In my opinion cell 
rendering is still too slow. I have to do some more tests and tweaking 
around with the different strategies to get the whole stuff faster.

So this is not yet very stable and the rendering API may also change. It 
depends on how the fastest implementation works.

You can create a patch for this, but I can't promise that this solution 
will still work in the "final" Table implementation.




-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

Reply via email to