a method to render page in webkit chromium engine in a kmeleon tab by using the chrome frame for ie plugin and the ietabplugin. this will require kmeleon 1.6 and xp and above naturally to install the chrome frame.

1- download and install the chrome frame enterprise edition from this link:
http://www.google.com/chromeframe/eula.html?msi=true

2- (if you already have google products installed or not concerned about google doing things behind your back you can skip steps 2 - 5). after installing, chrome frame installs an update service..you might want to remove it.
go to c:\windows\tasks and you will find 2 tasks for googleupdate and googleupdateservice..delete them both
now you will need to remove the installed service- you can view it in services msc

go to startmenu>run and in the run buffer type:
sc delete gupdate
click ok
this will remove the service

3- unregister the update dll from the registery
startmenu>run and type:
regedit
click ok, in regedit, do a search for goopdate

(not for goopdate.dll like in the snapshot above..just goopdate because the file name will differ if you're using non-english os like goopdatede.dll or goopdatefr.dll so just search for goopdate
there will be 2 keys pointing to the update dll, delete the first one and then contine search(f3) and delete the second one.
close regedit

4- reboot your computer

5- go to c:\program files\google and delete the update folder- you can rename it if you want but it's now pointless and taking hd space

6- go to C:\Program Files\Google\Chrome Frame\Application and locate a folder called 'installer' this is useless backup of the chrome frame which takes about 85 mb..delete it to freeup hd space.

7- download this regkey and merge it in your registryright-click>save target as)
http://kmext.sourceforge.net/pends/chromeframefix.reg
this will enable kmeleon to use ietab for chrome and will also fix a problem in clicking links in chrometab that reverts back to the ie engine.

8- restart or relogin your pc

9- download this extension:
http://kmext.sourceforge.net/pends/coralietab+chrometab.7z
use kem to install or manually delete compreg.dat and xpti.dat from k-meleon\components folder. this is a slightly modified corelietab which will enable the chrometab..if you already use corelietab, just install it on top, it will not affect ietab browsing and you can still open pages in ietab normally by selecting sendpage/send link to>trident render.

10- restart k-meleon , right click on a page or link and select sendto >webkit render to open in chrome frame




your browsing history/cache saved passwords in kmeleon chrometab will be stored at this location:
C:[documents settings|Users][user name]\Local Settings\Application Data\Google\Chrome Frame\User Data\k-meleon\Default



Edited 1 time(s). Last edit at 05/03/2011 09:45PM by disrupted.

Disrupted,

I am no fan of Chrom, nor its offshoot Iron. How about QtWeb?

<g>

N

they are both webkit browsers, although chromium webkit is more advanced when it comes to js engine.. we are just using the chrome engine to create a webkit tab in kmeleon and you won't be installing the actual chrome browser-there's no ui.

Quote
disrupted(unlogged)
they are both webkit browsers, although chromium webkit is more advanced when it comes to js engine.. we are just using the chrome engine to create a webkit tab in kmeleon and you won't be installing the actual chrome browser-there's no ui.

disrupted,

Ah-ha, now I understand. Thanks!

N

does it eat ram much?

i haven't tested it when it comes to ram usage, it will depend on the type of page, js etc but naturally rendering in chromewebkit tab will consume more ran than using native gecko engine, you'll be launching a second engine in memory.

this is a strictly developer's extension not meant for regular browsing, just like ietab or in some cases if a page has display problems in gecko-not necessarily requiring a newer engine as webkit is more trident-compliant than gecko, meaning some pages written to accommodate ie(especially ie6/7) will have no problems in webkit but will be misplaced or disjointed on gecko.

gecko in my opinion is still a superior engine regardless of the buzz for chrome/webkit js speed, the xul packaging is what fails it in products like firefox-something which kmeleon doesn't suffer from.. kmeleon(for windows) was the natural evolution of the original netscape which also used native widgets

http://en.wikipedia.org/wiki/Netscape_6
"The Mozilla engineers decided to scrap the Communicator code and start over from scratch. All resources were bound to work on the Mozilla-based Netscape 6.0 release, which some Netscape employees still deem one of the bigger mistakes in the company's history."

another very important point about webkit that almost all 'western' journalists or reviewers overlook or fail to recognise is the rendering of unicode fonts which is quite poor compared to other engines, even ie and that's a venue where gecko rules them all
having the proper fonts installed on your system, you can compare unicode rendering between browsers on this page
http://en.wikipedia.org/wiki/Help:Multilingual_support#Browsers
you will notice that webkit fails to render several scripts

while webkit is getting all the praise on pc mags, i doubt if those writers are readers of non-conventional languages and that's probably why chrome might be gaining ground in the us, euroasians and far east surfers still opt for firefox or stick with ie.

this is an interesting link, although outdated..it pretty much still applies
http://www.alanwood.net/unicode/browser-coverage.html