Re: [webkit-dev] contentWidth of a table row & rendering data

On 1/17/07, Mark Rowe <[EMAIL PROTECTED]> wrote: You may want to have a look at how the Drosera project is configured. It builds + links against tip of tree WebKit, and it's revision history should give a bit of info about what was required to make that work. I'll look into that for a permanen

Re: [webkit-dev] contentWidth of a table row & rendering data

On 18/01/2007, at 11:10 AM, Stephen Deken wrote: How are you specifying which framework to link against? I'm specifying my WebKitBuild/Release directory in my Framework Search Paths, and I'm copying the frameworks into my app bundle's Frameworks directory. I'm also specifying @executable

Re: [webkit-dev] contentWidth of a table row & rendering data

The email you reference was written prior to WebKit being open-sourced. Ah, of course. How are you specifying which framework to link against? I'm specifying my WebKitBuild/Release directory in my Framework Search Paths, and I'm copying the frameworks into my app bundle's Frameworks dire

Re: [webkit-dev] contentWidth of a table row & rendering data

Hi Stephen, On 18/01/2007, at 3:03 AM, Stephen Deken wrote: On 1/17/07, David D. Kilzer <[EMAIL PROTECTED]> wrote: There is nothing that says you can't ship your own copy of WebKit (legal or otherwise)! OmniWeb does just that. Strange -- I'd read some discussion (apparently from 2004) which

Re: [webkit-dev] contentWidth of a table row & rendering data

On 1/17/07, David D. Kilzer <[EMAIL PROTECTED]> wrote: There is nothing that says you can't ship your own copy of WebKit (legal or otherwise)! OmniWeb does just that. Strange -- I'd read some discussion (apparently from 2004) which indicated the WebKit framework was not licensed for distributi

Re: [webkit-dev] contentWidth of a table row & rendering data

There is nothing that says you can't ship your own copy of WebKit (legal or otherwise)! OmniWeb does just that. You just have to weigh the consequences, the most obvious of which is that if Apple ships an update to WebKit (security fix or bug fix), your application won't take advantage of

Re: [webkit-dev] contentWidth of a table row & rendering data

On Jan 16, 2007, at 6:34 PM, Mark Rowe wrote: I believe the code relevant to determining where to draw the highlight outline is at . Beautiful, that's exactly what I needed. Now my dilemma is this.

Re: [webkit-dev] contentWidth of a table row & rendering data

On 17/01/2007, at 11:28 AM, Stephen Deken wrote: The nightly webkit appears to solve this issue, and actually does me one better -- the web inspector tool gets the (sometimes disjoint) render boxes that outline the selected node. If the web inspector does it, it stands to reason that I ca

Re: [webkit-dev] contentWidth of a table row & rendering data

I'll look into linking in the nightly tonight to see if it corrects my issue. Is there any other way to get the box (or boxes) for the rendered nodes? I'm using elementAtPoint: to get the DOMNode under the cursor and highlight it. The nightly webkit appears to solve this issue, and actually

Re: [webkit-dev] contentWidth of a table row & rendering data

Are you using shipping Safari, or a WebKit nightly, to do your testing? I'm using shipping Safari in 10.4.8 with all patches applied. Does the nightly not have this issue? I'll look into linking in the nightly tonight to see if it corrects my issue. Is there any other way to get the box (or b

Re: [webkit-dev] contentWidth of a table row & rendering data

Hi Stephen, Are you using shipping Safari, or a WebKit nightly, to do your testing? http://nightly.webkit.org/ Dave On Jan 16, 2007, at 7:20 AM, Stephen Deken wrote: Hello, This is a plea for help. I have a project for which I need to get the rendered outline of a DOM element. For my p

[webkit-dev] contentWidth of a table row & rendering data

Hello, This is a plea for help. I have a project for which I need to get the rendered outline of a DOM element. For my purposes, using the DOM offsetWidth and offsetHeight, combined with the offsetLeft and offsetTop (with the offsetParent's coords) gives me what I need in most cases. How