Re: Exporter comes finally to the scene :)

Hi Matzew, I followed the previous pattern of the excelExport component. So IMO, I think it is not odd for the component users. On Fri, Apr 18, 2008 at 7:41 PM, Matthias Wessendorf [EMAIL PROTECTED] wrote: On Fri, Apr 18, 2008 at 7:02 PM, Hazem Saleh [EMAIL PROTECTED] wrote: Hi Matzew,

Re: Exporter comes finally to the scene :)

On Sat, Apr 19, 2008 at 9:22 AM, Hazem Saleh [EMAIL PROTECTED] wrote: Hi Matzew, I followed the previous pattern of the excelExport component. So IMO, I think it is not odd for the component users. well, perhaps personal choice. Take this:

Re: Exporter comes finally to the scene :)

Agree with Matzew, action listener way looks better. It'll also help making it work with client side state saving. On Sat, Apr 19, 2008 at 11:11 AM, Matthias Wessendorf [EMAIL PROTECTED] wrote: On Sat, Apr 19, 2008 at 9:22 AM, Hazem Saleh [EMAIL PROTECTED] wrote: Hi Matzew, I followed the

Re: Exporter comes finally to the scene :)

Hi Team, Generated file is now depending on the mime type :) . Here is an example of usage) s:exporter for=your dataTable id fileType=XLS or PDF h:commandButton action= value=Export/ /s:exporter Thanks all for your suggestions. On Fri, Apr 18, 2008 at 5:45 AM, Hazem Saleh [EMAIL PROTECTED]

Re: Exporter comes finally to the scene :)

Hi Matzew, What is the problem with the previous syntax :- s:exporter for=your dataTable id fileType=EXCEL or PDF h:commandButton action= value=Export/ /s:exporter On Fri, Apr 18, 2008 at 6:57 PM, Matthias Wessendorf [EMAIL PROTECTED] wrote: Hi, I would instead of: s:exporter for=your

Re: Exporter comes finally to the scene :)

Hi, I would instead of: s:exporter for=your dataTable id fileType=EXCEL or PDF h:commandButton action= value=Export/ /s:exporter expect something like: commandButton... s:exporter/ /commandButton On Fri, Apr 18, 2008 at 6:49 PM, Hazem Saleh [EMAIL PROTECTED] wrote: Hi Team,

Re: Exporter comes finally to the scene :)

On Fri, Apr 18, 2008 at 7:02 PM, Hazem Saleh [EMAIL PROTECTED] wrote: Hi Matzew, What is the problem with the previous syntax :- s:exporter for=your dataTable id fileType=EXCEL or PDF h:commandButton action= value=Export/ /s:exporter I thought that the exporter would be an

Exporter comes finally to the scene :)

Hi Team, Iam pleased to tell you that I integrated both the excelExport and the pdfExport components into one single component called (exporter). Till now, it exports the contents of DataTables to EXCEL or PDF files. Here is an example of usage) s:exporter for=your dataTable id fileType=EXCEL or