True ... BUT imagine the doc you need to set up for the end-users:
dependencies for tomahawk: ---list of jar-files--- if you want to use this component: add ---list of jar-files--- to the above list if you want ... and so on It might be easier to separate them into a entity and then document the individual entity's requirements... regards Alexander -----Original Message----- From: Martin Marinschek [mailto:[EMAIL PROTECTED] Sent: Thursday, August 24, 2006 2:58 PM To: MyFaces Development Subject: Re: Excel Export for Extended Datatable Well, the dependency wouldn't be a run-time-dependency, much more a compile-time-dependency. regards, Martin On 8/24/06, Jesse Alexander (KSFD 121) <[EMAIL PROTECTED]> wrote: > I think it would be a good idea to seperate such "heavy" components from > Tomahawk... > > One reason I see is that maybe such libraries can be "banned" by > corporate-managers. > Users in such corporations could still use tomahawk... Others without > the restriction > just throw a few more jar-files into their webapps and can use the > addon. > > regards > Alexander > > -----Original Message----- > From: Jurgen Lust [mailto:[EMAIL PROTECTED] > Sent: Thursday, August 24, 2006 10:14 AM > To: MyFaces Development > Subject: Re: Excel Export for Extended Datatable > > What library will you use to generate the Excel output? POI? > Should we really make this a dependency for Tomahawk? I think it would > be better to put it in a different subproject. Some kind of > ExportRenderKit, which could also contain PDF renderers using iText, for > example. > > Jurgen > > Op wo, 23-08-2006 te 17:44 +0000, schreef Martin Marinschek: > > Yeah, exactly. > > > > If that works, I'd fancy it a lot more! > > > > regards, > > > > Martin > > > > On 8/23/06, Cagatay Civici <[EMAIL PROTECTED]> wrote: > > > Hi Martin, > > > > > > Yes that seems like a better idea, so something like this one right? > > > > > > <t:datatable id="tableId"> > > > ... > > > ... > > > ... > > > </t:datatable> > > > > > > <s:excelExporter for="tableId" /> > > > > > > This would render a button and onclick exports the datatable data to > excel > > > format. > > > > > > Cagatay > > > > > > > > > On 8/23/06, Martin Marinschek < [EMAIL PROTECTED]> wrote: > > > > Hmm... My problem with our extended data-table is that it is much > > > > toooo overweight already. Couldn't we work with an extra component > > > > here, which has a for-attribute referencing a dataTable-component, > and > > > > displays the button and on click the excel data for the dataTable? > > > > > > > > regards, > > > > > > > > Martin > > > > > > > > On 8/23/06, Cagatay Civici <[EMAIL PROTECTED]> wrote: > > > > > Hi, > > > > > > > > > > I've created a new feature for the datatable that allows > exporting > > > presented > > > > > data to the excel format. > > > > > > > > > > Simply an excel button is placed on the datatable header and > clicking on > > > it > > > > > makes an ajax request, a popup is displayed and excel file is > presented. > > > > > > > > > > Following are the two screenshots; > > > > > > > > > > http://img206.imageshack.us/my.php?image=table17gs.jpg > > > > > http://img80.imageshack.us/img80/3568/table7xm.jpg > > > > > > > > > > This was a requirement needed in my last project, I think it > would also > > > be > > > > > useful if I integrate this for our extended datatable with an > attribute. > > > > > > > > > > What do you think? > > > > > > > > > > Cagatay > > > > > > > > > > > > > > > > > -- > > > > > > > > http://www.irian.at > > > > > > > > Your JSF powerhouse - > > > > JSF Consulting, Development and > > > > Courses in English and German > > > > > > > > Professional Support for Apache MyFaces > > > > > > > > > > > > > > > > -- http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces
