[quote]Originally posted by Amorph:
Funny; I read most of this as "they won't release it until they're done working on it," which seems fine with me. Developing on a moving target is a PITA.
And anyone who thinks KHTML is opaque should be thanking God on their knees that Apple didn't adopt Gecko.
I read it that way to, but when they're done there will need to be something else other than WebCore or people simply wont be able to use it. This is different from developing on an evolving framework. It's more like finishing a puzzle with pieces missing.
And to clarify, it's not KHTML that people are complaining about, it's WebCore.
Quote from Dave Hyatt's weblog:
[quote]I keep receiving emails from people trying to build applications using WebCore. People are asking me for help or advice on implementing the bridge inside WebCore.
If you're trying to embed the Safari layout engine right now, stop it!
Don't try to build code around these two components.
Update:: Quoted from ADC: "In addition to providing the best web browser for Mac users, one of the goals of Safari is to provide a fast and efficient HTML rendering engine for Mac application developers. Apple is actively
preparing a Safari SDK that will be available later this year."
In other words, all good things come to those who wait, so be patient!