I've just finished reading it - very impressive, thanks! It has everything I need (well, probably something is missing still, but I can't find anything offhand). If such a class exists and works as advertised, I will have no problem quickly switching at least SPText with children and SPTextPath to it. In fact, for some time we could maintain both old and new implementations and switch between them for testing vs. actual work, until the new one is mature enough.
With regard to planning, we're now early in the release cycle, and this one is going to be a long one, so you have quite some time to work on this if you start now (several months). I think it will be OK to still have no official textflow support in 0.42, however the regular text and text-on-path must work at least we well as now. So, for now you can focus on these simpler cases (i.e. without wrap_inside_shapes) to finish them for the next release, and leave the flowtext for later.
On Sat, 19 Feb 2005 01:04:49 +0000, Richard Hughes <richard@...724...> wrote:
- I implement parse_svg_length_list() because the old flow_src did.
Should this really belong closer to the XML layer?
We have it in sp_svg_length_list_read
- The appearance of this document doesn't mean I've decided whether
to wrap the existing code, switch over the users, then write my own innards, or to do it all in one big (destructive) commit. The latter is quite a lot less work, but the former will likely be broken for shorter intervals (although maybe more of them).
I think we can go for the latter, but with a period of both implementations being available to switch between, as per above.