Re: Antw: New gda-report's DTD

[Rodrigo Moya <rodrigo linuxave net>]

Derek Neighbors wrote:
> 
> > of course! the reports should be dynamic, not as the people in
> > metaphrast do. Although, we could have an option to store the output in
> > a file, so that it can be viewed later. But IMO the data should come
> > from the database on-the-fly.
> 
> GNUe is doing something where you have an xml template that holds how you
> want your report to look independent of data, basically what you would see
> in teh designer.
> 
> Then it would be ran through an engine to populate it with data.  Where it
> would create an xml file with the data and teh formating.  We were
> thinking of then running this through a customized Jade.  Which gives us
> postscript, pdf, html, rtf out of the box.
>
But this, IMO should go inside the report DTD. I haven't looked too much
in the report's DTD, but I suppose, Carlos, you're having this in mind,
or not?

What I really like is the generation of an xml file with the output
generated, and then converting it to several formats. Have you got
something done in GNUe about this?
 
> > > I don't know if this should be correct. Why you want to save the report
> > > query in a XML file? Why not save it only in RAM ?
> 
> I think we planned on saving the formatting on disk, and making saving the
> output optional.  So it would be all ram if you wanted, but if it was
> report people wanted over and over without data change you could save for
> archval.
> 
yes, there could be a sort of cache in the gda-report engine, and then
allow apps to get the cache copy or run the report again.

> With this architecture we could actual have basis for EDI exports and
> other B2B exchanges if done correctly.
> 
> > another option we could have. I think gnome-print generates Postscript,
> > so it should be quite easy to convert to other formats.
> >
> 
> Once again a gnome only solution is not very prudent.
> 
yes, on this I was wrong. The postscript should be generated, if so, in
the non-GNOME part.