Quote
The version number is not just to be trendy. It fools website which only check the version number for compatibilty.
Quote
rodocop
adodupan had made the setdefault replacement for old KM, working from new js-file inside kmprefs.jar (exe-file is not needed more).
This one - as I can suggest - works in KM74 too. My assemblies have it biult-in.
Quote
George Hall
The SetDefault.exe from K-Meleon 1.6.0Beta2.6 works with K-Meleon 74Beta
SetDefault.exe only displays error message the first times it is used,
Also, "Set program access and defaults" displays K-Meleon 1.6.0 in Custom Configuration.
I tried SetDefault with Windows 7 64Bit and set K-Meleon 74Bets as the default browser created K-Meleon Folder with K-Meleon shorcuts in "All Programs."
SetDefault.exe also put a K-Meleon shortcut on tghe desktop and in "Quick Launch"
We only fix to installed correctly when SeytDefault is first ran and display K-Meleon 74 in Custom Configuration instead of K-Meleon 1.6.0
Quote
George Hall
When K-Meleon 74Beta is first launched about:home displays Settings, History, and Open last session at the bottom right hand corner of the web page.
I rather changes settings from a menu instead of a web page.
Quote
rodocop
adodupan had made the setdefault replacement for old KM, working from new js-file inside kmprefs.jar (exe-file is not needed more).
This one - as I can suggest - works in KM74 too. My assemblies have it biult-in.
Quote
soccerfan
Quote
rodocop
adodupan had made the setdefault replacement for old KM, working from new js-file inside kmprefs.jar (exe-file is not needed more).
This one - as I can suggest - works in KM74 too. My assemblies have it biult-in.
A while ago, disrupted had made kmdefaulter2 (for newer km?)
http://kmeleonbrowser.org/forum/read.php?9,91993
Folks could try and check if this still works.
Quote
George Hall
Quote
soccerfan
Quote
rodocop
adodupan had made the setdefault replacement for old KM, working from new js-file inside kmprefs.jar (exe-file is not needed more).
This one - as I can suggest - works in KM74 too. My assemblies have it biult-in.
A while ago, disrupted had made kmdefaulter2 (for newer km?)
http://kmeleonbrowser.org/forum/read.php?9,91993
Folks could try and check if this still works.
Extension that require tools usually have to run the whole time that the K-Meleon Browser is running.
kmdefaulter2 may increase the memory overhead becuase it may run continously,
SetDefault does run continously so it does not increase the memory overhead.
Quote
George Hall
I tried put SetDefault.exe in browser folder in K-Meleon 74Beta
Then SetDefault.exe worked when I clicked "Set as Default Browser" in Browser preferences.
The addition of Browser folder or the location of kmprefs in omni,ja seems to changed the location needed for SetDefault.exe for to work.
_localdocs_KMmacrolanguage { macroinfo=_("View information on the K-Meleon MacroLanguage"); $OpenURL="resource:///defaults//localdocs//macrolanguage.htm"; &OpenURL_InNew; }
Quote
George Hall
If Kmprefs.jar was in the browser folder then SetDefault.exe would run correctly in K-Meleon 74Beta.
Becuase kmprefs looks for SetDefault.exe from folder above the chrome folder.
CurProcD is the Current Process Directory which is the K-Meleon root folder.
The new location of kmprefs prevents SetDefault.exe from running in the Browser Preferences.
Quote
George Hall
Having kmprefs.jar and SetDefault.exe in the K-Meleon 74Beta browser folder solves two problems.
1. SetDefault.exe runs from the Browser Preferences.
2. kmprefs.jar in the browser folder allows SetDefault.exe to set the default
extensions to the "K-Meleon Web Browser from the Browser Preferences.
Also you you need remove the word browser from the "Install location" to set K-Meleon 74Beta when setting default browser from the Browser Preferences.
However, SetDefault.exe does not set K-Meleon 74Beta as the Default Browser for the protocols for FTP, HTTP, aand HTTPS
Quote
rodocop
I have a question too: is it supposed final release to have all chrome jars inside omni.ja (like in beta) or in traditional KM folder structure (like in 74b-d builds)?
What would the final architecture look like?
Quote
George Hall
In Firefox the spplication folder is the browser folder instead of the firefox.exe driectory.
I found this by reading a bug poating which is not a bug Here:
https://bugzilla.mozilla.org/show_bug.cgi?id=840555
Thats why CurProcD does not launch SetDefault.exe when click "Set as Default Browser" in the Browser Preferences.
The following function does not work in K-Keleon 74beta because browser folder is the application folder.
},
setDefault: function() {
var proc = Components.classes["@mozilla.org/process/util;1"]
.createInstance(Components.interfaces.nsIProcess);
proc.init(getFile(getFolder("CurProcD"),"SetDefault.exe"));
proc.run(true,[pref.getCharPref("general.useragent.locale")],1);
},
This function is located in kmprefs contents in the file pref-browsing.xul
This function needs to chnaged or we could keep SetDefault.exe in the browser folder in K-Meleon 74Beta.
I understand this. But the 'open' folder structure allows easier extensibility for KM by its own addons - 'unpack and use'.Quote
guenter
The omni.ja(r) are to accelerate start up. Sensible to use. I am regurgitating
info from Mozilla.org. About two or more years old - so do not ask me for links.
Quote
rodocop
I understand this. But the 'open' folder structure allows easier extensibility for KM by its own addons - 'unpack and use'.Quote
guenter
The omni.ja(r) are to accelerate start up. Sensible to use. I am regurgitating
info from Mozilla.org. About two or more years old - so do not ask me for links.
Would this possibility be available in new KM (may be in Profile folder)?
Quote
guenter
@ Dorian: Translation question. Do we have layers again or still tabs?
You wrote layers.
Can I still translate as Tab?
If so? I am almost through the KMeleon.kml
Quote
guenter
Localization does not work in this beta version. The browser cannot find the kml.
Quote
rodocop
I have a question too: is it supposed final release to have all chrome jars inside omni.ja (like in beta) or in traditional KM folder structure (like in 74b-d builds)?
What would the final architecture look like?
Quote
Zero3K
Btw, when I tested the beta in this thread, it crashed after opening a couple of folders via their assigned nicknames.
Quote
Dorian
Quote
guenter
@ Dorian: Translation question. Do we have layers again or still tabs?
You wrote layers.
Can I still translate as Tab?
If so? I am almost through the KMeleon.kml
Sorry, I think I used the wrong file. I'm not used to that locale settings
Quote
Dorian
Quote
guenter
Localization does not work in this beta version. The browser cannot find the kml.
Can you send me your locale?
Quote
guenter
Is there any chance that we can reuse the other files that were in locales folder such as k-meleon.dll, bookmarks.dll, favorites.dll...?
Quote
guenter
That would give the update project a good start with many translations finished except for the chrome/locale files.
Quote
guenter
Quote
Dorian
Can you send me your locale?
Yes. I (stern.daler) sent it at this moment to a dorian at kmeleonbrowser.
Quote
Then goto F2 GUI Appearance and set it to e.g. French. When You close the en-US Preferences chrome Window the K-Meleon native kml menues are already in French.
It surprises me always how You managed to do that.
Quote
p.s. I sometimes think the strings from the K-Meleon.dll, history.dll etc. should also be moved into a kml. And maybe those from K-Meleon Chrome also. The now obsolete Orca browser by Avant project did something like that.