some thoughts to start

Hi Andras,

> So Jens, I think having the data structures in KDOM for the Kuanta
> preview release is out of question. 

yes, it is sad but we can not change it yet.

> Let's go with the parser alone for now and discuss that (in a different
> thread). 

After looking around in KDOM and KHTML2 I would propose the following:

Let us try to create our own parser backend, which could be based on Qt's XML 
parser. If we do this right we can load this in the future via 
kdom/parser/KDOMParserFactory 

Let us create our own builder that creates our old datastructure but uses the 
interface in kdom/parser/KDOMDocumentBuilder.h  This would be only a 
temporary solution in order to create our old data structure. In the future 
we would switch to the builder of KDOM. 

This would be used for HTML/XML parsing only. 
We would add custom attributes for our internal need in Quanta. 

All parsing of special areas would happen on top of this with our current 
code. 

I did not look in any detail yet, but this is the direction I would like to go 
in the moment. 

Any thoughts about this?

I will be in the province in the next 6 days and I do not know if I will have 
any internet access.

Jens

_______________________________________________
quanta-devel mailing list
[email protected]
https://mail.kde.org/mailman/listinfo/quanta-devel

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)

iD8DBQBDuSb3kYmIVB8IV+ARAnt5AJ0aAvqmIXZbly5DG0M0JjfWS6HVIwCffaqv
UYH/bLEMorCBoWt4lnGfwOM=
=hkBN
-----END PGP SIGNATURE-----