Comments on: Using Nested YUI 2 DataTables for Row Expansion

By: Amitabh

Amitabh — Mon, 07 Jun 2010 12:19:46 +0000

Solved NDT using XHRDataSource :-)

By: Amitabh

Amitabh — Mon, 07 Jun 2010 11:13:26 +0000

Hi!!

Can you please share an example that uses XHRDataSource. Have tried but its just not calling the source file for json data.

Regards.

By: TSmith

TSmith — Tue, 06 Apr 2010 19:38:31 +0000

Nicely done Satyam, I will be reviewing your technique and samples from your website in order to implement this in my app.

Thanks!

By: Dev

Dev — Tue, 30 Mar 2010 10:34:42 +0000

Hi Satyam

Can you please share the nested data table example that used XHRDataSource

By: Shripad

Shripad — Tue, 30 Mar 2010 03:12:56 +0000

I am trying to use nested table and i am creating the JSON object from java side.But data is not rendering on the web page.Following is the JSON response i am able to see from firebug

({“query”:{“count”:”2″,”created”:”2010-03-30T02:43:40Z”,”lang”:”en-US”,”updated”:”2010-03-30T02:43:40Z”,”uri”:”http://localhost:8080/YUI/yuiAction.do?format=json&debug=true&q=”,”diagnostics”:{“publiclyCallable”:”true”,”url”:{“execution-time”:”356″,”content”:”http://us.music.yahooapis.com/release/v1/list/artist/269863?start=1&count=2″},”user-time”:”378″,”service-time”:”356″,”build-version”:”5275″},”results”:{“Release”:[{"id":"209601444","releaseYear":"2009","title":"Classic [Spectrum Audio]“,”url”:”http://new.music.yahoo.com/abc/albums/classic-spectrum-audio–209601444″}]}}})

By: true false maybe » DataTable in yer DataTable

true false maybe » DataTable in yer DataTable — Sat, 20 Mar 2010 00:28:16 +0000

[...] http://www.yuiblog.com/blog/2010/03/17/using-nested-datatables-for-row-expansion/ [...]

By: John Lindal

John Lindal — Fri, 19 Mar 2010 01:50:05 +0000

Touché.

We’re actually using this extension, so I have an incentive to fix the problems. I submitted one patch for IE, and pagination is next.

By: Satyam

Satyam — Thu, 18 Mar 2010 22:17:33 +0000

John
It was a conditional statement, not an absolute one. My example has issues and they are explicitly stated. It is a matter of disclosure, under certain conditions it is acceptable.

The problem is that there is no easy fix for the issues in that example so you are very limited in what you can do. All 17 occurrences of references to the sectionRowIndex property have to be taken care of as well as the opposite assumption, that there is a correspondence in between the record and the row, and those are harder to find out since there is no single keyword to look for, and I would assume there are just as many.

Anyway, it was you who asked about that example, don’t complain about my reply.

By: John Lindal

John Lindal — Thu, 18 Mar 2010 20:24:11 +0000

I wholeheartedly disagree with your statement that the example shouldn’t be there, but I do agree that it needs some more work. I have some fixes that need to be applied to the code and will try to get them in soon.

By: Satyam

Satyam — Thu, 18 Mar 2010 13:49:57 +0000

John
I have and it really doesn’t work that good. For one, DataTable uses the sectionRowIndex property of TR elements for a lot of things, my editor counts 17 occurrences of it in datatable.js. All of those come out wrong with extra rows added as that example uses. You cannot insert rows into DataTable and expect it to fully work. As soon as you add very little functionality, the whole thing breaks down.

Besides, as I mention in the text, nesting one datatable within another brings up some problems such as styles propagating down from master table to child table or events bubbling up from child to master. The nested datatables cannot be in the same branch of the DOM as the master table, thus, they have to be separate and just positioned to look right, but not actually related hierarchically as far as the DOM is concerned.

Without explicitly stating all those issues, that example should not even be there.

Also, please see: http://yuilibrary.com/projects/yui2/ticket/2528595