I have uploaded a new unofficial updated variation KM-16-S2014.
from the brand-new Seamonkey 2.0.14, Gecko 1.9.1.19 (Thanks to Guenter).
The profiles folder will be created inside the K-Meleon main folder,
and should leave profiles from other versions untouched.
If, when in Linux, you want this folder inside the wine configuration directory
because of property rights problems, rename the file profile.ini
inside the K-Meleon main folder to for example profile.ini-renamed before the first start.
Note : This version needs the 80's runtimes. Download MSvce8dist.exe from
http://jujuland.pagesperso-orange.fr and install it.
I did contact mr. kairo on whether (or not) there will be any more new SM 2.0 releases after SM 2.0.14 and he told me that SM 2.0.14 will be the last one once SM 2.1 goes final later this May.
So it looks like SM 2.0 may suffer the same fate as FF 3.5; SM 2.0 may soon be EOL'ed once the final release of SM 2.1 gets released.
Thank you for the info.
So further updates for K-Meleon would have to be
based on Firefox-3.6.x, because Seamonkey files
working with K-Meleon would not be available anymore.
I have made for personal use a version KM-16-3617,
based on FF-3.6.17, which works ok with k-meleon.exe
from KM-17-alpha.
So for a while, as long as FF-3.6 will be supported,
this should be updatable.
Quote 4td8s
I did contact mr. kairo on whether (or not) there will be any more new SM 2.0 releases after SM 2.0.14 and he told me that SM 2.0.14 will be the last one once SM 2.1 goes final later this May.
So it looks like SM 2.0 may suffer the same fate as FF 3.5; SM 2.0 may soon be EOL'ed once the final release of SM 2.1 gets released.
it looks like I may have to take these previous comments back, Fred.
there may be just one more SM 2.0 release (most likely 2.0.15) coming, even though SM 2.1 final had just came out Friday afternoon Pacific time of June 10.
there may be just one more SM 2.0 release (most likely 2.0.15) coming, even though SM 2.1 final had just came out Friday afternoon Pacific time of June 10.
though the Seamonkey folks right now have been either silent or undecided about another new SM 2.0 release. truly hard to tell what direction they're going with SM 2.0.x currently. there's some talk that they're gonna push out SM 2.2 beta after FF 5.0 final comes out.
even the SM folks are moving at a quicker pace similar to Mozilla Firefox because of their rapid release process.
there may be just one more SM 2.0 release (most likely 2.0.15) coming, even though SM 2.1 final had just came out Friday afternoon Pacific time of June 10.
though the Seamonkey folks right now have been either silent or undecided about another new SM 2.0 release. truly hard to tell what direction they're going with SM 2.0.x currently. there's some talk that they're gonna push out SM 2.2 beta after FF 5.0 final comes out.
even the SM folks are moving at a quicker pace similar to Mozilla Firefox because of their rapid release process.
Let's hope they do so, because as of yesterday 1.9.2.18 is the latest version and FF 3.5 seems not to update nicely and suggests a bump up to 3.6.18. Will try with Shiretoko nnightlies, but without much hope.
I have found out, that K-Meleon 1.6 runs also
with the files of Xulrunner 1.9.1.20pre.
Debian Squeeze is the stable branch of one of the
main Linux distributions, and it has a very conservative
attitude concerning the applications that it uses in its
rolling releases.
The browser of Debian is Iceweasel, which is actually
Firefox with a different name. The heart of Iceweasel
in Debian Squeeze is Xulrunner 1.9.1.x .
This is updated usually with backports as soon as
securitry flaws appear in Firefox.
There is now a Xulrunner 1.9.1.20pre for Linux, but also
for Windows in the Mozilla nightlies.
I presume, that Xulrunner 1.9.1 will soon be updated to
Gecko 1.9.1.20 for Linux, and hopefully also for Windows.
As Debian Squeeze will probably not change from Gecko 1.9.1.x
to a higher Gecko version, I hope that updates for
Xulrunner 1.9.1 will continue for a while.
Debian releases new stable versions usually every
2 years. Debian Lenny 5.0 came out in 2009,
Debian Squeeze 6.0 came out in 2011, so the next
stable Debian 7.0 would appear in 2013.
This gives K-Meleon 1.6 a chance to survive for
a while as it is, provided that Xulrunner 1.9.1.x
would be also updated in a Windows version.
As Xulrunner 1.9.1 as well as k-meleon.exe from 1.7
need the 80's runtimes, and the older kplugins need the
70's runtimes, the 70's and 80's dlls would both have to
be present in a variation based on Xulrunner 1.9.1.x .
Quote Fred
As Xulrunner 1.9.1 as well as k-meleon.exe from 1.7
need the 80's runtimes, and the older kplugins need the
70's runtimes, the 70's and 80's dlls would both have to
be present in a variation based on Xulrunner 1.9.1.x .
Fred
Which 70's kplugins should be updated?
With available sources?
All versions work well with 90's runtimes too,
as Guenter and me found out. Plugins usually do NOT
dependent on compiler version of K-Meleon.exe.
(Last winter's spelltest.dll was an exception.)
1.6b2 K-Meleon.exe works with GRE compiled with 90's runtimes.
For my personal 1.6 with Gecko 1.9.2.x from FF 3.6.x
and using k-meleon.exe from KM 1.7 I could not
use the kplugins from 1.6. I had to replace them
with the kplugins from KM 1.5 , and they needed the 70's
runtimes to work.
The kplugins were :
macros, fullscreen, bookmarks , history and privacy.
It is possible, that the kplugins from 1.6 work
with Xulrunner Gecko 1.9.1.x . I have not checked
that yet. But anyhow, it is no problem to add
the 70's runtimes to the K-Meleon main folder.
Many may even have them already in their Windows system.
But more important is the problem to have a working
Gecko platform in the future, because K-Meleon in its
present form does not work with files from Firefox 5
at all.
quote]Firefox 3.5 is no longer receiving security and stability releases. Remaining Firefox 3.5 users will receive an automated update notification for Firefox 3.6.18 as well.[/quote]
@FRED
---
>personal 1.6 with Gecko 1.9.2.x from FF 3.6.x
---
Typo? 1.7 uses 1.9.2 like FF3.6
You're using 1.7 as your personal browser?
Sorry, didn't start development of 1.7 yet.
I'll stay with 1.6 while fixing bug by bug.
Have a brand new KM every day.
---
>k-meleon.exe from KM 1.7 I could not use the kplugins from 1.6.
---
Since some kplugins are compiled against GRE,
there may be problems. Bookmarks, history and privacy
should have problems. History.dll never worked for me in KM1.7.
What happens if you press CTRL+H in 1.7?
Does it require a combination of kplugins to work?
But others (like macros.dll) should work, because they have no dependencies.
(Tested fresh compiled macros.dll in 1.7 without problems.)
---
>with Xulrunner Gecko 1.9.1.x
---
KM GRE is compiled from mozilla component inside
source packages (xulrunner, seamonkey, firefox).
Their sources contain an identical updated mozilla component.
I've checked that since December.
Only the binary files you're using are different.
Could not find any 1.9.1.20pre.sources yet.
---
>But more important is the problem to have a working
>Gecko platform in the future, because K-Meleon in its
>present form does not work with files from Firefox 5
>at all.
---
Where is D.B.? Any sign of life? Latest change was for GRE 2.0.
Where is d-e-s-g-a-2? Still translating?
I don't know what will happen. It is like milking a dead cow.
But then again, Firefox-light or Seamonkey-light
- with KM features and KM branding will always be an option.
Did you count the devs that compiled KM since 2005?
My hope is, that this branch will be further updated because of
the fact, that Debian depends on it for Debian Squeeze.
If windows versions will also , I don't know.
When speaking of "personal" browser , I was thinking of a
not published personal experimental version.
The combination of 1.6 with k-meleon.exe from 1.7 , the kplugins
of 1.5 and the gecko 1.9.2 from Firefox 3.6 worked for me
satisfactorily .
FireFox with 1.9.1.19 got kicked from the server.
I still have these:
firefox-3.5.17.source.tar.bz2
firefox-3.5.18.source.tar.bz2
firefox-3.5.19.source.tar.bz2
---
>The combination of 1.6 with k-meleon.exe from 1.7 , the kplugins
>of 1.5 and the gecko 1.9.2 from Firefox 3.6 worked for me
>satisfactorily .
---
K-Meleon1.7.exe starts up in 1.6 directory with working history.
K-Meleon1.7.exe can't load old Sessions from 1.6.
Which part of 1.6 did you use?
I used KM 1.6 for everything except for k-meleon.exe
from 1.7 and kplugins from 1.5 , together with
Gecko 1.9.2.x .
There may be of course things that do not work
correctly, but it's usable.
Quote Fred
I used KM 1.6 for everything except for k-meleon.exe
from 1.7 and kplugins from 1.5 , together with
Gecko 1.9.2.x .
There may be of course things that do not work
correctly, but it's usable.
Fred
Fred,
I would be curious to find out why you are using this particular combo of parts from different KMs?
Quote Fred
There is not much difference to KM 17 except
for the kplugins from KM 15.
This provides a working history and may also be
a bit more stable.
I have uploaded now a variation KM-16-F3618
based on Firefox 3.6.18 and Gecko 1.9.2.18 .
This needs k-meleon.exe from KM 17 to work.
Fred
Fred,
Thanks, I'll try that. I have another variation based on Guenter's work which has a a working history too. Haven't looked at what other kplugins from Km 1.5 might also go with this hybrid. Thanks.
Quote 4td8s
even the SM folks are moving at a quicker pace similar to Mozilla Firefox because of their rapid release process.
more like rabid releases ;D
oh whatever. it looks like the rapid or "rabid" release process Mozilla has will ultimately send K-meleon to the nearest graveyard (look what happened to Netscape and Flock recently - those two browsers are now obsolete) since you guys are unable to keep up with the newest gecko versions that Mozilla is rapidly releasing.
it looks like so far SM 2.0.14 is the last release of the 2.0 series but the Seamonkey team hasn't yet decided on EOLing SM 2.0x yet.
As one looks back at KM versions of old, it is readily apparent that bug fixes have always been available. As KM does not use XUL (for much), many times over the years, KM has been secure when FF and SM have not been. As for EOL for 3.6.xxx, well let us wait and see. Mozilla has blinked over Asa's outrageous statements and has told the Enterprise Community that YES, after all, they do wish to support them.
AFAIK, the next releases of KM will be 1.6 and probably a 1.7 beta, which will keep us current for now. What the future will bring is yet another story, one not written yet IMO.
N
Edited 1 time(s). Last edit at 07/01/2011 07:26AM by ndebord.