The DOM methods I immediately missed were getChild, getChildCount, and getChildIndex.
>The problem with this is all the DOM methods expect to see a user element. >Which means our code is peppered with casts from dom elements to user elements. AFAICT, its quite a bit worse than that. Since all those generic element objects are subclasses of dom.client.Element, not user.client.Element, you CANNOT use those DOM methods with the dom.client.Element subclasses. Seems to me that makes them unusable for now. Also, note that the google widgets aren't actually eating their own dog food yet (they still use the user.client.Element). Basically, its fine to refactor any method in the DOM class that delegates to the dom.client.Element, e.g., replace DOM.removeChild(parent, child) with parent.removeChild(child), but I can't find anything else to take advantage of. (And I suspect that GWT would be inling that refactoring anyway.) (I agree with the comments that the documentation is a bit lean in this area. I'll be watching Bruce Johnson's talk tonight to see what I've missed.) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~----------~----~----~----~------~----~------~--~---
