Lunascape Support Forum

Proposes to replace the current engine "WebKit" on the engine modified by the company "Google" called "Chromium"
http://dev.chromium.org/Home
At this engine is the ability to use plug-ins "Google Chrome".

or add as an additional engine "Chromium"
The engine is much more stable than the current "WebKit".

Chromium aka Chrome is the project name for Google's browser that use Webkit as its layout rendering engine.
Read more here.

Excerpt from the above linked source:

You're right. Somewhere I read that Google still modifies the webkit library, but may be wrong. I gave the suggestion, because I thought that the original library Webkit is hard to add support for plugins.
Already I can not wait to service plugins Chrome.

No, you are absolutely right!
They actually modify Webkit to make it run with their browser and in different environments. As you know Webkit is natively an Apple development which runs on Mac OSs. And these are quite different from Win OSs.
As far as I know, even Lunascape modifys the Webkit source to make it work with this browser.

You are indeed right. Webkit isn't even able to support Java properly.
We are all waiting for Webkit 2. We are hoping and praying ...

We'll see what we can do...

i agree with all of u chromium should be added. as well should presto ever go open source that would be magnificent to add.

would be better if folks actually understood the explanation given on Chromium at Chromium.org

Chromium does not change the webkit core.

They enclose it with a layer that adds the interfaces on which the following layers are depending. But each layer has absolutely no knowledge of the layer that comes next. This way it is going to be dead easy to rip out the webkit core and replace it with a newer one.

In other words. Adding Chromium as engine...wrong idea...Chromium is a browser, just like Lunascape. it uses webkit as engine, just like lunascape...

Another wrong idea...Chrome extensions. They are not linked to the engine, they are linked to a higher layer. Lunascape does not have this layer, it has its own...the Lunascape UI... It's not like with the Gecko engine, which also comes with its own UI (Extended Gecko Mode) on which to graft the Firefox/Gecko extensions...Since lunascape does not have these layer(s) Chrome extensions will not work most times since they would be actively looking for the Chrome interfaces into the layer that handles their use

Now, if Chromium were to decide to add such functionality to its layers that you could turn off certain parts, just like with the Gecko engine, than perhaps we may see a Chrome browser become part of Lunascape, but with it's UI layer by default disabled. Would be a resource monger though, running a separate instance for each extension (thats the way Chrome does it)

I've managed to dig up the page which shows it a bit more graphically, hopefully this prevents further confusion and allows users to understand why using the same engine, does not always mean it also can support all of the extensions other browsers use on that engine...

http://www.chromium.org/developers/desi ... -in-chrome

The same problem exists for the IE addons, some of these actively search for specific IE interfaces not available in the WebBrowser control. Because these happen to be located in one of the layers which IE lays on top of its engine.

Hello Mr. Lunatic.
It would still be nice to have Chromium. I mean, couldn't we modify the chromium to work with Lunascape? It would run a bit differently because of what is on TOP of it that makes it unique. Its kind of like linux. There's a lot of them, and they're all unique (trust me), and yet they all have the same core. Wouldn't it work? Please?