Victor,
thanks for your explanations. i'll give a look into FOray when i'll
feel more confident about the layout process.
cheers, Renaud
Renaud Richardet wrote:
> Victor,
> in [1] you talked about dealing with the positioning of areas
> during the AreaTree building. could you point me to the
> classes in FOray that handle that logic?
...
> [1]
> http://nagoya.apache.org/eyebrowse/[EMAIL PROTECTED]
l.apache.org&msgNo=10534
Hi
On 22.02.2005 22:35:15 Renaud Richardet wrote:
> > So far, I can only say that there's so mandatory reason for that change.
> > It would certainly make the renderers simpler but there might be
> > problems in other areas. The real downside is when you have to do the
> > same calculations in every
hello Jeremias
merci for the informations.
> I wondered about that, too:
> http://nagoya.apache.org/eyebrowse/[EMAIL PROTECTED]&by=thread&from=984481
interesting!
Victor,
in [1] you talked about dealing with the positioning of areas during
the AreaTree building. could you point me to the clas
Salut Renaud
I wondered about that, too:
http://nagoya.apache.org/eyebrowse/[EMAIL PROTECTED]&by=thread&from=984481
So far, I can only say that there's so mandatory reason for that change.
It would certainly make the renderers simpler but there might be
problems in other areas. The real downside
bonjour fop-dev's
i've been walking through the rendering process. if i understand it
rightly, an area doesn't records it's absolute position. therefore, we
have to pass the currentIPPosition, currentBPPosition all along during
the rendering process to figure out where to position an area.
what i
