days, and I will
fix the encoding at the same time, unless there is a more urgent need.
Peter
--
Peter B. West [EMAIL PROTECTED] http://www.powerup.com.au/~pbwest/
"Lord, to whom shall we go?"
-
To unsubscribe,
J.Pietschmann wrote:
Arved Sandstrom wrote:
Considering that our new chief executive is Greg Stein, I'd be
surprised if
this isn't on the horizon. :-)
Gosh! Can we have it before Christmas? :-)
2003?
Good to see you back, Joerg. Good holiday?
Peter
--
Peter B. West [EMAIL
rough the cracks. Some such approach may be a
good idea, but I would be loathe to call it EventHandler. The whole
point about pull parsing is to move away from event handling. I would
think of these more as methods with parameters like "optional", "single"
or "multi
branch. Another possibility. especially
for directories are not going to be merged back into the HEAD and whose
content is largely the same, is to merge them out from HEAD into maint.
Not having followed the details of the proposed changes very closely,
I would have to look at individual cases.
to either 1) only want them moved in one branch (probably not
desirable), or 2) move them twice, once for each branch. Especially on the
maintenance branch, you will want to be careful to get the new files tagged
with the maintenance branch tag.
I don't think anyone here knows all of the implica
Jeremias Maerki wrote:
Moving around directories on the server so we don't lose history on
files. See my proposal on directory structure reorganization, ex.
moveing src/org to src/java/org.
On 27.11.2002 16:19:26 Peter B. West wrote:
Jeremias Maerki wrote:
BTW: Anybody around with exper
ing
on the redesign so that i will work on them first.how
about keep properties?
Sri,
You have picked just about the toughest layout problem of them all. If
you want to work on this one, you have to get involved in redesign, with
either the HEAD line or alt.design.
Peter
--
Peter B. West [EMAIL
t
the FOs, to apply those values. Alt-Design takes the second view.
Peter
--
Peter B. West [EMAIL PROTECTED] http://www.powerup.com.au/~pbwest/
"Lord, to whom shall we go?"
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
Jeremias Maerki wrote:
BTW: Anybody around with experience in CVS surgery???
Not really, but what do you want to do?
Peter
--
Peter B. West [EMAIL PROTECTED] http://www.powerup.com.au/~pbwest/
"Lord, to whom shall
xhausted." But, a pull model can be grafted onto a push model by implementing what amounts to a specialized buffer of the pushed data that accepts pull queries...no?
Which is what I have done.
Peter
--
Peter B. West [EMAIL PROTECTED] http://www.powerup.c
Oleg Tkachenko wrote:
Peter B. West wrote:
I don't believe is is only a matter of style. I think the detrimental
effects of push for general programming are glaringly obvious.
It's just event-driven processing, how it could be detrimental?
I may have referred to Dijkstra (R.
it is to answer the mailing lists, we might be able to eliminate some of the
mailing list traffic.
And if it is not automatic, an explanation of the easier than before
manual process would be useful.
Peter
--
Peter B. West [EMAIL PROTECTED] http://www.powerup.com.au/~pbwest/
"Lord, to wh
Oleg Tkachenko wrote:
Peter B. West wrote:
Why is it easier for developers to use? Is it because the API is less
complex or more easily understood? Not really. As you point out, the
SAX API is not all that complex. The problem is that the processing
model of SUX is completely inverted
W. Eliot Kimber wrote:
Oleg Tkachenko wrote:
Peter B. West wrote:
I have debugging my FO tree building be running it against various
example fo files. Of the three I have used so far, I have found
problems with two.
./docs/examples/pagination/allregions.fo has the problem that I
ar as XSL-FO is concerned. It is a system-color(), however,
as far as FOP is concerned.
I assume that these errors are not deliberate, and that I should clean
them up as I go.
Peter
--
Peter B. West [EMAIL PROTECTED] http://www.powerup.com.au/~pbwest/
"Lord,
od reasons why the layout is not susceptible to the same
simple solution.. I do have a number of ideas to contribute, and when
the web site is restored I will be referring to some of the notes I have
made and posted there.
Peter
--
Peter B. West [EMAIL PROTECTED] http://www.powerup.com.au/~pbwe
hen I talk about the layout engine, I have in mind the process that
builds the layout tree, and moves chunks as they are completed into the
area tree.
Peter
--
Peter B. West [EMAIL PROTECTED] http://www.powerup.com.au/~pbwest/
"Lord, to whom shall we go?"
--
Oleg Tkachenko wrote:
Peter B. West wrote:
I like pull parsing model in general, but how do you manage with not
such strict content model as fo:root have, e.g. fo:block with
(#PCDATA|%inline;|%block;)* ?
How about:
FoXMLEvent ev = expectStartElement
Oleg,
...
Oleg Tkachenko wrote:
Peter B. West wrote:
taking a very isolated path. My motivation can be summed up in the
slogan SAX SUX. I couldn't understand why anyone would persist with
it for any complex tasks, e.g. FOP.
Actually I cannot say I fully agree with this, because I
currently working through the fo examples. Once
that is done, I will have to fill in any blanks.
TODO:
Corresponding properties.
Complete PropertyValue validation.
Comprehensive testing.
Complete provision for markers in all FO classes.
Other things I can't think of now.
More later on the
= expectCharacters();
return ev;
}
Peter
--
Peter B. West [EMAIL PROTECTED] http://www.powerup.com.au/~pbwest/
"Lord, to whom shall we go?"
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
Peter
--
Peter B. West [EMAIL PROTECTED] http://www.powerup.com.au/~pbwest/
"Lord, to whom shall we go?"
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
Keiron Liddle wrote:
Hi Developers,
I propose we have a vote for Victor to become a committer.
+1
Peter
--
Peter B. West [EMAIL PROTECTED] http://www.powerup.com.au/~pbwest/
"Lord, to whom shall we go?"
-
To u
ument is called two times.
--
Peter B. West [EMAIL PROTECTED] http://www.powerup.com.au/~pbwest/
"Lord, to whom shall we go?"
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
Keiron Liddle wrote:
On Tue, 2002-11-19 at 15:07, Peter B. West wrote:
If possible I think we should try to avoid making multiple passes since
it can lead to loops etc. The table layout auto will need at least two
passes but this should be possible using the layout managers.
Is that a
Jeremias Maerki wrote:
Hi Peter
I should have done that earlier because about at the same time I updated
to Xerces 2.2.0, Xerces 2.2.1 was published and I knew it was a bugfix
release.
On 19.11.2002 15:18:45 Peter B. West wrote:
I'm glad to see that you have upgraded Xerces to 2.2.1. I
out what was going on.
This may fix some problems that have been attributed to Xalan.
Peter
--
Peter B. West [EMAIL PROTECTED] http://www.powerup.com.au/~pbwest/
"Lord, to whom shall we go?"
-
To unsubscribe,
ratulated. Are
you there, Tony?
Peter
--
Peter B. West [EMAIL PROTECTED] http://www.powerup.com.au/~pbwest/
"Lord, to whom shall we go?"
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
ties,
I will design and implement the layout engine, and it *will* work.
Before then, however, the whole exercise may have been rendered academic
by Sun.
Peter
--
Peter B. West [EMAIL PROTECTED] http://www.powerup.com.au/~pbwest/
"Lord, to whom shall we go?"
--
a good job (or at
least can't *know* that we did) until we get the entire page-sequence read
anyway, which means that we might be better off reading it in before we
start & then taking the second approach. FWIW. Actually, I hope to learn a
lot from Keiron's repli
was getting ready to post some details about this, but I wanted to
finish the creation of the FO objects first. I will now post them this
weekend.
Peter
--
Peter B. West [EMAIL PROTECTED] http://www.powerup.com.au/~pbwest/
"Lord, to whom shall we go?"
r in the german-speaking part of the world
. . .
I might be interested too, depending on where and when. I am subscribed to
party@.
--
Peter B. West [EMAIL PROTECTED] http://www.powerup.com.au/~pbwest/
"Lord, to whom shall we go?"
---
e.g.,
why you don't know when the end of a page has been reached. A shortcut
to an understanding of such things would be very useful.
Peter
--
Peter B. West [EMAIL PROTECTED] http://www.powerup.com.au/~pbwest/
"Lord, to whom shall we go?"
-
Kevin O'Neill wrote:
On Tue, 2002-11-12 at 11:21, Peter B. West wrote:
"I like it" is the acid test; for me, of all code, but in particular for
open source. Open source may be driven by many things, but money is not
one of them. Pleasure is, and is high on the list. In spi
ce may be driven by many things, but money is not
one of them. Pleasure is, and is high on the list. In spite of that,
OS generates vast amounts of high-quality software. Go figure.
Peter
--
Peter B. West [EMAIL PROTECTED] http://www.powerup.com.au/~pbwest/
"Lord, to whom shall we g
gave me much food for thought. So I'll rephrase the question: what, if
anything, is the cost of using the interface instead of the implementation?
Peter
Peter B. West wrote:
> Jeremias,
>
> I have no objection at all, as long as it costs nothing. It is free,
> isn't i
Oleg,
Thanks for that. I have noticed that there are quite a few people who
do respond on dev-user, in addition to yourself and Keiron, which is why
I wondered whether Joerg was making a specific request. I eventually
concluded he was not.
Peter
Oleg Tkachenko wrote:
Peter B. West wrote
hmann wrote:
I'm on vacancy from tomorrow on for a bit more than three
weeks, so I can't do this myself.
Who will take care of the unanswered questions while I'm
offline? Oleg?
--
Peter B. West [EMAIL PROTECTED] http://www.powerup.com.au/~pbwest/
"
Rhett Aultman wrote:
... as soon as I'm done taking the GRE tomorrow (wishes of luck appreciated)...
Consider them wished.
Peter
--
Peter B. West [EMAIL PROTECTED] http://www.powerup.com.au/~pbwest/
"Lord, to whom s
f the mind - but I'll
remember the offer.
Peter
--
Peter B. West [EMAIL PROTECTED] http://www.powerup.com.au/~pbwest/
"Lord, to whom shall we go?"
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
ed subtree, and reestablish it as a "pending".
These things just sound interesting - sexy, even, now that you mention
it - though I doubt their sex appeal was a strong motive for creating
them. The "raw" documentation doesn't really give much of a feel for
their potentia
Provided, of course, that he controls his CRCRs.
Peter B. West wrote:
+1
--
Peter B. West [EMAIL PROTECTED] http://www.powerup.com.au/~pbwest/
"Lord, to whom shall we go?"
-
To unsubscribe, e-mail: [EMAIL PROT
+1
Keiron Liddle wrote:
Hi Developers,
I suggest we have a vote for Oleg to be a committer. If Oleg accepts
then he can get on with making FOP great!
--
Peter B. West [EMAIL PROTECTED] http://www.powerup.com.au/~pbwest/
"Lord, to whom shall
seen
this habit in a number of places and not only by Keiron! I've made it a
habit to follow this pattern
...
--
Peter B. West [EMAIL PROTECTED] http://www.powerup.com.au/~pbwest/
"Lord, to whom shall we go?"
---
ts of using WeakHashMaps instead of HashMaps?
--
Peter B. West [EMAIL PROTECTED] http://www.powerup.com.au/~pbwest/
"Lord, to whom shall we go?"
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
eeds a bit more investigation. As I have said, I have recently
seen spurious CRLF endings in checked-out files.
Peter
--
Peter B. West [EMAIL PROTECTED] http://www.powerup.com.au/~pbwest/
"Lord, to whom shall we go?"
---
've started a little check-program (in Java) that
analyzes files on their line endings using regex-matching. I think, I'll
expand that to a little project including command-line app, ant-task etc.
--
Peter B. West [EMAIL PROTECTED] http://www.powerup.com.au/~pbwe
form, and is contra-indicated on
binary files, while '-kb' is contra-indicated on text files, on which
you definitely want expansion.
These values, incidentally, come from RCS, and can be read about with
'man co'.
Unless something has changed recently, CRLF will h
dea how to...
1. identify files not having correct linevindingstlithoutckaving de opendeach an>every file?
2. enforce correct line endings?
--
Peter B. West [EMAIL PROTECTED] http://www.powerup.com.au/~pbwest/
"Lord, to whom shall we go?"
---
en
we have a split in the project and that wouldn't be good.
Between all committers. I meant that closer liaison between committers
is a good thing. All committers then have a more lively appreciation of
what the others are up to.
Peter
--
Peter B. West [EMAIL PROTECTED] http://www.pow
sible. A
lot is already there. We can build on that.
I concur with Oleg here. (Yes, really.) However, there are people who,
as Victor has said, who find the all-or-nothing approach extremely
difficult. If they can come up with practical ways of easing such
difficulties, their suggest
Victor Mote wrote:
Peter B. West wrote:
Re some recent questions on this topic. As I understand it, creating a
branch in the tree off an existing file set simply involves tagging the
set of files with the new branch tag. From that point on, as long as a
particular file remains unchanged, a
Keiron,
Re your latest commits, could you comment on what you had to do to "make
sure area tree is serializable"? I have been curious about aspects of
the serialization of trees for some time now.
Peter
--
Peter B. West [EMAIL PROTECTED] http://www.powerup.com.au/~pbwest/
&quo
ll be relative to these tag points.
It's kinda messy, but it might just be feasible.
Peter
--
Peter B. West [EMAIL PROTECTED] http://www.powerup.com.au/~pbwest/
"Lord, to whom shall we go?"
-
To unsubscribe, e-mail: [
problems.
My two minutes are up.
Peter
--
Peter B. West [EMAIL PROTECTED] http://www.powerup.com.au/~pbwest/
"Lord, to whom shall we go?"
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
to benefit from a number of recent
developments which I have no intention of writing myself.
If you took offence from the "short attention span comment", I am sorry.
No such offence was intended. The comment concerns the general
approach to development that you mentioned.
Peter
--
(and kudos) while the new layout engine languished for want of
love and attention. It's a real concern, made all the more real by the
tenor of these suggestions.
Peter
--
Peter B. West [EMAIL PROTECTED] http://www.powerup.com.au/~pbwest/
"Lord, to whom shall we go?"
-
FrenchName CDATA #REQUIRED
>
xml-lang.xsl is used to generate CountryLanguageScript.java, the class
against which all new CountryType, LanguageType and ScriptType
PropertyValues are validated.
Peter
--
Peter B. West [EMAIL PROTECTED] http://www.powerup.com.au/~pbwest/
"Lord, to whom sha
ick with the existing
framework and not be a ground-up reworking. The methodological changes
now being discussed are only possible because of that decision, strongly
argued by Keiron, I believe.
Peter
--
Peter B. West [EMAIL PROTECTED] http:/
Maybe the simplest is to move the old layout to the trunk, get that
working and put the new layout in a branch. But it needs to be agreed
upon.
How difficult would this be? Would it be you who did most of this, or
could you successfully direct others to assist?
Peter
--
Pet
&w=2
http://marc.theaimsgroup.com/?l=fop-dev&m=102011250524180&w=2
--
Peter B. West [EMAIL PROTECTED] http://www.powerup.com.au/~pbwest/
"Lord, to whom shall we go?"
-
To unsubscribe, e-mail: [EMAIL PRO
messages that at
least one of these is called "FOP_0-20-0_Alt-Design".
How can I find out about all of the branch names? Which "branch" is the
default trunk? The upcoming 0.20.5 maintenance release?
--
Peter B. West [EMAIL PROTECTED] http://www.
that is to apply future changes directly.
Have a look and let me know if anything needs fixing.
Peter
--
Peter B. West [EMAIL PROTECTED] http://www.powerup.com.au/~pbwest/
"Lord, to whom shall we go?"
-
To unsubscri
te in english. :-)
I'm sorry Jeremias. It was a joke. See bugger and fop in a nearby
dictionary.
--
Peter B. West [EMAIL PROTECTED] http://www.powerup.com.au/~pbwest/
"Lord, to whom shall we go?"
-
To unsubsc
gnitude for a while (months+) since this one catches
all of the mistakes that my team is likely to make.
If anyone wants to take on the task of extending the schema with
schematron asserts. Feel free.
--
Peter B. West [EMAIL PROTECTED] http://www.powerup.com.au/~pbwest/
"L
7;m planning to write a testcase that runs multiple FOPs
simultaneously to find out where the buggers are.
Jeremias,
What kind of FOPs are we talking about?
--
Peter B. West [EMAIL PROTECTED] http://www.powerup.com.au/~pbwest/
"Lord,
and clearly how it works, but if you
sure it's a better way to validate and wont overhead processing, I
believe you :)
So, do we decide to go this way? Other opinions?
This is what is already happening in alt.design, but the structure is
very different from the existing processing structur
Jeremias wrote:
> I'm planning to write a testcase that runs multiple FOPs
> simultaneously to find out where the buggers are.
Jeremias,
What kind of FOPs are we talking about?
Peter
--
Peter B. West [EMAIL PROTECTED] http://www.powerup.com.au/~pbwest/
"Lord, to
have, e.g. fo:block with
(#PCDATA|%inline;|%block;)* ?
This basically says, "Anything," so it is also easy. Just get the next
event and apply any special processing constraints, like checking for
footnote and float in "out-of-line" areas.
Peter
--
Peter B. West [EMAIL PROTECTED]
tylesheet (or even
into java class using xalan's xsltc) during fop building and use it as
optional sax filter at run-rime.
--
Peter B. West [EMAIL PROTECTED] http://www.powerup.com.au/~pbwest/
"Lord, to whom shall we go?"
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
t and so I propose the end of the first week of november
> as target date for the release candidate.
Does your wife know about this?
Peter
--
Peter B. West [EMAIL PROTECTED] http://www.powerup.com.au/~pbwest/
"Lord, to whom shall we go?"
-
pport, if I recall
> properly.
>
> Did I understand properly Peter that FOP 1.0 should support Jdk 1.3 ?
--
Peter B. West [EMAIL PROTECTED] http://www.powerup.com.au/~pbwest/
"Lord, to whom shall we go?"
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
but I'm willing to help
> (slowly) in other areas in the mean time if the new code is not yet ready to
> add these features. I will have a look at the todo list and the state of the
> code and come back (privately) when I have some time.
>
> Patrick Andries
> (member of the Ca
e no
> obstacles for redesigned fop to implement bidi support.
>
> PS.Actually it's even feasible to produce hebrew pdf using fop right now
> (well, under certain circumstances).
--
Peter B. West [EMAIL PROTECTED] http://www.powerup.com.au/~pbwest/
"Lord, to whom shall we go?"
ll at least be relevant to HEAD.
> - FO extensions
Peter
--
Peter B. West [EMAIL PROTECTED] http://www.powerup.com.au/~pbwest/
"Lord, to whom shall we go?"
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
Victor Mote wrote:
> My apologies for using up so much
> bandwidth.
Victor,
That's what it's there for. No apology required.
Peter
--
Peter B. West [EMAIL PROTECTED] http://www.powerup.com.au/~pbwest/
"Lord
an attempt to smuggle part of the
Transform namespace's constraints into the Format namespace. They are
completely different expression environments, which is why it doesn't
work. Has anyone else given this any thought?
Peter
--
Peter B. West [EMAIL PROTECTED] http://www.poweru
storage overhead was too great. Requiescant in pace.
Peter
--
Peter B. West [EMAIL PROTECTED] http://www.powerup.com.au/~pbwest/
"Lord, to whom shall we go?"
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additiona
Arved Sandstrom wrote:
>>-Original Message-
>>From: Tony Graham [mailto:[EMAIL PROTECTED]]
>>Peter B. West wrote at 30 Sep 2002 13:28:18 +1000:
>> > Tony Graham wrote:
>> > > [EMAIL PROTECTED] wrote at 27 Sep 2002 16:44:32 -0300:
>>...
acter" and "a
sequence of one character"? Well, one is a sequence, and therefore a
string, and there's no XSL conversion, etc.
So how do I represent a character?
To me, the cleanest, least ambiguous way is to represent a
attribute assignment value with "''" - a string literal of
length 1.
Peter
--
Peter B. West [EMAIL PROTECTED] http://www.powerup.com.au/~pbwest/
"Lord, to whom shall we go?"
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
Original Message
Subject: Re: Regarding your comment about on xsl-editors
Date: Fri, 27 Sep 2002 14:00:53 -0500
From: Paul Grosso <[EMAIL PROTECTED]>
To: "Peter B. West" <[EMAIL PROTECTED]>
CC: xsl-editors <[EMAIL PROTECTED]>
References
gth one), or is it just a literal (length 1), or just an
NCName (length 1), or is it something else? What does it look like, and
how is the parser going to handle it?
...
> > So IMO the spec is currently very vague on this.
>
> Then write to [EMAIL PROTECTED] asking fo
wrote:
>>From: Peter B. West [mailto:[EMAIL PROTECTED]]
>>
>>Fopdevs,
>>
>>Any comments on the representation and parsing of type
>>attributes would be gratefully received.
>
>
> This came up on www-xsl-fo, because Eric Bischoff and myself had the same
&
me)
> and from-table-column( NCName)
> (might even make a bit of sense for hyphenation-char and
> for fo:character's character in very, very strange cases)
A custom parser should not be necessary. The restriction
could be expressed as a constraint on the result, checked at
the
Original Message
Subject: Re: Regarding your comment about on xsl-editors
Date: Fri, 27 Sep 2002 10:55:28 +1000
From: "Peter B. West" <[EMAIL PROTECTED]>
To: Paul Grosso <[EMAIL PROTECTED]>
CC: xsl-editors <[EMAIL PROTECTED]>
References: <[EMAI
Fopdevs,
Any comments on the representation and parsing of type
attributes would be gratefully received.
Peter
--
Peter B. West [EMAIL PROTECTED] http://www.powerup.com.au/~pbwest/
"Lord, to whom shall we go?"
--
Original Message
Subject: Regarding your comment about on xsl-editors
Date: Wed, 18 Sep 2002 18:10:28 -0500
From: Paul Grosso <[EMAIL PROTECTED]>
To: "Peter B. West" <[EMAIL PROTECTED]>
CC: [EMAIL PROTECTED]
Peter,
Thank you for your comment to [EMAIL PROTE
t I'm
just confused.
Peter
Original Message
Subject: Regarding your comment about inline building on xsl-editors
Date: Wed, 18 Sep 2002 18:37:10 -0500
From: Paul Grosso <[EMAIL PROTECTED]>
To: "Peter B. West" <[EMAIL PROTECTED]>
CC: [EMAIL PROTECTED]
Pe
old Ray Bradbury(?) story. Yeesh
;-)
--
Peter B. West [EMAIL PROTECTED] http://www.powerup.com.au/~pbwest/
"Lord, to whom shall we go?"
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
been spoken in some remote monastery.)
Peter
Arved Sandstrom wrote:
>>-Original Message-
>>From: Peter B. West [mailto:[EMAIL PROTECTED]]
>>Sent: August 20, 2002 9:51 PM
>>To: [EMAIL PROTECTED]
>>Subject: Re: Style issues.
>
> [ SNIP ]
>
>>
mind, we might not throw the baby out with the bathwater.
> The only encoding rule I'd realy like to have:
> Don't mix underscores with camelCase.
> Beside looking *really* ugly, it screws up Emacs' dynamic
> identifier completion, and I'd rather like to do
> something for FOP than fixing this.
It comes down to "ugliness", doesn't it? "camelCase" is nice. I
haven't heard it before, and I agree with your admonition.
Peter
--
Peter B. West [EMAIL PROTECTED] http://www.powerup.com.au/~pbwest/
"Lord, to whom shall we go?"
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
it. In general, the only
knowledge we can assume about the characteristics of the text we are
processing is what is contained in the database.
Peter
--
Peter B. West [EMAIL PROTECTED] http://www.powerup.com.au/~pbwest/
se that convention except that someone always forgets to do
>>it and your back where you started.
>
> I knew that comment would come up. That's why I stamped it as unpopular.
>
>>what about
>>
>>currentPageNumber = m_pageNumber + 1;
>
> I can live with th
le this.
>
> I will maintain the following point: the layout managers concept allows
> us to explore how to do this sort of thing.
I happen to agree. Layout driven from below has to be instructed to go
in certain directions by some processes capable of judging the results
at higher levels. That's a layout manager *function*, whether it occurs
on the page-builder or on an individual block builder.
Not drowning, waving.
Peter
--
Peter B. West [EMAIL PROTECTED] http://www.powerup.com.au/~pbwest/
"Lord, to whom shall we go?"
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
J.Pietschmann wrote:
> Peter B. West wrote:
>
>> More less than more, I should think. Parsing is inherently "generic".
>> E.g., I assume that you would use the same tokenizer and first-level
>> parser.
>
>
> At the tokenizer level, sure. Howeve
es.
>
>
> Well, if widows="2" and you've laid out a block
> and discover there is only one line on the new page,
> what do you do? The easiest way seems to be to steal
> a line from the previous page.
...
Peter
--
Peter B. West [EMAIL PROTE
c FlowLayoutManager(FObj fobj) {
>Well, bad things happen.
Good idea, but we can hardly go crook at anyone who misses something
like this. However, if one is about to engage in a wholesale c&p, it is
probably worth asking, "Is there a better way?"
Peter
--
Peter B. We
olution
in the marker subtree must be deferred until the subtree is "re-parented".
Peter
--
Peter B. West [EMAIL PROTECTED] http://powerup.com.au/~pbwest
"Lord, to whom shall we go?"
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
Peter B. West wrote:
> J.Pietschmann wrote:
> And yes, it is absolutley choc-a-bloc with instancesof and casts, which,
Should read "absolutely chock-a-block"; it is not to be confused with
the consumption of chocolate.
>> - Have a FONode method which goes through
quot;blink"), so I preconstructed these and had the PropManager select and
> return the appropriate TextState object. Interestingly, this seemed
> to *increase* memory consumption of the test run, despite, of course,
&g
501 - 600 of 847 matches
Mail list logo