[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Using DOM via WebKit from Cocoa

Subject: Re: Using DOM via WebKit from Cocoa
From: Charles Parnot <email@hidden>
Date: Sat, 5 Apr 2008 17:10:56 -0700
Delivered-to: email@hidden
Delivered-to: email@hidden
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:from:to:in-reply-to:content-type:content-transfer-encoding:mime-version:subject:date:references:x-mailer; bh=1V2T98rkYpfq9FvB7tHmc69Tx992zFDSkXdjzlgvKzE=; b=B5qWYzecyAdC9TvJxm6F7g/w8ZxJKfJ/SV1224VS/AxM5a1Lf0rdcKSJhEgvA95+U6/iNqHCTlcxvFomYX4Y19nl83eZ+OqAXSqPyzgvAlUY5AMSaIrrmUuCSGGvWHMfGdStkenmXN4ZHKFfeYuoeAC372bUHhjv6eSW++wYBAk=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:from:to:in-reply-to:content-type:content-transfer-encoding:mime-version:subject:date:references:x-mailer; b=WWEY83nBK/728nF4wFmVis0/b4Ere4ggwOcEaNOCTVh6VaSI+KZJr/dmVQJ0Z+qSnyVx/lJTqpnEp/t5+YSHItd43VMDgXv4U+f+n0DwPuvIgDfmlsCuryEUFpGUbz1zpzquLcZqx9s8xkEh5xGdaPsoCbRO3EIypXUF5+WNnqE=

It seems like the only way to learn is to scour the DOM header files and hope for the best.

Yes, the classes are "documented" in the header files, but not in the Xcode html documentation or Apple developer web site.

However, it is very easy to get to the headers in Xcode: use the cmd- double-click on a symbol to get directly to the header file for it. E.g. get to DOMHTMLElement header @interface, check the methods implemented there, cmd-click on the superclass name right there to navigate the class hierarchy,...

Trying to compare this information to my other DOM
references has so far not been very fruitful.

I have found that the ObjC DOM implementation follows the w3c specs quite well. Reading those specs will help you understand exactly what each method does in ObjC. Note that they deprecated some of the methods in Leopard, to rename them avoiding orphan ':' (very clearly visible in the headers too).

Now, it is true that the functions defined in the specs are quite low- level for DOM access and it is probably up to you to create higher level methods to simplify some frequent patterns in DOM manipulations (sort of making your ObjC version of Prototype or other js framework). But this is a limitation of the DOM specs themselves, not its ObjC implementation.

And if you find a bug, there are still some people working on WebKit, I believe, and they might fix it if you report it ;-)

HTH a little,

charles


_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webkitsdk-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webkitsdk-dev/email@hidden

This email sent to email@hidden

Follow-Ups:
- Re: Using DOM via WebKit from Cocoa
  - From: Keary Suska <email@hidden>

References:
	>Using DOM via WebKit from Cocoa (From: Keary Suska <email@hidden>)

Prev by Date: Using DOM via WebKit from Cocoa
Next by Date: Re: Using DOM via WebKit from Cocoa
Previous by thread: Using DOM via WebKit from Cocoa
Next by thread: Re: Using DOM via WebKit from Cocoa
Index(es):
- Date
- Thread

Home