Adam Thompson <[email protected]> writes: > However, the more I think about it the more I think it's potentially not the > best direction for edbrowse since it places a lot of dependancy on something > beyond our control, i.e. the stability or otherwise of a js library.
True, they're all moving targets. On the other hand, we're pretty much tied to a JS library, so we're going to have to deal with its possible instability anyway. To me, the render-in-JS idea does seem pretty slick. > I also wonder if this'd work in terms of browsing a web page without > js, In the non-JS case, the only thing we ever call is render. We don't evaluate scripts or call form handlers from the page. > or one which defines its own render function. That's easy. Just call it edbrowse_render, to prevent namespace conflicts. Still, we have to make sure that this function can't be overwritten by some script. -- Chris _______________________________________________ Edbrowse-dev mailing list [email protected] http://lists.the-brannons.com/mailman/listinfo/edbrowse-dev
