[webkit-dev] DOM tree surgery and DOM tree destruction
mjs at apple.com
Wed Jun 25 13:12:58 PDT 2008
On Jun 25, 2008, at 12:16 PM, Pitaga wrote:
> Thanks very much for this response.
> We (my co-workers and I) want to use WebKit modules selectively,
> running anything like full browser sessions. Over time, we'll do
> this as
> cleanly as we can, taking full advantage of smart pointers. For now,
> focused on implementing our own (non-trivial) algorithms. We're
> into browser sessions, running our algorithms on DOM trees, and
> worrying as
> little as possible about API issues. We're more than willing to
> write code
> to destroy objects. We're coping with smart pointers, rather than
> advantage of them. If this seems like the wrong attitude, please
> excuse us
> on the grounds that it's appropriate for us to focus first on
> Given that we're interfering with the mechanisms for automatic
> and need to write code to destroy trees, how do we do this?
If you want to use WebKit DOM classes in a way that violates their API
and memory management model, I think you are on your own as to
figuring out how to make it work.
More information about the webkit-dev