On Sun, 21 Aug 2005 02:29 pm, Jeremias Maerki wrote:
The API discussion thread around 2005-08-03 trailed off. I'd like
to revive it again because I feel that is something that needs to be
done.
Anybody against moving the CLI to a org.apache.fop.cli package?
For command line applications I
On 21.08.2005 09:08:48 Manuel Mall wrote:
On Sun, 21 Aug 2005 02:29 pm, Jeremias Maerki wrote:
The API discussion thread around 2005-08-03 trailed off. I'd like
to revive it again because I feel that is something that needs to be
done.
Anybody against moving the CLI to a
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUGĀ·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=36224.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED ANDĀ·
INSERTED IN THE BUG DATABASE.
On Sat, Aug 20, 2005 at 08:56:09PM +0200, Jeremias Maerki wrote:
I'm currently working on the PS renderer and as part of that I tried to
factor out more common code between the PDF and PS renderers. As a
result of that I already have some of the more important features
(borders and viewports)
What the hell is unfortunate about having a better idea? If that helps
make the code simpler and more easily understandable that's cool. And it
sounds like it does. I simply had to fix the problem somehow because I
want to get the first release out as soon as possible. And I was very
happy that
Jeremias Maerki wrote:
We've already broken API compatibility so changing packages (I'm
thinking think about org.apach.fop, removing apps) shouldn't be a big
deal before the first release.
I guess people would be more upset about FOPException moving
to a new package than any other API change.
Well, PDF and PostScript initially start with points, not with
millipoints. So you have to choose between one of the two coordinate
systems. I chose points because it generates smaller output files as the
millipoint coordinate system created too many zeros. I don't think this
will cause confusion.
Peter B. West wrote:
Fopsters,
Some of you may be aware of the activity going on around StAX. Java 1.6
(Mustang) was to have included JAXP 1.4, but that looks to be on hold
until Dolphin. However, StAX will be part of it, and soon enough, SAX
will be a dim memory.
Yeah, right. I give