You are viewing a plain text version of this content. The canonical link for it is here.
Posted to batik-users@xmlgraphics.apache.org by th...@kodak.com on 2006/03/26 17:14:04 UTC
Re: svn commit: r388911 - TEXT_COMPOUND_DELIMITER
Hi all,
I am curious to hear how/if people are using TEXT_COMPOUND_DELIMITER.
The solution I committed is maximally backwards compatible but has some
ugliness
to it. My proffered solution would be to remove TEXT_COMPOUND_DELIMITER
completely and instead use TEXT_COMPOUND_ID as a soft reference to the
Element.
This would clean up the code a bit and make the behavior a little less
modal than
it currently is. Would this be a significant problem for anyone?
deweese@apache.org wrote on 03/26/2006 09:40:51 AM:
> 2) In most places TEXT_COMPOUND_DELIMITER has effectively been
> replaced by TEXT_COMPOUND_ID. TEXT_COMPOUND_ID has a unique
> value for each element in the DOM but retains no reference to
> the element.
>
> In dynamic documents TEXT_COMPOUND_DELIMITER is still bound on
> elements, with a hard reference to the DOM element.
---------------------------------------------------------------------
To unsubscribe, e-mail: batik-users-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: batik-users-help@xmlgraphics.apache.org