With all the experimentation going on with newer Geckos, wonder if there is the possibility of a beta for K-Meleon 1.7?

Tks.

N

the k-meleon development team is really moving at a snail's pace while Mozilla, on the other hand, is moving at almost supersonic speed in releasing new versions of firefox so we really don't know if there will even be a first KM 1.7 beta. if there will be one, it may take weeks or even months before it will actually happen.

heck, I'm still waiting for either a KM 1.6 beta 3 or a KM 1.6 release candidate 1.
it's been almost EIGHT months since K-meleon 1.6 beta 2 came out and no future betas were released ever since.



Edited 1 time(s). Last edit at 08/06/2011 01:09AM by 4td8s.

I suspect a KM 1.6b3 is in the works.... can't say when it may show up or if a newer version of KM 1.7 is being worked on. No news I'm afraid, but then I'm not in a position to know.

N



Edited 1 time(s). Last edit at 08/06/2011 03:19AM by ndebord.

Quote
ndebord
I suspect a KM 1.6b3 is in the works....

Mailed Dorian yesterday,
since there is no one around with access
to download page and bugs, but he may be on holiday.

One of the last changes for KM1.6b3 could be
a working plugin-check. It works in KM1.54.

www.mozilla.com/en-US/plugincheck/

Failure caused by GRE or Chrome changes
from 1.8.1 to 1.9.1.. I have no idea,
why nobody tried to fix that
in the past two years.

There are enough open bugs left for KM1.6
release candidate and most of latest changes
in KM1.6b3 should be useful for KM1.7.



Edited 1 time(s). Last edit at 08/06/2011 10:17PM by deadlock.

Quote
deadlock

Quote
ndebord
I suspect a KM 1.6b3 is in the works....

Mailed Dorian yesterday,
since there is no one around with access
to download page and bugs, but he may be on holiday.

One of the last changes for KM1.6b3 could be
a working plugin-check. It works in KM1.54.

www.mozilla.com/en-US/plugincheck/

Failure caused by GRE or Chrome changes
from 1.8.1 to 1.9.1.. I have no idea,
why nobody tried to fix that
in the past two years.

There are enough open bugs left for KM1.6
release candidate and most of latest changes
in KM1.6b3 should be useful for KM1.7.

Deadlock,

Much thanks for the updated info... a release candidate makes me drool uncontrollably. <g> As for KM 1.7, well so long as Debian keeps Gecko 1.9.2 for Ice Weasel, up-to-date code should be available for it.

Don't know enough about coding to comment, except to say that I have been around K-Meleon for longer than I care to remember and one constant as always been that at random times, things slow down. I figure that because KM has always been a Mom and Pop enterprise that that is reason enough. As there has always been only one or two people working on C++ at any one given time.

Another plus for KM has been the macro scripting language and in particular KKO's marvelous rewrite of it. This has helped many in the KM community provide extensions that to my mind put FF to shame. I've had macros written for me in a day or two when I ask for help and that is not something you can say about the rest of Mozilla.

N



Edited 1 time(s). Last edit at 08/07/2011 12:37AM by ndebord.

Quote
ndebord
a release candidate makes me drool uncontrollably.

Ooops?!
You misunderstood, there was no answer yet.
You'll need developers for a release candidate,
if you don't want to fix the bugs for yourself.

Quote
ndebord
been around K-Meleon for longer than I care to remember

As many others here.
Never got used to using other browsers.
Only tried to compile KM last Winter,
because K-Meleon 1.6 didn't start on my
old Celeron notebook (without SSE).

Bad idea.

Quote
ndebord
Another plus for KM has been the macro scripting language

A view lines can replace lots of addons, but
I still didn't find a hidden Easter egg in KM.

Quote
deadlock

Quote
ndebord
a release candidate makes me drool uncontrollably.

Ooops?!
You misunderstood, there was no answer yet.
You'll need developers for a release candidate,
if you don't want to fix the bugs for yourself.

Quote
ndebord
been around K-Meleon for longer than I care to remember

As many others here.
Never got used to using other browsers.
Only tried to compile KM last Winter,
because K-Meleon 1.6 didn't start on my
old Celeron notebook (without SSE).

Bad idea.

Quote
ndebord
Another plus for KM has been the macro scripting language

A view lines can replace lots of addons, but
I still didn't find a hidden Easter egg in KM.

deadlock,

Nah, just the idea of a release candidate makes me drool, be it real or a mirage!

<g>

Gotta ask KKO for an easter egg.

Do not have a direct line to Dorian, but then he has always been shy about posting, a trait he shares with several other KM developers over the years.

N

Quote
deadlock

One of the last changes for KM1.6b3 could be
a working plugin-check. It works in KM1.54.

www.mozilla.com/en-US/plugincheck/

Failure caused by GRE or Chrome changes
from 1.8.1 to 1.9.1.. I have no idea,
why nobody tried to fix that
in the past two years.

There are enough open bugs left for KM1.6
release candidate and most of latest changes
in KM1.6b3 should be useful for KM1.7.

1.) The plugins page error is in

https://www.mozilla.com/en-US/plugincheck/

in this line 672/673.

checkPlugins('https://plugins.mozilla.org/pfs/v2';

The document which it refers too: contains

"[]"

I assume that it calls default code from GRE191 source tree that is located in:

./toolkit/mozapps/plugins...


Which AFAIK lands in toolkit.jar during build.
K-Meleon does currently not use/have this part of toolkit.

This source tree part contains no xpt or dll as far as I can see.

Possibly: ./components/plugins.xpt & pluginGlue.js could help to do the job.

They are part of K-Meleon 1.6 GRE. No idea whether they work?

2.) I agree. If bugs are fixed for a 1.6 version it can be probably reused.

I am not competent to say whether the open bugs are show stoppers that must be fixed before coders/devs can move on to the next version. So I can only agree with deadlock's evaluation.



Edited 1 time(s). Last edit at 08/07/2011 10:57AM by guenter.

Quote
ndebord

Nah, just the idea of a release candidate makes me drool, be it real or a mirage!

for now, a KM 1.6 RC seems to be just a dream, a mirage. same for KM 1.7 beta.
wait 'til year 2013 or 2014 or even longer for either one (or both) to actually happen (that is a BIG if and when).

Why kmel development is so slow? few developers? no time?

Quote
fra
Why kmel development is so slow? few developers? no time?

fra,

The latest developer is living a life and has no time. He produced everything from version 0.9 up until now, so unless a C++ developer appears, there will be no future development for K-Meleon. (FYI, Camino is in the same boat... the last Gecko used for both is 1.9.2, Camino further ahead with that engine than K-Meleon.)

With Embed killed off by Mozilla Corp., the future of derivatives that use operating system specific APIs is poor. In the beginning there were 3 main offshoots: Galeon for Linux, Camino for OSX and K-Meleon for Windows. Galeon begat Epiphany which made the transition to WebKit and Camino and K-Meleon are both looking to find C++ coders. <sigh>

N



Edited 1 time(s). Last edit at 02/22/2012 01:43AM by ndebord.

Quote
fra
Why kmel development is so slow? few developers? no time?

yup that's all. [few or no devs] + [no time] = [no new KM 1.7]
simple as that. and since KM 1.7 is based on Gecko 1.9.2, Mozilla will be ending all support for Gecko 1.9.2 based programs like Firefox 3.6 in late April 2012.

There are unofficial types. I keep up with FF 3.6+ on my version.
http://home.dbdbdugbug.operaunite.com/Projects/content/KMFILES/Download-K-Meleon-db.html

You can update it your self.
http://home.dbdbdugbug.operaunite.com/Projects/content/KMFILES/Z_UPDATING.html

Other than that, for major K-meleon programing, im not there.
I looked at making a K-meleon 1.8. There is no way.
Anything past FF 3.6 is to far out there to work with K-Meleon.

K-meleon is secure, you just need to get into the about:config & change things
to secure it up, for the future.
http://home.dbdbdugbug.operaunite.com/Projects/content/KMFILES/Readme.txt
http://home.dbdbdugbug.operaunite.com/Projects/content/KMFILES/A_KMFILES_HELP.html

My 1.7 version is kept up with the latest FF 3.6 types & holds up good.
But it has no history. I was hoping for a Macro that would take over the
job of history. Im not sure if it could be fixed that way for it.
For me I only see 2 bugs, history & password.
If those 2 things would be fixed it would make K-meleon 1.7 better to use.
The Security part is in the about:config & if there could be a sandbox added to the browser, or something that makes an sandbox watch KM, (Avast has a sandbox setting.) this would make it better.

Just because the engine is old, does not make it bad!



Edited 4 time(s). Last edit at 03/26/2012 05:43PM by dugbugoffice2.

Quote
dugbugoffice2
My 1.7 version is kept up with the latest FF 3.6 types & holds up good.
But it has no history. I was hoping for a Macro that would take over the
job of history. Im not sure if it could be fixed that way for it.

I have tried to make a macro to record history. There are problems with the macro language in 1.7 version. Dates will not report using the x=injectJS command and file extension is left off when writing an ini file. We could manage without the file extension, maybe, but how to have a history without datetime stamps?

$_Snippet_Date = injectJS( "var d = new Date(); function returnVar(d){return d;} returnVar(d);");
alert( $_Snippet_Date, "Date()", INFO);

This does not work in 1.7 but does work in 1.6 versions.

Hanlon’s razor is an eponymous adage named after Robert J. Hanlon that states: “Never attribute to malice that which is adequately explained by stupidity.”

JamesD

dugbugoffice,
history.dll from the last KM CCF ME (size 77312b) works fine with your build.
Just overwrite your existing one.

You can download it here

New history.dll works just fine.

Hanlon’s razor is an eponymous adage named after Robert J. Hanlon that states: “Never attribute to malice that which is adequately explained by stupidity.”

JamesD

Quote
JamesD
There are problems with the macro language in 1.7 version. Dates will not report using the x=injectJS command and file extension is left off when writing an ini file.

$_Snippet_Date = injectJS( 'var d = new Date(); function returnVar(d){return d;} returnVar(d);');
alert( $_Snippet_Date, 'Date()', INFO);

This does not work in 1.7 but does work in 1.6 versions.

@JamesD
1) Why did you pick 'new Date()' as an example?
Is there any working injectJS command for 1.7a2?
I guess it was disabled completely in that alpha.

2) What file extensions are you talking about?

@all
That 'new' history.dll is an old one.
It uses khistory.dat which has a different
file format. It works, but it was made
for version 1.5 or older.

The original history.dll from 1.7a2 package didn't
work, because it was compiled with wrong libraries.
Anyone with VS2005 can build a working file with
CVS sources. It uses history.dat in profile just
like 1.6 did. The history.dat files are
interchangeable.

Quote
deadlock
1) Why did you pick 'new Date()' as an example?
Is there any working injectJS command for 1.7a2?
I guess it was disabled completely in that alpha.

2) What file extensions are you talking about?

I needed a date string when I thought I would have to do a macro for history in ver 1.7. I had experimented with obtaining a system date in KM 1.6.0 beta 2.4. I made all the following work there. I did not obtain a usable date in 1.7.

$_Snippet_Value = injectJS( "Date()"); 
alert( $_Snippet_Value, "datestring", INFO);

$_Snippet_Date = injectJS( "var d = new Date(); function returnVar(d){return d;} returnVar(d);");
alert( $_Snippet_Date, "Date()", INFO);

$_Snippet_Year = injectJS( "var d = new Date(); dm = d.getFullYear();  function returnVar(dm){return dm;} returnVar(dm);");
alert( $_Snippet_Year, "d.getFullYear()", INFO);
 
$_Snippet_Month = injectJS( "var d = new Date(); dm = d.getMonth();  function returnVar(dm){return dm;} returnVar(dm);");
alert( $_Snippet_Month + 1, "d.getMonth() +1", INFO);

$_Snippet_Day = injectJS( "var d = new Date(); dm = d.getDate();  function returnVar(dm){return dm;} returnVar(dm);");
alert( $_Snippet_Day, "d.getDate()", INFO);

$_Snippet_WeekDay = injectJS( "var d = new Date(); dm = d.getDay();  function returnVar(dm){return dm;} returnVar(dm);");
alert( $_Snippet_Day, "d.getDay()", INFO);

$_Snippet_DateString = injectJS( "var d = new Date(); dm = d.toDateString();  function returnVar(dm){return dm;} returnVar(dm);");
alert( $_Snippet_DateString, "d.toDateString()", INFO);

As for the file extension, I had a path to profilefolder plus History.ini. The ini file was written as as Hist17 without an extension.

$_Hist17_Path = getfolder(ProfileFolder)."\\History.ini";

and

	iniwrite($_Hist17_DateTime, "1" , $_Hist17_HistURL_1, $_Hist17_Path);
	iniwrite($_Hist17_DateTime, "2" , $_Hist17_HistURL_2, $_Hist17_Path);
	iniwrite($_Hist17_DateTime, "3" , $_Hist17_HistURL_3, $_Hist17_Path);
	iniwrite($_Hist17_DateTime, "4" , $_Hist17_HistURL_4, $_Hist17_Path);
	iniwrite($_Hist17_DateTime, "5" , $_Hist17_HistURL_5, $_Hist17_Path);
	iniwrite($_Hist17_DateTime, "6" , $_Hist17_HistURL_6, $_Hist17_Path);

Resulted in this file. Filename is 'Hist17'.

[]
1=http://www.myway.com/
2=http://apnews.myway.com//article/20120328/D9TPFAM00.html
3=http://www.dailyrotation.com/index.php
4=http://thechive.com/category/girls/
5=http://www.duke-energy.com/north-carolina/outages/current.asp
6=http://kmeleon.sourceforge.net/wiki/NewPreferences

Notice that the place for a date is empty. It has only the [] symbols.

I think I have run into other problems with the macro language in 1.7 but my memory is such that, right now, I know exactly what those were. Those items and history are why my default browser is still 1.6.

I hope this info is useful.

Hanlon’s razor is an eponymous adage named after Robert J. Hanlon that states: “Never attribute to malice that which is adequately explained by stupidity.”

JamesD

@JamesD
If you didn't test all injectJS commands
used by K-Meleon 1.7a2 default installation
and selected injectJS with 'new Date()', only,
to get a working 'personal' history macro,
then my question is:

Is there a working injectJS command in your 1.7a2?

If there is no command, you'll have to replace
all components that use injectJS, or create
a new binary of k-meleon.exe.

You said you ran into other problems with 1.7's macro language.
Are there examples?

@ deadlock

I have not found an injectJS() that works in 1.7. Send page as a link, page properties - images and links don't work either.

Hanlon’s razor is an eponymous adage named after Robert J. Hanlon that states: “Never attribute to malice that which is adequately explained by stupidity.”

JamesD

Quote
JamesD
I have not found an injectJS() that works in 1.7. Send page as a link, page properties - images and links don't work either.

Now I remember. All that works fine in 1.7 CVS version.
Last summer I told dorian about a faulty setting
in CVS code of injectJS. He applied changes here:

BrowserWindow.cpp-1.19+1.20

Obviously this bug is in 1.7a2 only
and it was no date() bug.

What 'other problems' did you have with 1.7's macro language?



Edited 1 time(s). Last edit at 03/30/2012 03:15PM by deadlock.