The serializer
By glazou on Monday 25 April 2005, 14:43 - Nvu - Permalink
I think I am going to entirely rewrite the content serializer in Gecko. It is messy and poorly documented, it does not allow pretty-printing in XML, it does not allow to customize pretty-printing, it has a few very annoying bugs dealing with whitespaces and line breaks. I added a lot of stuff there for source colorization, and it could be architectured better. So I am going to trash almost everything and design a pretty printer controller based on a configuration file. With that, the user will be able to customize the output of all elements and all attributes in a given namespace and save that customization. Case, indentation, wrapping, carriage returns. What else?
Comments
Is this happening before or after you try to remerge Nvu work into the main Mozilla code base, assuming you (still) plan to do so? Either way, have fun...
That'd be great. Please, try not to loose on speed
Showing first lines <? ?> ????
Is there not an existing open source serializer you could use instead of reimplementing the lot?
Daniel, which serializer? We have more than one, no? And some of these are rather sensitive to changes (that is, web content expects certain behavior out of getting innerHTML, say).
There is a lot of interest in the serializer behavior from me, sicking, akkana, peterv, and brade; so you may want to discuss your design a little more widely before you start implementing...
Also, I hope you're working on the trunk; the branch's XML serializer has serious issues with namespaces.
Ok, just... don’t break it :). We’re depending on it where I work ^_^.
One request: for source code control, it is important not to allow many line breaks to change because of a simple change in a single line. It is important that line breaks can be preserved as much a possible.