Quote Originally Posted by agent
Put the definition for the DOM classes into a different file, say DOM.dll. All plugins that need to access it can reference it. Next, when the plugin is initialized for a particular document, the DOM for the currently loaded page is passed to it. I've written several plugin systems that do similar to this. Simple as pie.
I see what you mean yes, or even if there was 1 DLL for the whole rendering engine each plugin could just render that and access all of the public methods/attributes/classes that would expose all of the information that it would ever need.

Quote Originally Posted by agent
To render plugins, btw, I propose that the plugin returns it's size to the browser which makes room for it. Then, the plugin provides a control, say ".PluginWindow as Control" which is then placed on top of the document. This is how most browsers do it and relieves us of painting each frame of a flash animation manually.
I see exactly what you mean and it's definately the best way to go about it.

I think if any browser was to seriously compete it would need to have support for Mozilla plugins (like Opera does for example) so that the plugin vendors (read Adobe) wouldn't need to support your browser at all with a new version, it would just work. Would take a bit of reading