You was replying a thread from Jun/2011. In this time the developers worked in a Browse version based in webkit.
Gonzalo On Tue, Feb 21, 2012 at 4:06 AM, lkcl luke <luke.leigh...@gmail.com> wrote: > http://trac.webkit.org/wiki/WebKit2 > > ok: one of the issues that i ran into on the original (flawed) > webkit-gobject development work, as well as the ports of pythonwebkit > to gtk and directfb, was quite how integrated the whole thing had to > be. there are now something like *eight* separate language bindings > to webkit (including at least two javascript ones), each of which is > in a separate state of development and even present *different* > versions of the same underlying DOM API. > > it would appear that webkit2 has "injected bundles" which is a stupid > way of saying "you can install a shared library dynamically into > webkit using dlopen". > > basically this means that it will at some point be able to - *without* > having any dependency or *any* interaction with the webkit team - add > language bindings and other features to webkit. > > i strongly, strongly, strongly advise the OLPC team to WAIT until such > time as such code has been written, before proceeding with the use of > webkit in OLPC. > > of course you are entirely free to do whatever you find to be most > useful to you, choosing instead to learn for yourselves why webkit1's > gobject introspection bindings are fundamentally flawed and spending > significant time doing so. > > l. > _______________________________________________ > Sugar-devel mailing list > Sugar-devel@lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/sugar-devel >
_______________________________________________ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel