I'm only saying the approach I took in 2.0 doesn't feel perfectly right. Hence it probably wouldn't be a backport but a new implementation for 1.x, which will take even longer. I am convinced that the MarkupFragment concept itself is the right way to go.
Juergen On 4/14/07, Eelco Hillenius <[EMAIL PROTECTED]> wrote:
> markupfragment is a pretty extensive refactor, and i dont think it will be a > straight backport. i think best is to leave it for 1.4 Then I suggest to drop it altogether. We have enough on our plates right now, and the idea was to have the 1.3 and 1.4 releases as close together as possible. And if Juergen isn't convinced it's for the better in the first place, we should just forget about it. Eelco
