kdom and khtml integration

[Maks Orlovich]

> > 2. Consider merging webkit datastructures like AtomicString/QualifiedName
> > and ElementFactory. This is optional ofcourse, however we have good
> > experiences with this functionality in kdom.
>
> Yes, I agree with that.

Could you perhaps elaborate on the advantages? I am quite concerned about 
loosing all the nice switches. 

>
> > 7. Consider renaming khtml to kxml, to reflect the improved xml
> > capabilities.
>
> Then we can as well go with "webkit" as a name ;)
>
> Honestly, I fail to see which problems you saw with the modularisation?
> Perhaps then it would be easier to decide. Right now I don't think that
> "avoiding a couple more virtual functions" would be a ground you base the
> start of spaghetti code (see Safari) on.

Well, one issue I talked about with Niko is that we definitely do not want to 
guarantee BC in impl classes. So if it's modular, we'll have to do some sort 
of thing where ksvg version is paired to the khtml version.