> htmlTag should probably be a proper class, I guess I figure when we use C++, for whatever reason, we should use its power. And selfishly, it's a good way for me to learn it. But I don't mean to create a lot of work for you either.
> all the char * members need to be replaced with string. Need to? Really? Right away? A good idea perhaps but might open up a can of worms. Like name is assigned the string produced by htmlAttrVal() in format.c, returning a c string of course, and yes I suppose this would autocast itself into a c++ string, but I wonder if there won't be a number of other cross file confusions here. The cw->tags is a concern for sure. Maybe could be void *, opaque pointer. If I remember right I build the html stack and then just move it to cw->tags, for that session, for the browsed file. Then use cw->tags later as you interact with the browsed file. Like filling out web forms, submitting, going to hyperlinks, etc, all those actions being encapsulated in html.cpp. Switch sessions and you get the tags for that session via cw->tags, and so on. But I should read through the code and make sure it's that simple. Karl Dahlke _______________________________________________ Edbrowse-dev mailing list [email protected] http://lists.the-brannons.com/mailman/listinfo/edbrowse-dev
