Here is what I understand, others may have more to
add:
I see two ways to interpret your question: (1) what
happens in the code that makes page-sequence be the
lowest granularity we have, and (2) why we do it that
way.
1) When the page-sequence's children
(layout-master-set, declarations?, flo
Fop-devs,
It occurs to me that some of the implications of the FAD approach have
not been successfully communicated. Part of this may well be because of
my own inadequate understanding of the FOP process. Before I continuing
with this discussion, I had better ensure that my understanding of on
Team,
On my two earlier API proposals [1], I'm going to take
a step back on the first one about combining the
apps.Driver class into apps.Fop. Joerg's thoughts
that the API wrapper/class and application
wrapper/class should be distinct is weighing on my
mind; in the future we may find it benefici
+---+
| Bugzilla Bug ID |
| +-+
| | Status: UNC=Unconfirmed NEW=New ASS=Assigned
-- "J.Pietschmann" <[EMAIL PROTECTED]> wrote:
> Glen Mazza wrote:
> > That should be enough for us in 1.0, no? Those
> more
> > elaborate API goals appear best discussed
> post-1.0,
> > presumably once more vital parts of the system
> have
> > been addressed.
>
> A stable API is as important as
Glen Mazza wrote:
That should be enough for us in 1.0, no? Those more
elaborate API goals appear best discussed post-1.0,
presumably once more vital parts of the system have
been addressed.
A stable API is as important as other major features.
If we do a mojor release, post-release API changes s
