summaryrefslogtreecommitdiffstats
path: root/quanta/parts/kafka/DESIGN
diff options
context:
space:
mode:
authorTimothy Pearson <[email protected]>2011-11-16 13:53:35 -0600
committerTimothy Pearson <[email protected]>2011-11-16 13:53:35 -0600
commitffa67ac75582192196cb70f866f6bfa00586542a (patch)
tree5a09c67b42a8228fc8348b5689b85006ea09942d /quanta/parts/kafka/DESIGN
parent997aa1672a07ce33c6696bd4a4124bfff97036e1 (diff)
downloadtdewebdev-ffa67ac75582192196cb70f866f6bfa00586542a.tar.gz
tdewebdev-ffa67ac75582192196cb70f866f6bfa00586542a.zip
Additional renaming of kde to tde
Diffstat (limited to 'quanta/parts/kafka/DESIGN')
-rw-r--r--quanta/parts/kafka/DESIGN2
1 files changed, 1 insertions, 1 deletions
diff --git a/quanta/parts/kafka/DESIGN b/quanta/parts/kafka/DESIGN
index d983309f..eabfd4e1 100644
--- a/quanta/parts/kafka/DESIGN
+++ b/quanta/parts/kafka/DESIGN
@@ -57,7 +57,7 @@ HTML
The Node class handle the pointers to the parent, next, previous and first child Node. *Each* Node has a valid pointer to a Tag. The Tag takes care to remember all the information concerning the Tag itself, like the attributes, the type, etc...)
One QTag per Element is created from the .tag files when Quanta is started. Each QTag contains all the DTD information about the Tag. E.g. the "IMG" Qtag says that it is a single Tag, and what are its attributes. You can get a QTag with QuantaCommon::tagFromDTD, but don't delete the QTag!
-Now to khtml. The class KHTMLPart is the HTML renderer widget of konqueror. It internally works with a Node Tree (another? Yep!) but these Nodes are real DOM::Nodes. (From now, I will call it the DOM::Node tree) Each of the DOM Nodes is khtml-internally linked to a rendering Node i.e. a change made to one DOM::Node will update the HTML rendering cf /path/to/kde/include/dom/*.h and also in the kdelibs cvs module, cf the nice kdelibs/khtml/DESIGN.html. WARNING about DOM::Nodes, they are just interfaces!!
+Now to khtml. The class KHTMLPart is the HTML renderer widget of konqueror. It internally works with a Node Tree (another? Yep!) but these Nodes are real DOM::Nodes. (From now, I will call it the DOM::Node tree) Each of the DOM Nodes is khtml-internally linked to a rendering Node i.e. a change made to one DOM::Node will update the HTML rendering cf /path/to/kde/include/dom/*.h and also in the tdelibs cvs module, cf the nice tdelibs/khtml/DESIGN.html. WARNING about DOM::Nodes, they are just interfaces!!