Victor and fopdevs,
See below...
Victor Mote wrote:
Peter B. West wrote:
I'm pleased and surprised to hear that most of your design questions
have been answered. What scope of design are you talking about?
Ah, a good question. The scope of design on which I am currently working is:
1)
On 17.06.2003 01:38:14 Victor Mote wrote:
I did a dry run of the startup refactoring (Session, Document, etc.) work
yesterday this morning, and am satisfied that the concepts work.
Here are some comments:
1. I am going to start committing changes, hopefully this evening. Much of
the work
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20827.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
Victor and fopdevs,
See below...
Victor Mote wrote:
Peter B. West wrote:
As to the necessary conditions for committer status, Shall we take that
as read, darling?* The question remains, If a another developer
happens along who 1) is persuaded that alt.design is worthwhile, and 2)
sees the
Victor Mote wrote:
Glen Mazza wrote:
No response on the below questions from any committer,
and I'm concerned about the drop-off on the FOP-DEV
mailing list over the past few weeks (at an
extrapolated 170 emails on FOP-DEV for the month, this
would be our lightest month since Dec. 1999!)
Glen Mazza wrote:
--- Peter B. West [EMAIL PROTECTED] wrote:
I thought it was generally
agreed some time ago
that my work on properties should be integrated, for
the simple reason
that it is smaller and faster.
Exactly! Now you're talking my language--smaller and
faster--i.e., something
Hi Art,
Thanks for your response to my posting. I think a mode attribute to
indicate whether to preserve text or format is a good idea. Formatting
issues can often be cleaned up by post-processing on the generated file.
I'm already doing this to remove the extra new line feeds that I've had to
On 6/17/2003 6:37 AM, Illiano, Vincent wrote:
Thanks for your response to my posting. I think a mode attribute to
indicate whether to preserve text or format is a good idea.
Either that, or add a '-ascii' attribute similar to '-txt' or 'pdf'... I
realize this moves away from the 3 character
Trying to build HEAD using Ant under Eclipse, I get the following error
when the hyphenation build is attempted:
[serHyph] Fatal Error: source directory ./src/hyph for hyphenation files
doesn't exist.
[serHyph] BUILD FAILED: file:/home/pbw/workspace/fop-head/build.xml:453:
Jeremias Maerki wrote:
I'm a bit concerned that you call this startup refactoring where it's
really API redesign in the end, I think. And that's an important topic
where I would have expected you to ask for a go for it before starting
on this. Generally, JustDoIt (tm) is a good thing but this
Peter B. West wrote:
What's happened to the redesign? I have nothing to prove - you guys do.
I'll just keep working, publishing design notes for anyone who is
interested, and, when I get chunks of code working, I'll publish the
comparisons. Shall we put them to the vote? Will a vote
Peter B. West wrote:
Which modules? I'm not sure what you mean. The modularity of area
processing? The Rec gives an utterly spurious view of this. It has
been misleading developers since the drafts were first published, and
giving the impression that things can be neatly modularised.
Victor Mote wrote:
Peter B. West wrote:
Which modules? I'm not sure what you mean. The modularity of area
processing? The Rec gives an utterly spurious view of this. It has
been misleading developers since the drafts were first published, and
giving the impression that things can be neatly
vmote 2003/06/17 09:35:58
Modified:src/java/org/apache/fop/apps AWTStarter.java
CommandLineOptions.java CommandLineStarter.java
Driver.java FOInputHandler.java InputHandler.java
PrintStarter.java
Peter B. West wrote:
If I have not answered your question, yell out. I am quite happy to
keep on at this until you at least understand my thinking on this, even
if you don't agree with it.
But I will be keeping on with it tomorrow, as it is very late here.
Peter
--
Peter B. West
On 17.06.2003 17:10:19 Victor Mote wrote:
Jeremias Maerki wrote:
I'm a bit concerned that you call this startup refactoring where it's
really API redesign in the end, I think. And that's an important topic
where I would have expected you to ask for a go for it before starting
on this.
Hmm, I've given up running Ant under Eclipse. Gave me too much of a
headache and it works well for me outside of Eclipse.
But I think the trick is to use ${basedir} instead of . in build.xml
because Eclipse has to set the base directory so everything is ok. I
have done some other changes locally
Ok,
RC3a seems to be rather stable and the changes since then look
non-critical to me. What about doing the release now (read: next days)
(and maybe 0.20.5a later if we get more hyphenation patterns back)
Or should we make the changes proposed by Jörg (improved memory
usage with tables - see
Victor Mote wrote:
My humble apologies. What is the easiest way to roll it back? Is there an
automated way?
I rolled them back manually, and have committed the change. All should be
back as it was before, except the affected files are two revisions higher.
Victor Mote
On 17.06.2003 19:16:23 Christian Geisert wrote:
RC3a seems to be rather stable and the changes since then look
non-critical to me. What about doing the release now (read: next days)
+1
(and maybe 0.20.5a later if we get more hyphenation patterns back)
Don't count on that. :-(
Or should we
chrisg 2003/06/17 12:02:25
Modified:src/documentation/content/xdocs fo.xml
Log:
fixed typo
Submitted by: John Collins [EMAIL PROTECTED]
Revision ChangesPath
1.5 +1 -1 xml-fop/src/documentation/content/xdocs/fo.xml
Index: fo.xml
chrisg 2003/06/17 12:04:05
Modified:src/documentation/content/xdocs compiling.xml
Log:
small clarification
Revision ChangesPath
1.8 +2 -1 xml-fop/src/documentation/content/xdocs/compiling.xml
Index: compiling.xml
chrisg 2003/06/17 12:05:05
Modified:src/documentation/content/xdocs news.xml relnotes.xml
Log:
added news about 0.20.5rc3
Revision ChangesPath
1.11 +7 -0 xml-fop/src/documentation/content/xdocs/news.xml
Index: news.xml
--- Jeremias Maerki [EMAIL PROTECTED] wrote:
I'm a bit unhappy that you placed/left Session in
the apps package. I
would like to see the apps package deprecated as a
whole over time. I
would like a cli package that only contains the
stuff needed for the
command line and I'd like to have
Hi,
What's going on with the new logo?
Christian
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
Christian Geisert wrote:
RC3a seems to be rather stable and the changes since then look
non-critical to me. What about doing the release now (read: next days)
(and maybe 0.20.5a later if we get more hyphenation patterns back)
Or should we make the changes proposed by Jörg (improved memory
usage
Jeremias Maerki wrote:
I'm a bit unhappy that you placed/left Session in the apps package. I
would like to see the apps package deprecated as a whole over time. I
would like a cli package that only contains the stuff needed for the
command line and I'd like to have (wish, not a
Peter B. West wrote:
They can. They must. But then what happens to the idea that the FO
tree can be processed and refined before the layout occurs? If you are
The pieces that can be processed are. The pieces that cannot are deferred.
tree can be processed and refined before the layout
Victor Mote wrote:
I'm not opposed to Avalon, but I might be if I understood it.
Well, the good message about Avalon is that it can make
development for much easier.
The bad news is that if too much of Avalon is exposed in the
APIs intended for common usage, it will drive many potential
embedders
Jeremias Maerki wrote:
main FOP api in the org.apache.fop package.
org.apache.fop.api package?
J.Pietschmann
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
J.Pietschmann wrote:
Well, static data often interferes badly with multithreading.
We can use it in the CLI, but in the core which is intended to be
possibly embedded in multithreaded long running server environments
should it is best to avoid them. Even if you can arrange to
synchronize
vmote 2003/06/17 19:10:32
Modified:src/java/org/apache/fop/rtf/renderer RTFHandler.java
Log:
Add support for text-align in paragraphs.
Revision ChangesPath
1.5 +34 -2 xml-fop/src/java/org/apache/fop/rtf/renderer/RTFHandler.java
Index: RTFHandler.java
No problem with that.
On 17.06.2003 23:03:22 J.Pietschmann wrote:
Jeremias Maerki wrote:
main FOP api in the org.apache.fop package.
org.apache.fop.api package?
Jeremias Maerki
-
To unsubscribe, e-mail: [EMAIL
33 matches
Mail list logo
