Hi there, at the moment I am writing an application which heavily depends on DOM. To make it run on 10.3, too, my idea is to distribute WebKit frameworks together with my app. Is this permitted? I did not found any license agreements on webkit.darwin.org. Besides this legal issue: has anybody got WebKit compiled on 10.4 (with MACOSX_DEPLOYMENT_TARGET 10.3) to run on 10.3? My test app complains about missing references, e.g. "WebKit undefined reference to _kCGImageSourceShouldPreferRGB32". Thanks in advance, Robert -- --- - .-. -- -- --- / \ ---- tin:b Software .-. / \ --- .-. __o .-. (i) / \ / \ / \ _`\<,_ / \ Robert Fischer / \ / \ / \ (*)/ (*) / `--------------- / `---' `-' `-----------'
On Jun 20, 2005, at 11:04 AM, Robert Fischer wrote:
at the moment I am writing an application which heavily depends on DOM.
The DOM features are in the OS X 10.3.9 update. If you can depend on 10.3.9, you can ship a 10.3-compatible version of your application.
To make it run on 10.3, too, my idea is to distribute WebKit frameworks together with my app. Is this permitted? I did not found any license agreements on webkit.darwin.org.
The license agreement is in the code. WebKit/LICENSE and WebCore/ LICENSE-* have the relevant licenses. But aside from what the license agreement allows, we recommend against building a copy of the WebKit frameworks and distributing them with your Mac OS X application, because of the various technical hurdles involved. It's quite likely your application will break with various system changes. To give just one example, since various other frameworks use the WebKit, your copy of the WebKit will be used by frameworks within your application too, not just your application. And there's no way to be sure which SPIs those frameworks might be using, or guarantee that an update to one of those other frameworks might start using an SPI your WebKit doesn't have.
Besides this legal issue: has anybody got WebKit compiled on 10.4 (with MACOSX_DEPLOYMENT_TARGET 10.3) to run on 10.3? My test app complains about missing references, e.g. "WebKit undefined reference to _kCGImageSourceShouldPreferRGB32".
No, I don't think anyone has TOT compiling on 10.3 yet, although we didn't remove the various Panther-specific ifdefs and code paths yet. Building on 10.4 and running what's built on 10.3 would be yet another challenge, and that's something we've never done before in the history of the WebKit project. -- Darin
On Jun 20, 2005, at 8:16 PM, Darin Adler wrote:
The DOM features are in the OS X 10.3.9 update. If you can depend on 10.3.9, you can ship a 10.3-compatible version of your application.
Great news to me! I was mislead by this sentence in the DOM documentation:
The Document Object Model API is available only in Mac OS X v10.3 with Safari 1.3 Developer Beta and later or in Mac OS X v10.4 and later.
("file:///Developer/ADC%20Reference%20Library/documentation/Cocoa/ Conceptual/WebKit_DOM/index.html") As Developer Beta was only available for ADC members that would be not acceptable for most of my customers. So, the documentation should get a little update on this point. Thx, Robert -- --- - .-. -- -- --- / \ ---- tin:b Software .-. / \ --- .-. __o .-. (i) / \ / \ / \ _`\<,_ / \ Robert Fischer / \ / \ / \ (*)/ (*) / `--------------- / `---' `-' `-----------'
On Jun 21, 2005, at 2:43 AM, Robert Fischer wrote:
The Document Object Model API is available only in Mac OS X v10.3 with Safari 1.3 Developer Beta and later or in Mac OS X v10.4 and later.
("file:///Developer/ADC%20Reference%20Library/documentation/Cocoa/ Conceptual/WebKit_DOM/index.html")
As Developer Beta was only available for ADC members that would be not acceptable for most of my customers. So, the documentation should get a little update on this point.
Well, it is correct to a point, in that the DOM API headers were not present on 10.3.9, so you couldn't build a product that used the DOM API on 10.3.9, you could only build on 10.4 and deploy on 10.3.9. However, I'm choosing to believe that this was an error in the build process and that the DOM headers were supposed to be included in 10.3.9. -- Kevin Ballard kevin@sb.org http://www.tildesoft.com http://kevin.sb.org
On Jun 21, 2005, at 8:27 AM, Kevin Ballard wrote:
On Jun 21, 2005, at 2:43 AM, Robert Fischer wrote:
("file:///Developer/ADC%20Reference%20Library/documentation/Cocoa/ Conceptual/WebKit_DOM/index.html")
As Developer Beta was only available for ADC members that would be not acceptable for most of my customers. So, the documentation should get a little update on this point.
I think the documentation people are already aware of this, and are going to update it. If you'd like to report the bug to them, though, just in case, you can do that at <http://bugreport.apple.com>.
Well, it is correct to a point, in that the DOM API headers were not present on 10.3.9, so you couldn't build a product that used the DOM API on 10.3.9, you could only build on 10.4 and deploy on 10.3.9.
However, I'm choosing to believe that this was an error in the build process and that the DOM headers were supposed to be included in 10.3.9.
Headers are never included with software updates, so it wasn't an error. However, there is something called the Mac OS X 10.3.9 SDK that you can get that makes this work. I don't know all the details. -- Darin
On 6/21/05, Darin Adler <darin@apple.com> wrote:
However, there is something called the Mac OS X 10.3.9 SDK that you can get that makes this work. I don't know all the details.
Are you sure? AFAIK the 10.3.9 SDK is only part of Xcode 2.x's Cross-Development foobage, which of course doesn't work on Panther. -- Finlay
On Jun 21, 2005, at 10:22 AM, Finlay Dobbie wrote:
On 6/21/05, Darin Adler <darin@apple.com> wrote:
However, there is something called the Mac OS X 10.3.9 SDK that you can get that makes this work. I don't know all the details.
Are you sure? AFAIK the 10.3.9 SDK is only part of Xcode 2.x's Cross-Development foobage, which of course doesn't work on Panther.
I'm not sure why the 10.3.9 SDK hasn't been released in a form usable on 10.3 yet; I looked and indeed I can't find it. I do remember that this was planned at one point, and it was the definitive way for people developing on Panther to get the tools they need for the new WebKit API. But I haven't kept up with things and there may have been a change to the release strategy. I'll let you know if I find out anything. -- Darin
On Jun 21, 2005, at 10:34 AM, Darin Adler wrote:
I'm not sure why the 10.3.9 SDK hasn't been released in a form usable on 10.3 yet; I looked and indeed I can't find it. I do remember that this was planned at one point, and it was the definitive way for people developing on Panther to get the tools they need for the new WebKit API. But I haven't kept up with things and there may have been a change to the release strategy.
I'll let you know if I find out anything.
I got the word on this from an Xcode expert at Apple. He said:
Just install the package itself from the Tiger disk onto your Panther box.
What that means I guess is that you find the relevant ".pkg" file, and use the Installer to install it on Panther. -- Darin
Umm, I thought that's where the headers were missing. I forget, though. All I really know is that when we added the DOM stuff to Colloquy, we couldn't build on 10.3.9 even though we could deploy on 10.3.9. On Jun 21, 2005, at 1:18 PM, Darin Adler wrote:
However, there is something called the Mac OS X 10.3.9 SDK that you can get that makes this work. I don't know all the details.
-- Kevin Ballard kevin@sb.org http://www.tildesoft.com http://kevin.sb.org
participants (4)
-
Darin Adler
-
Finlay Dobbie
-
Kevin Ballard
-
Robert Fischer