Re: Big Small Doubt

2003-01-14 Thread VipinJ

But I think you're mixing things here. You're talking about a HTML
preview and you're talking about Excel. Is that linked together
somehow?
What are trying to accomplish?

The clients need the same report in 3 formats :
PDF
HTML
Excel

We are doing an MIS for a leading airline.
There are around 80 reports.
So what we are trying to do is to reuse the same FOP code to generate
HTML and Excel reports.

If this is not successful, we will have to add 80+80=160 new files.
:-))

So before giving them the estimate, we would like to see how much of
work is left

That is the intention.


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



RE: Big Small Doubt

2003-01-14 Thread Calero, Roberto
Title: RE: Big Small Doubt





My friend,


Please do not mix apples and oranges. You can generate XML data and from that point you can create whatever you want.
My personal approach would be:
- Create XML data to power your report
- Create 1 XSLT for creating CSV content, 1 for HTML and 1 for XSL-FO
- By using the above XSLT's now you are ready to create CSV and HTML content. Just run a simple XSLT transformation and you are done!! No need for using FOP whatsoever.

- For creating your PDF version you only need to run an XSLT transformation to create XSL-FO content then you can use FOP to create PDF content based on the previously generated XSL-FO content.

- If the layout of your report ever changes (but not the data to be displayed) you ONLY need to update your XSLT files instead of changing your app.

Roberto


-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, 14 January 2003 2:51 PM
To: [EMAIL PROTECTED]
Subject: Re: Big Small Doubt




But I think you're mixing things here. You're talking about a HTML
preview and you're talking about Excel. Is that linked together
somehow?
What are trying to accomplish?


The clients need the same report in 3 formats :
PDF
HTML
Excel


We are doing an MIS for a leading airline.
There are around 80 reports.
So what we are trying to do is to reuse the same FOP code to generate
HTML and Excel reports.


If this is not successful, we will have to add 80+80=160 new files.
:-))


So before giving them the estimate, we would like to see how much of
work is left


That is the intention.



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





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



Re: Big Small Doubt

2003-01-14 Thread Jeremias Maerki

On 14.01.2003 04:51:13 VipinJ wrote:
 
 But I think you're mixing things here. You're talking about a HTML
 preview and you're talking about Excel. Is that linked together
 somehow?
 What are trying to accomplish?
 
 The clients need the same report in 3 formats :
 PDF
 HTML
 Excel
 
 We are doing an MIS for a leading airline.
 There are around 80 reports.
 So what we are trying to do is to reuse the same FOP code to generate
 HTML and Excel reports.
 
 If this is not successful, we will have to add 80+80=160 new files.
 :-))

I know how you must feel with this prospect. Roberto Calero is right
about his observations in general, but I'd like to add a few points:
- Every report you generate also has to be in Excel format. I guess that
  means that every report is primarily a table of data. So all 80
  reports are probably more or less the same to a certain degree. What
  you could try is to find a common denominator on the data you have to
  generate the report. What I want to say is this: If you can come up
  with a common XML format (not XSL:FO, HTML or something like that,
  your own XML format) in which you can map every or most of your 80
  reports, then you might be in a position where you only have to write
  only one single XSLT for each output format (HTML, XSL-FO and
  CSV/Excel). I guess you already have to do a lot of copy/paste when
  you create your XSLT if you haven't sorted out a common stylesheet
  library already.
  
MIS report data (XML)
  +---+--- XSLT --- HTML
  +--- XSLT --- CSV (alternative 1)
  +--- XSLT --- Gnumeric XML --- Cocoon/POI --- XLS
  ¦  (alternative 2)
  +--- XSLT --- XSL-FO --- FOP --- PDF

See here for the Cocoon/POI stuff: 
http://xml.apache.org/cocoon/userdocs/serializers/xls-serializer.html
  
- You seem to be wanting to convert XSL-FO to Excel. I don't think this
  is a good idea. XSL-FO is made to define a page layout, not to
  generate a spreadsheet document. That's simply not what it was made
  for. It's better to do this before you get to XSL-FO like I suggest in
  the point above.

 So before giving them the estimate, we would like to see how much of
 work is left
 
 That is the intention.

I hope this helps along the way.

Jeremias Maerki


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



RE: Big Small Doubt

2003-01-14 Thread Calero, Roberto
Title: RE: Big Small Doubt





Exactly! Moreover, you can reuse your already existing XML file. The data is not the one changing but the format for generating the report and maybe the report layout (maybe depending on the selected format)

-Original Message-
From: Jeremias Maerki [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, 14 January 2003 5:54 PM
To: [EMAIL PROTECTED]
Subject: Re: Big Small Doubt




On 14.01.2003 04:51:13 VipinJ wrote:
 
 But I think you're mixing things here. You're talking about a HTML
 preview and you're talking about Excel. Is that linked together
 somehow?
 What are trying to accomplish?
 
 The clients need the same report in 3 formats :
 PDF
 HTML
 Excel
 
 We are doing an MIS for a leading airline.
 There are around 80 reports.
 So what we are trying to do is to reuse the same FOP code to generate
 HTML and Excel reports.
 
 If this is not successful, we will have to add 80+80=160 new files.
 :-))


I know how you must feel with this prospect. Roberto Calero is right
about his observations in general, but I'd like to add a few points:
- Every report you generate also has to be in Excel format. I guess that
 means that every report is primarily a table of data. So all 80
 reports are probably more or less the same to a certain degree. What
 you could try is to find a common denominator on the data you have to
 generate the report. What I want to say is this: If you can come up
 with a common XML format (not XSL:FO, HTML or something like that,
 your own XML format) in which you can map every or most of your 80
 reports, then you might be in a position where you only have to write
 only one single XSLT for each output format (HTML, XSL-FO and
 CSV/Excel). I guess you already have to do a lot of copy/paste when
 you create your XSLT if you haven't sorted out a common stylesheet
 library already.
 
MIS report data (XML)
 +---+--- XSLT --- HTML
 +--- XSLT --- CSV (alternative 1)
 +--- XSLT --- Gnumeric XML --- Cocoon/POI --- XLS
 ¦ (alternative 2)
 +--- XSLT --- XSL-FO --- FOP --- PDF


See here for the Cocoon/POI stuff: 
http://xml.apache.org/cocoon/userdocs/serializers/xls-serializer.html
 
- You seem to be wanting to convert XSL-FO to Excel. I don't think this
 is a good idea. XSL-FO is made to define a page layout, not to
 generate a spreadsheet document. That's simply not what it was made
 for. It's better to do this before you get to XSL-FO like I suggest in
 the point above.


 So before giving them the estimate, we would like to see how much of
 work is left
 
 That is the intention.


I hope this helps along the way.


Jeremias Maerki



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





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



Re: Big Small Doubt

2003-01-13 Thread Jeremias Maerki
FOP doesn't support Excel output. Have a look at POI instead. Also,
Cocoon can generate Excel output using POI.

http://jakarta.apache.org/poi/
http://xml.apache.org/cocoon/

On 11.01.2003 09:36:44 VipinJ wrote:
snip/
 Also please tell me whether there is any way to generate excel output
 using fop.


Jeremias Maerki


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



Re: Big Small Doubt

2003-01-13 Thread VipinJ

Hi,

We went through a few sites and found that we can write a xsl style
sheet defining the transformations for fop tags to html related tags.

The site is : http://www.renderx.com/fo2html.html

They say we can create html output from FOP. I am going to try that
out.

If that is successful, cant we do the following to get excel??

response.setContentType(application/vnd.ms-excel);

Is it possible??
Please advice

Warm Regards,
Vipin.




  
Jeremias Maerki 
  
[EMAIL PROTECTED]To: [EMAIL PROTECTED] 
 
enmail.ch   cc:
  
 Subject: Re: Big Small Doubt   
  
01/13/03 03:20 PM   
  
Please respond to   
  
fop-user
  

  

  




FOP doesn't support Excel output. Have a look at POI instead. Also,
Cocoon can generate Excel output using POI.

http://jakarta.apache.org/poi/
http://xml.apache.org/cocoon/

On 11.01.2003 09:36:44 VipinJ wrote:
snip/
 Also please tell me whether there is any way to generate excel
output
 using fop.


Jeremias Maerki


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






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



Re: Big Small Doubt

2003-01-13 Thread Jeremias Maerki

On 13.01.2003 12:36:03 VipinJ wrote:
 We went through a few sites and found that we can write a xsl style
 sheet defining the transformations for fop tags to html related tags.
 
 The site is : http://www.renderx.com/fo2html.html
 
 They say we can create html output from FOP. I am going to try that
 out.

That stylesheet has nothing to do with FOP. It's just plain XSLT. But I
guess, it will do what you need.

 If that is successful, cant we do the following to get excel??
 
 response.setContentType(application/vnd.ms-excel);

You can try, but I don't think you will succeed. The MIME type you
mention specifies an Excel document. Sending HTML to Excel will probably
result in garbage. Sending CSV as Stephan advised has a slightly higher
chance of success.

But I think you're mixing things here. You're talking about a HTML
preview and you're talking about Excel. Is that linked together somehow?
What are trying to accomplish?


Jeremias Maerki


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



Re: Big Small Doubt

2003-01-11 Thread Stephan Wiesner
[EMAIL PROTECTED] wrote:
Hi,
We have already done pdf reports using fo.
And we have delivered.
Now the clients need html preview and the pdf to be sent by email (For
low band width clients)...
Is there any way that we can reuse the code for pdf to generate html
or do we need to write html
FO can be transformed to HTML, I haven't done that myself though. Might 
be more effcient to directly transform your XML to HTML, though.


Also please tell me whether there is any way to generate excel output
using fop.

You can generate CSV files quite easily with an XSLT style. Depending on 
your XML sources, of course. Again, this should be much more efficient 
than generating FO and transforming that, especially, because you don't 
need any formating informations for the excel tables.

Stephan

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