@ George Hall

Whatever plugin is used must have been a nightmare to write. For sure it does not use the registry. Half of the items that I found there will not read with our macro language and many have the version number as part of the key. I think it is impossible to provide any temporary solution using a macro.

I am an impatient sort of person so I have made for myself a couple of temporary work-a-rounds for KM 74's lack of "send page as a link" and "about:plugins". These will not work for everyone. and you will have to edit the code to fit you own situation.

The first is my replacement for send page as a link. I have Outlook and it you use another program or version, you will have to adjust the code. Search your mail product for command line switches.

OutLook.kmm

#  K-Meleon Macros (http://kmeleon.sourceforge.net/wiki/index.php?id=MacroLanguage2)
#
# ---------- OutLook.kmm
# ---------- K-Meleon Macro Language to call Outlook new mail from KM ---------------
#
# Dependencies		: main.kmm
# Resources			: Microsoft Outlook
# Preferences		: -
# Version			: 1.0   2013-12-03
# --------------------------------------------------------------------------------

_OutLook_SendPage {
macroinfo="Opens new note - use paste to obtain data";
$_Outlook_data = "[title]  \n" . $TITLE  . "\n  \n" . $URL ;
setclipboard( $_Outlook_data );
exec("c:\\Program Files\\Microsoft Office\\Office12\\outlook.exe /c ipm.note /m Options=PlainText");
}

_OutLook_BuildMenu {
setmenu(_Mail_Mail,macro,"Send Page to Outlook...",_OutLook_SendPage);
}

#-------------------------------------------------------------------
$OnInit=$OnInit."_OutLook_BuildMenu;";
$macroModules=$macroModules."OutLook;";

The second is my replacement for about:plugins. It is only accurate if you install plugins globally. Note that the menu item is under EDIT - CONFIGURATION as "Plugin data."

PluginData.kmm

#  K-Meleon Macros (http://kmeleon.sourceforge.net/wiki/index.php?id=MacroLanguage2)
#
# ---------- PluginData.kmm  (for KM 74)
# ---------- Show the about:plugins using my KM 1.6.0 beta 2.6 version
# ---------- Plugins must be globally installed for this to be accurate
#
# Dependencies		: main.kmm
# Resources			: a KM of 1.6 or older
# Preferences		: -
# Version			: 1.0   2013-12-11
# -------------------------------------------------------------------------------- 

_PluginData_RunCode {
$_Snippet_url = "about:plugins" ;
exec("C:\\Program Files\\K-Meleon\\k-meleon.exe -new " . $_Snippet_url ;
}


_PluginData_BuildMenu {
	# add another option to Configure menu
	setmenu("_Config_Settings",macro,"Plugin data","_PluginData_RunCode",4);
}

## - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
$OnInit=$OnInit."_PluginData_BuildMenu;";
$macroModules=$macroModules."PluginData;";

A macro to use about:plugins may work if the plugin container has a switch that allows viewing of plugins.

Some execuatble files have switches in them that allow certain functions to be performed.

If plugin-container.exe or plugin-hang-ui.exe have some switches in them it may be possible to view plugins using a macro that uses the switch that allows viewing of plugins.

I found a way to view the about:pugins,

When Firefox views about:plugins it is displayed as an htm file.

the files in about folder in K-Meleon and place the plugins.htm in the folder to view the plugins intend of using about:plugins.

it is a temporay fix until we figure out how to fix about:plugins

about:plugins = about/plugins.htm under K-Meleoon folder or browser folder.

A macro should work if it views pligin.htm

Display about:plugins in firefox and save as pjugins.htm in K-Meleon the we can view plugins loading plugins.htm with K-Meleon 74

Quote
Goerge Hall
I found a way to view the about:pugins,

When Firefox views about:plugins it is displayed as an htm file.

the files in about folder in K-Meleon and place the plugins.htm in the folder to view the plugins intend of using about:plugins.

it is a temporay fix until we figure out how to fix about:plugins

about:plugins = about/plugins.htm under K-Meleoon folder or browser folder.

A macro should work if it views pligin.htm

Display about:plugins in firefox and save as pjugins.htm in K-Meleon the we can view plugins loading plugins.htm with K-Meleon 74

view about:plugins in firfox and save as complete webpage as About Plugins.htm

THen viwew "C:\Program Files (x86)\K-Meleon\plugins\About Plugins.htm"

Then the plugins are displayed.

That is the only fox that works for now.

James may come up with way to fix abour:plugins until he does we just have to view the "About Plugins.htm" file.

I made a small mistake while viewing "About Plugins.htm" is only shows plugins already installed.

New Plugins won't be listed unless you save "About Plugins.htm" as a complete webpage again.

In omni.ja folder chrome\toolkit\content\global contains files plugins.css and plugins.htm

The extact location is the following while using a compression program such as WinRAR which can vew omni.ja files.

chrome\toolkit\content\global\plugins.css
chrome\toolkit\content\global\plugins.htm

This must be related to about:plugings because plugins.css is displayed the source code of "About Plugins.htm"

The compolete about:plugins fix is copy the files from emebd.jar that let K-Mleon 1.6 Beta 2.6 to view aboutLplugins into omni.ja that allow Firfox to voew about:plugins.

K-Meleon 1.60Beta 2.6 has plugins.css, plugins.dtd, plugins.htm, plugins.properties, and region.properties in embed.jar at the following locations:

embved.jar/content/global/plugins.css
embved.jar/content/global/plugins.htm
embed.jar/locale/en-US/global/plugins.properties
embed.jar/locale/en-US/global-region/region.properties
embed.jar/locale/en-US/mozapps/plugins/plugins.dtd
embed.jar/locale/en-US/mozapps/plugins/plugins.properties

Firefox has has has plugins.css, plugins.htm, plugins.properties, and region.properties in omni.ja at the following locations:

omni.ja/chrome/toolkit/content/global/plugins.css
omni.ja/chrome/toolkit/content/global/plugins.htm
omni.ja/chrome/en-US/locale/en-US/global/plugins.properties
omni.ja/chrome/locale/en-US/global-region/region.properties
omni.ja/chrome/locale/en-US/mozapps/plugins/plugins.dtd
omni.ja/chrome/locale/en-US/mozapps/plugins/plugins.properties

When K-Mwlwon 1.6.0 Beta embed.jar files are copied into K-Meloen 74's omni.ja file about:plugins starts to work again.

Quote
George Hall
The compolete about:plugins fix is copy the files from emebd.jar that let K-Mleon 1.6 Beta 2.6 to view aboutLplugins into omni.ja that allow Firfox to voew about:plugins.

K-Meleon 1.60Beta 2.6 has plugins.css, plugins.dtd, plugins.htm, plugins.properties, and region.properties in embed.jar at the following locations:

embved.jar/content/global/plugins.css
embved.jar/content/global/plugins.htm
embed.jar/locale/en-US/global/plugins.properties
embed.jar/locale/en-US/global-region/region.properties
embed.jar/locale/en-US/mozapps/plugins/plugins.dtd
embed.jar/locale/en-US/mozapps/plugins/plugins.properties

Firefox has has has plugins.css, plugins.htm, plugins.properties, and region.properties in omni.ja at the following locations:

omni.ja/chrome/toolkit/content/global/plugins.css
omni.ja/chrome/toolkit/content/global/plugins.htm
omni.ja/chrome/en-US/locale/en-US/global/plugins.properties
omni.ja/chrome/locale/en-US/global-region/region.properties
omni.ja/chrome/locale/en-US/mozapps/plugins/plugins.dtd
omni.ja/chrome/locale/en-US/mozapps/plugins/plugins.properties

When K-Mwlwon 1.6.0 Beta embed.jar files are copied into K-Meloen 74's omni.ja file about:plugins starts to work again.

I made one mistake

embed.jar/locale/en-US/mozapps/plugins folder does not exist

but omni.ja has fies located at
omni.ja/chrome/locale/en-US/mozapps/plugins/plugins.dtd
omni.ja/chrome/locale/en-US/mozapps/plugins/plugins.properties

which may not do anyhting when the following embeded files are copied

embved.jar/content/global/plugins.css
embved.jar/content/global/plugins.htm
embed.jar/locale/en-US/global/plugins.properties
embed.jar/locale/en-US/global-region/region.properties

Thr fololowing omni.ja files are replaced with embed.jar files

omni.ja/chrome/toolkit/content/global/plugins.css
omni.ja/chrome/toolkit/content/global/plugins.htm
omni.ja/chrome/en-US/locale/en-US/global/plugins.properties
omni.ja/chrome/locale/en-US/global-region/region.properties

If their are anymore mistakes please find them and fix them and write about them.

Quote
George Hall
K-Meleon 1.60Beta 2.6 has plugins.css, plugins.dtd, plugins.htm, plugins.properties, and region.properties in embed.jar at the following locations:

embved.jar/content/global/plugins.css
embved.jar/content/global/plugins.htm
embed.jar/locale/en-US/global/plugins.properties
embed.jar/locale/en-US/global-region/region.properties
embed.jar/locale/en-US/mozapps/plugins/plugins.dtd
embed.jar/locale/en-US/mozapps/plugins/plugins.properties

I cannot seem to find plugins.dtd in the embed.jar file of K-Meleon 1.60 Beta 2.6. I found the other five files although some of your locations are incorrect.

I am going to have a look at omni.ja next.

K-Meleon 74 is made to read thise 4 files whuch were present in earlier versions of K_Meleon.

K_meleon 74 needs to be changed to read the new format of the files that allow viewing of pluguns in Firefox.

The files following are diferent in K-Mleon 74;

plugins.css
plugins.htm
plugins.properties
region.properties

Than the ones in K-Meleon 1.6.0 Beta2.6.

The K-Meleon 74 is still setup to read those old files instead of new ones in Firefox 25 and 25.0.1.

So do I put the old files in the new omni.ja? Please tell me again how to open a ja file.

Edit: Nevermind, I found where I asked before.



Edited 1 time(s). Last edit at 12/13/2013 01:41AM by JamesD.

Quote
JamesD
So do I put the old files in the new omni.ja? Please tell me again how to open a ja file.

Edit: Nevermind, I found where I asked before.

The compression progams WinRAR and Bandizip are able to open the oomni.ja file.

It doesn't worrk with 7-zip because 7-zip was created when mozilla still used tnhe .jar file format for chrome files such as embed.jar. Now mozilla uses the .ja file format with omni.ja.

My 7zip 4.65 opens omni.ja easily

And the best way is to use TotalCommander with 7zip-plugin to handle archives like folders (ja and jar files need Ctrl+PageDown to get into)



Edited 1 time(s). Last edit at 12/13/2013 06:10AM by rodocop.

Quote
rodocop
My 7zip 4.65 opens omni.ja easily

And the best way is to use TotalCommander with 7zip-plugin to handle archives like folders (ja and jar files need Ctrl+PageDown to get into)

I tried 7-zip 4.65 on the Mozilla Firfox 25.0.1 omni.ja file and it did not open and i could not look inside.


7-zips to open .jsr files file not .ja files. omni.ja uses a different format which newer than the 7-zip 9.20 Beta.

7-zip can only open omni.ja after a files are added with another compression program such as WinRAR.

When files are added to omni.ja by WinRAR the format changes to a zip format.
Which 7-zip can open and add files to.

The RAW unmodified omni,ja from firefox can;t be read by 7-zio.

You're right, George.

So I recommend to use TC with archive plugins to have no problems with omni.ja.

I opened the ja file with ExtractNow. I will most likely rebuild it with 7-Zip in zip format. First I have to take my wife shopping.

JamesD and roboxop

I just found that Compressed Folder function in Windows 7 can open and files to omni.ja if is renamed to omni.zip.

However, the default association for ZIP files must be set to set to windows 7.

If 7zip ro WinRAR are set to open ZIP files.

Windows 7 must be reset to the default file association for ZIP files.

The follwing 2 websites have REG files that reset Windows 7 default file associations

Windows 7: Default File Type Associations - Restore
http://www.sevenforums.com/tutorials/19449-default-file-type-associations-restore.html

File Association Fixes for Windows 7
http://www.winhelponline.com/blog/file-asso-fixes-for-windows-7/

Well,
all this is good but I don't need any other solution except my described own. And I do really recommend it to others as it's the most convenient way to work with such compressed files - look into them, modify them, update, copy, move etc.

Quote
George Hall
The files following are diferent in K-Mleon 74;

plugins.css
plugins.htm
plugins.properties
region.properties

Than the ones in K-Meleon 1.6.0 Beta2.6.

The K-Meleon 74 is still setup to read those old files instead of new ones in Firefox 25 and 25.0.1.

This absolutely does work!

Check off one more thing from the todo list.

Thanks George

Quote
JamesD

Quote
George Hall
The files following are diferent in K-Mleon 74;

plugins.css
plugins.htm
plugins.properties
region.properties

Than the ones in K-Meleon 1.6.0 Beta2.6.

The K-Meleon 74 is still setup to read those old files instead of new ones in Firefox 25 and 25.0.1.

This absolutely does work!

Check off one more thing from the todo list.

Thanks George

Eventualy I hope figure out why about:plugins doesn;t work with the firefox files.

Then we could fix K-Meleon 74 so it is more compatible with Firefox plugin container and omni.ja plugin mechanism.

If fix K-Meleon to more compatible with plugin contair then it would help fix prblesm with the flash plugi.

When K-Mleon 74 switches to full screen on some flash websites, it crashes the flash plugin.

I fully agree with you, George : making omni.ja and plugin.container work as they should would be a big progress towards a more compatible browser.

The other thing is the plugin question.

I should say the solution of these two items is more important for the moment than the rest. Unfortunately I cannot be of any help to helping solve that. I hope others can.

Mala

I just need three more items completed before I can make 74 my default browser.

1. Cookie management with a white list. Cookie Monster 3.47 does not work with 74.

2. A spelling checker.

3. A password manager.

Quote
JamesD
I just need three more items completed before I can make 74 my default browser.

1. Cookie management with a white list. Cookie Monster 3.47 does not work with 74.

2. A spelling checker.

3. A password manager.

It might help us to figure out how to use a password mamher with K-Meleon 74 my examing the password manager files in the omni.ja.

It might show the format of how of firefox passwords are stored and where they stored in firefox.

Then you could make changes to the M-Meleon browser folder or the omni.ja password files to allow us to use a password manager wuth K-Meleon 74.

Also examing the omni.ja help with other 2 problems because a lot of firfox features are stored in the omni.ja file.

I found that passwords are likely handled by code in the omni at:

chrome\toolkit\content\passwordmgr

Unfortunately I am not very useful with either js or xul. I will keep looking to see if I can find how this code get invoked. Maybe there will be something in locale.

Quote
JamesD
I found that passwords are likely handled by code in the omni at:

chrome\toolkit\content\passwordmgr

Unfortunately I am not very useful with either js or xul. I will keep looking to see if I can find how this code get invoked. Maybe there will be something in locale.

I that doesn't a temporary would be using the password manager from K-Mleon 1.6.0 Beta2.6 by copying the password files in emned.jar into omni.jar

And use some kmeleon 1.6.0 Beta2.6 settings and other files thaat may be needed form macros and modules folder.

There are two more file for passwords in Omni at:
chrome\en-US\locale\en-US\passwordmgr

I will have a look at the KM jar files.

Edit:
The spelling stuff in chrome is only a license and source code. I put there in order to comply with the license because I included spelling in beta 2.6.

Spelling is handled in beta 2.6 with files located as follows:

K-Meleon\components\spellchk.dll

K-Meleon\kplugins\spelltest.dll

K-Meleon\macros\spelltest.kmm

K-Meleon\dictionaries\

I tried copying spellchk.dll to KM 74 to see if the red line would show up under a misspelled word, but had no luck. In the 1.6 KMs that file alone would cause the red underscore.



Edited 1 time(s). Last edit at 12/14/2013 08:10PM by JamesD.

I have no idea what runs passwords in KM 1.6. These files display some text values:

embed\locale\en-US\wallet\pref-passwords.dtd
embed\locale\en-US\wallet\walletPrefsOverlay.dtd
embed\locale\en-US\wallet\wallet.properties
embed\locale\en-US\wallet\walletTasksOverlay.dtd

Quote
JamesD
I have no idea what runs passwords in KM 1.6. These files display some text values:

embed\locale\en-US\wallet\pref-passwords.dtd
embed\locale\en-US\wallet\walletPrefsOverlay.dtd
embed\locale\en-US\wallet\wallet.properties
embed\locale\en-US\wallet\walletTasksOverlay.dtd

Look for files the name password in them may be a clue

embed.jar\content\pippki is related to passwords contains password.js
omni.ja\chrome\pippki\content\pippki also has password.js file

examining password.js should make give us some clues of how password manager works.

Some other files related password manager are in the pippki folder.

Quote
George Hall

Quote
JamesD
I have no idea what runs passwords in KM 1.6. These files display some text values:

embed\locale\en-US\wallet\pref-passwords.dtd
embed\locale\en-US\wallet\walletPrefsOverlay.dtd
embed\locale\en-US\wallet\wallet.properties
embed\locale\en-US\wallet\walletTasksOverlay.dtd

Look for files the name password in them may be a clue

embed.jar\content\pippki is related to passwords contains password.js
omni.ja\chrome\pippki\content\pippki also has password.js file

examining password.js should make give us some clues of how password manager works.

Some other files related password manager are in the pippki folder.

the grepfrefs folder in something to with the password manager in K-Meleon 1.6.0 Beta 2.6.

The greprefs.js in the omni.ja is a replacement for the greprefs folder in K-Meleon 74.

K=Meleon 74 cant access the greprefs.js file in the omni.ja as long as it can't
a password manager is impossible.

Just for info : This morning I noticed that print preview doesn't work in k-meleon 74.

Mala