Quote
desga2
As Camino developers said, is time to migrate to WebKit engine.
Better for us, worst for Mozilla.
Quote
desga2
Yes it is, other Gecko browser migrated to Webkit engine; Epiphany, Flock, and the next are Camino and K-Meleon. Technically the migration is possible.
This announcement changed our future "roadmap":
K-Meleon 1.6.x => Seamonkey 2.0.x, Firefox 3.5.x => Gecko 1.9.1.x
K-Meleon 1.7 => Firefox 3.6.x => Gecko 1.9.2.x
K-Meleon 1.8? => Seamonkey 2.1.x?, Firefox 4.0.x? => Gecko 2.0.x?
K-Meleon 2.0? => Based in Webkit engine?
All this is a supposition, we don't know if will there are developers needed to migrated the project to Webkit engine.
Almost is possible that we have to renamed the project (or created a new project) because K-Meleon is by definition a Gecko embed browser project and not a Webkit embed browser project.
Quote
ndebord
Quote
desga2
Almost is possible that we have to renamed the project (or created a new project) because K-Meleon is by definition a Gecko embed browser project and not a Webkit embed browser project.
Flock didn't rename itself when it made the move and name recognition is important.
except to note that they probably look at K-Meleon, Camino and Galeon as gadflys they'd just as soon do without, as they are a constant reminder that there is another way to go with Gecko browsers than XUL/XPI emulation that is faster with operating system specific APIs.
Quote
desga2
As Camino developers said, is time to migrate to WebKit engine.
Better for us, worst for Mozilla.
Quote
guenter
When the project moves to another html-engine, the project will take these ideas and concepts along (hopefully), what better name can the browser have but the old fitting name, K-meleon, with its brand recognition. Epiphany, Flock, Camino,... Maxton... do/did not rename when they change their html-engine because they have had well established brand names.
The end users does not care what engine drives the vehicle.
So the name should be taken along if the project has to change the engine.
Quote
gordon451
Quote
desga2
As Camino developers said, is time to migrate to WebKit engine.
Better for us, worst for Mozilla.
My other browser is QtWeb 3.7 with AppleWebKit/533.3 -- unfortunately WebKit does not support Java. For example, I cannot use Landgate Property Finder, which works reasonably well in KM, and very well in IE6.
As the cat said to the rodents: "Don't be in too much of hurry to jump overboard -- there's only one of me, but lots of sharks out there..."
Don't get me wrong -- QtWeb is a nice browser which handles most mapping sites very well. But...
Gordon.
Quote
desga2
K-Meleon migration is lees complicated than other projects because we aren't using XUL for the GUI (only Preferences panel and some extensions).
Quote
desga2
WebKit and Chromium can be embedding in a MFC application:
http://code.google.com/p/chromiumembedded/
http://magpcss.org/ceforum/viewtopic.php?f=6&t=50
K-Meleon migration is lees complicated than other projects because we aren't using XUL for the GUI (only Preferences panel and some extensions).
Quote
desga2
This website work fine with Java in Iron browser that use WebKit.
QtWeb is yet uncompleted for this features.
And other Webkit browser as Google Chrome/Chromium based browser work fine with Java.
Quote
gordon451
Yes, you are right. However, QtWeb is the only WebKit browser which runs in W2K...
Quote
MS SDK 7
supports x86, x64, and IA64 platform architectures for building and running applications on Windows XP SP3, Windows Server 2003 R2, Windows Vista, Windows Server 2008, and Windows 7
Quote
Mozilla Wiki Documentation
Embedding/NewApi
==================
Getting the code
---------------------
The code currently lives outside the main tree in a separate Mercurial repository (http://hg.mozilla.org/incubator/embedding/).
Quote
Cattleya
Hi, I have a question: "Can K-Meleon use the newest Gecko of Firefox 7.0 ?"
I read this and this, but still don't know what it mean ? I'm not a developer, so I really don't know about that : (
I think newer Gecko version will be better, faster, I will glad if K-Meleon can integrate it.
Quote
desga2
Yes it is, other Gecko browser migrated to Webkit engine; Epiphany, Flock, and the next are Camino and K-Meleon. Technically the migration is possible.
This announcement changed our future "roadmap":
K-Meleon 1.6.x => Seamonkey 2.0.x, Firefox 3.5.x => Gecko 1.9.1.x
K-Meleon 1.7 => Firefox 3.6.x => Gecko 1.9.2.x
K-Meleon 1.8? => Seamonkey 2.1.x?, Firefox 4.0.x? => Gecko 2.0.x?
K-Meleon 2.0? => Based in Webkit engine?
All this is a supposition, we don't know if will there are developers needed to migrated the project to Webkit engine.
Almost is possible that we have to renamed the project (or created a new project) because K-Meleon is by definition a Gecko embed browser project and not a Webkit embed browser project.
Quote
Peter Sauer
Quote
desga2
Yes it is, other Gecko browser migrated to Webkit engine; Epiphany, Flock, and the next are Camino and K-Meleon. Technically the migration is possible.
This announcement changed our future "roadmap":
K-Meleon 1.6.x => Seamonkey 2.0.x, Firefox 3.5.x => Gecko 1.9.1.x
K-Meleon 1.7 => Firefox 3.6.x => Gecko 1.9.2.x
K-Meleon 1.8? => Seamonkey 2.1.x?, Firefox 4.0.x? => Gecko 2.0.x?
K-Meleon 2.0? => Based in Webkit engine?
All this is a supposition, we don't know if will there are developers needed to migrated the project to Webkit engine.
Almost is possible that we have to renamed the project (or created a new project) because K-Meleon is by definition a Gecko embed browser project and not a Webkit embed browser project.
Is K-Meleon still in development? Is there a K-Meleon build (1.8? 2.0?) with an up-to-date GRE? If not, will there by any?
Quote
c933103
Is it still possible to continue use gecko engine even it is not available?