: K-Meleon Forum
K-Meleon development related discussions.
A word you have used in your post: "Ogilvy", has been banned from use. Please use a different word or contact the forum administrators.
[quote=ndebord] [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] desga2, Flock didn't rename itself when it made the move and name recognition is important. I spent a lot of years in advertising at Ogilvy & Mather and that is the central core premise of that biz. IF KKO's superb macro language can be adapted to WebKit, you would be a step up on all the others, as that single change made my day with KM. I've read all the online justifications from Mozilla and don't get their reasoning, 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. SIGH[/quote]
K-Meleon forum is powered by