huh

Nope. It's still going strong.

There haven't been any new releases since v0.7, though I believe some of the plugins have been updated.

Look at the Project Status link:

http://kmeleon.sourceforge.net/resources/status.php

As the bar chart shows, very nice trend indeed.
Thank you developers! ;-)

May be this project is (still) alive. I don't 'monitor ' the delveloper's
mailing-list. Perhaps they are just bashing/crashing/burning Phoenix there? ;-)

Lele needs to fix that page. The release date is wrong. It was 2002.

Are there any plans for a new release in the near future ?

Also the version info in the current k-meleon.exe (source file MfcEmbed.rc) still says it's version 0.6.5, copyright 2001

At least the About K-Meleon dialogue says copyright 2000-2002 and
Version 0.7 Build 700 Compiled Thu Oct 31 00:54:24 2002.
I think that's the latest official release.

I wouldn't mind if there were beta/nightly/monthly etc. precompiled
binaries to try out. I haven't really investigated if these are available.
At least the project home page doesn't convey the feeling that the
project is going strong. These forum pages are very good and helpful.

When I look at the project page I expect to see more weekly news maybe
lifted from the mailing list or from the forums (what were the most hectic/
important issues there). Also if some major bugs were fixed I woul like to read it
from the news section. The news should be in the beginning. Of course I
understand that maintaining web pages depends on available resources and priorities.

I have looked at the Phoenix pages (sorry to mention that;-) They have clear
milestones, roadmap and timelines. The project seems to has clear
purpose. I don't say that K-Meleon project doesn't have a purpose.
I just wish that the project page could somehow reflect the current
development and future plans. No wonder if casual browsers wonder
"has development stopped".

Phoenix seems to be feature driven project. It is no use to release
new K-Meleon builds if there aren't new features or bug fixes
(what features are we waitng for - what goodies iare behind the horizon?)
I come from Netscape 4.7 environment- I still miss some of it's
browser's preferences. I know that you can customise your browser
to achieve at least some of them (own colors, clear location bar etc.).

Maybe it would be a good idea if there were downloadable Netscape and IE-centered customised versions with the same outlook (skins), menus and shortcuts to ease transformation. Of course some people would say: those
browsers already exist, why emulate old browsers. You should ask: why
people use browsers, why should they switch to K-Meleon.

1. They wan't fast browsing with good rendering. K-Meleon provides that.
They wan't some usability features they are used to: autocompletition, global history: not so lucky.
2. They don't wan't to switch to K-Meleon if it is too different from their
previous browsers (learning curve.). They are used to the look and menus of their
previous browser. It isn't a question (not at least in the beginning) which is
the better browser. It is a usability issue. Are they familiar enough with the interface. If there were custom made installs for Netscape and IE switching would be easier. Later, when they are hooked to K-Meleon. they could install/adapt to K-Meleons 'native' environment.

I don't mean that the core K-Meleon should be significantly changed.
Almost all these changes could be implemented with skins, macros, menus,
plugins ( I am aware what the resources section contains.)
Thus no bloat or speed decrease to the core K-Meleon.

I must however say that every half decent browser should have
global history, link coloring, user colors and url-completition as a default option.
What K-Meleon has is speed, configurability and macros! It is time to put
that configurability into a good use.

Default K-Meleon (native) install shouldn't be that boring old IE-look
(without too much feel) or a bare bones construction set.. K-Meleon should
have its own colorful and tasteful icons and skins to separate it from other browsers.Eye candy is also psychologically important.

There you have some goals. I hope you can implement at least some of them.
Projects which can't deliver die. This is not criticism, it is constructive
observations ;.) Better stop now before I start to ramble.

K-Meleon doesn't have global history because embedded Mozilla doesn't officially support it. Visited link colors and a URL autocompletion require a global history. Now you can make visited link color work by installing appcomps.dll and mork.dll from Mozilla (basically adding the core of Mozilla's global history functionality) but there still won't be a global history window (ctrl-h). That would have to be added as a K-Meleon plugin since Mozilla implements this in XUL. Supposedly Mozilla will add basic global history functionality to the embedded core but who knows when that will be.

There is a doc about making visited color links work by installing the two dlls but I don't remember where it is. Basically you put the two dlls in the components subdirectoty and delete compreg.dat (and possibly xpti.dat) and that's it. A history.dat file will appear in your profile subdirectory containing visited links.

I agree that K-Meleon shouldn't look like IE by default but you can download a Netscape 4.x skin and a Netscape-like 'K' throbber from the resources page to make K-Meleon now more like Netscape.

The doc (history/visited links):
http://tln.lib.mi.us/~amutch/pro/kmeleon/khistfiles.htm
but, dammit, I couldn't make it work, so follow the instructions rigorously! :-)

Devs know that URL completetion is asked for:
http://www.geocrawler.com/lists/3/SourceForge/9632/0/10250320/
:-)

Try deleting both compreg.dat and xpti.dat and restarting K-Meleon. K-Meleon will rebuild both files. Also try not using the browser.visited_color pref in prefs.js as the default is already set to #551A8B (purple) via all.js. If it's working then a file history.dat will appear in your profile subdirectory. To reset visited links you have to delete history.dat.

Thanks a lot man! It turns out that I do in fact have the history.dat..
and the visited links *sometimes show* as red but not always.. (ok, I'll try the
default purple setting, but how would that make a difference?)
I get the same effect when I disable all stylesheets.. I don't get it! :-P
Thanx
/H

Yeah, I think K-Meleon's best default skin would the Galeon look.

The doc (history/visited links):
http://tln.lib.mi.us/~amutch/pro/kmeleon/khistfiles.htm

New file and instructions posted for K-Mel 0.7

Regarding using a later Mozilla build, this can be done manually if Mozilla is also installed by simply copying the newer DLLs (54 total) from the Mozilla directories to K-Meleon (xcopy /s /d "c:\Program Files\Mozilla\*.dll" "c:\Program Files\K-Meleon") and deleting compreg.dat and xpti.dat in K-Meleon\components so they can be rebuilt. I've done this and have been using K-Meleon 0.7 with Mozilla 1.2 final for over a week now with no problems.

asmpgmr,

This probably only worked because we used a beta 1.2 and you used the final 1.2. In general, the code changes between the different versions will break K-Meleon.

Yes obviously it has

Jim,

Don't be so lazy. We've got development updates right on the home page.

Not really, the home page only mentions an update to one plugin, and a unimportant one at that considering K-Meleon is based on Mozilla and not the M$-Borg(tm) browser. The updated beta macros plugin isn't even mentioned.

Are there any plans for 0.8 ? What features will be added ? What bugs will be fixed ? I have several open bugs and RFEs in the bugs tracking system but there has been no activity on any them recently. I also check the CVS repository and there haven't been many checkins to K-Meleon recently. I read that over a year elapsed between 0.6 and 0.7 (I started with 0.7), hopefully it isn't another year before 0.8 appears.

asmpgmr,

Did deeper into CVS. There have been a number of plugin checkins. We'll be adding more details news-wise shortly.

Andrew,

I am aware that work has been done on some of the plugins (like macros) but nothing has been done on the main program in approximately 2 months.

Also when will a non-debug build of the new macros.dll be posted ?

Just a note about copying over later mozilla 1.2.x dlls into the kmeleon directory. It does works for me with moz 1.2.1 so long as I copy over the dlls from /dist and /dist/component.