Rather than grabbing it from the TableComponent, can I suggest that
you just make it so that it accepts the same source object
(IBasicTableModel) and columns property, which would make it very easy
to use, since the syntax would be identical to the table which would
probably be declared directly next to it.  Or any 'collection of
beans' could be used along with a list of properties you want included
in the file. Use commons PropertyUtils and a list of maps will look
just like a list of beans, which makes things pretty convenient.

--sam


On 6/21/06, Martin Schnyder <[EMAIL PROTECTED]> wrote:
As part of a student project we developed a small component to export
(download) tabular data in the CSV format. We thought it might be useful for
others and described it in the Wiki
(http://wiki.apache.org/tapestry/ExportingCSVFiles). The code is also
available on Tassel.



The data to export has to be passed as lists of strings. I tried to extend
the export component so that it can fetch the data to export from an
existing Table component on a page but this seems to be a bit difficult
because the data that the table displays is only determined in the rendering
process of the Table component.



Martin






---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to