Well the tags are built in a growing linked list as the page is parsed,
but at the end of parse I plop them all into an array,
so it is easy to grab tag 243 (example), just index the array,
because the text in your buffer actually has encoded
tag 243 {go to this link}
You don't see tag code 243 but it's there,
and it is accessed when you go to that link.
If we want tags to continue to grow after page parse,
new tags because of javascript creating html structures etc,
then we want something with the dynamic power of a linked list or a tree
but also an easy way to index like an array.
Not sure if C++ list has this much power, or vector,
but in C there wasn't anything, which is why I made the compromise I did.
Anyways we might be able to forget the array and stay with the c++ list,
and use its power to move forward.
Create tags whenever javascript tells us to,
and they can have parent links inside them to define the tree structure
of forms and tables and so on.
Karl Dahlke
_______________________________________________
Edbrowse-dev mailing list
[email protected]
http://lists.the-brannons.com/mailman/listinfo/edbrowse-dev
