Adam offers: > I may have a go at plugging in the new code at some stage.
Let me know if you want to take a whack at it. That would be great. If not I may try it next week. Either is fine with me. This is a roadmap. struct tagInfo and htmlTag move back into eb.h. In fact we won't need js.h at all. Once the vital declarations move from js.h into eb.h, change makefile so it doesn't refer to js.h or jsdom.cpp or jsloc.cpp. Nor does it need the mozilla headers or libraries, except for the target edbrowse-js, which builds properly today. And include edbrowse-js under all: struct htmlTag has the member jv, javascript variable, which links this tag to the corresponding object in the js world. currently HeapRootedObject jv; needs to be jsobjtype jv; Rename createJavaContext1 to createJavaContext in ebjs.c and similarly for freeJavaContext1. Remove the block at the top of ebjs.c that is there just for stand alone compilation. Generate the prototypes for ebjs.c, I can do it with my tool if you like, and put them into eb.p. We won't need ebjs.p any more. Many of these functions are plug in replacements for the old functions. get_property_string(object, name) it does what it did before. So I'm hoping it is an easy process from here. Put it all together and build the new edbrowse. Make sure edbrowse-js is linked into your path, or edbrowse won't be able to exec edbrowse-js - although you may want to test that condition as well. Lots of testing, websites, javascript, and of course exercising jsrt. Once we have some confidence in the new architecture, delete js.h ebjs.p jsdom.cpp jsloc.cpp. Convert html.cpp back to html.c. Sadly, there were a few times I used c++ strings in here, for convenience, and I think you told me not to, and now I see why. Switch these back to strings using my dynamic string management routines in stringfile.c, then the file can go back to html.c Change makefile flags and libraries so edbrowse is a C program again. Globally replace eb_bool eb_true eb_false with bool true false, and appropriate #defines in eb.h, as it was before. 3.5.3 Then we can take the next step and the next and the next. Karl Dahlke _______________________________________________ Edbrowse-dev mailing list [email protected] http://lists.the-brannons.com/mailman/listinfo/edbrowse-dev
