3 ms·
(I am a Chrome developer.) As far as I know we've never heard from the Awesomium developers; they don't mention which version of Chrome they're based on which
by evmar 15y ago
(I am a Chrome developer.)
As far as I know we've never heard from the Awesomium developers; they don't mention which version of Chrome they're based on which makes me suspect they're not staying in sync with trunk.
That suspicion comes from the fact that the Chromium Embedded developer does participate in Chrome development -- to the extent that he keeps his project working -- and occasionally pops up on our mailing list discussing API changes that would benefit embedding.
PS: wonder whether the Awesomium people are doing the right thing by WebKit's LGPL license, hmm...
- adamkhrona 15y agoI'm the main Awesomium developer-- the 1.6 branch is based off a stable revision from April 2010. We've recently updated to the latest Chromium trunk and will be launching an experimental, public build of our 1.7 branch soon. (Would have happened sooner but we've been focusing more on getting the library stable rather than absorbing new features.) By the way, we do participate in the development of Chromium (albeit, rather covertly in IRC), I personally have been a long-time lurker of the mailing-list since the first month it opened. :-) Regarding WebKit's (or, more specifically, WebCore's) LGPL license-- we've sought legal counsel on this and believe we've satisfied the conditions. We are, nonetheless, planning to package up WebKit into a separate dynamic library in the near future.