Quote
guenter
Then we must have two macros.
$OpenURL=$tux==""?"chrome://rvjmimeedit/content/mimeType.html", "file:///".getfolder(RootFolder)."/browser/extensions/{fb4eaeed-d1c9-45d1-a2bb-f2876142daf0}/mimetype.html";
Quote
JujuLand
Quote
guenter
Then we must have two macros.
No, just use it:
doneQuote
guenter
You forgot to add any of Your changes in rvjmimeedit.txt. You added French locale, a great new macro and changed the position of the info file, mimeType.html ...
I did not sign my last change - so SVP do that for me when You update to the next version. Thank You in advance.
CHANGE LOG IMHO You edit above:
Version 0.6.1 K - 13 October 2014, Preview existing MIMETypes fixed, guenter.
Quote
guenter
p.s. If You use this: chrome://rvjmimeedit/content/mimeType.html for Windows
mimeType.html should IMHO be in ./content/ not in ./{fb4eaeed-d1c9-45d1-a2bb-f2876142daf0}/mimeType.html
Quote
guenter
Maybe that caused Your problem on Linux? Of old it used to be where You placed it.
But I found that it only can be called as chrome in content or content/pref/
chrome://content/pref/mimeType.html chrome://content/mimeType.htmland it fails
$OpenURL=$tux==""?"chrome://rvjmimeedit/content/mimeType.html","file:///".getfolder(RootFolder)."/browser/extensions/{fb4eaeed-d1c9-45d1-a2bb-f2876142daf0}/mimetype.html"
$OpenURL=($tux==""?"chrome://rvjmimeedit/content/mimeType.html" : "file:///".getfolder(RootFolder)."/browser/extensions/ {fb4eaeed-d1c9-45d1-a2bb-f2876142daf0}/mimetype.html");
I agree with you, but don't forget that it's talking about Linux Firefox version running under Linux.Quote
Siria
It contains also a chrome chapter, but no mention that chrome-paths wouldn't work under Linux.
Perhaps some path mistake in this mime-extension itself?
Quote
JujuLand$OpenURL=($tux==""?"chrome://rvjmimeedit/content/mimeType.html" : "file:///".getfolder(RootFolder)."/browser/extensions/ {fb4eaeed-d1c9-45d1-a2bb-f2876142daf0}/mimetype.html");
Quote
siria
Those complicated addon-extension paths are a complete mystery to me yet, so I had just kept the original paths you guys have posted.
snip...
Perhaps some path mistake in this mime-extension itself?
snip...
Still, the 7z by you and the one by guenter have a different folder structure.
Quote
guenterQuote
siria
Perhaps some path mistake in this mime-extension itself?
2.) Impossible.
That is an anciant part of the Mozilla/SeaMoney suite XUL code.
....
The basic code is not by a Bob Janc or a guenter but we just altered it
to work with a new app and do the job after some other codes changed.
Quote
siria
Quote
guenterQuote
siria
Perhaps some path mistake in this mime-extension itself?
2.) Impossible.
That is an anciant part of the Mozilla/SeaMoney suite XUL code.
Perhaps some path mistake in those alterations? :cool:
That security stuff might well be another prob too, not just in Linux perhaps also in those ultramodern windows systems.
Version 0.6.2 - 15 November 2014, by alain, siria and guenter : bugfix, Kmm modified, mimeType.html relocatet to .contentr/pref, guenter. Version 0.6.2 - 14 November 2014, by guenter, siria and alain : kmm modified and prefs added to make it avalaible immediately when installed, alain. Version 0.6.1 K - 13 October 2014, by guenter review existing MIMETypes fixed, guenter. Removed looked state that was only used when the code that drives the addon was used to work with browser prefs, guenter. Version 0.6 K74 - 12 October 2014, by guenter : uses ID by Bob Janc because K-Meleon can use that now, guenter. Updated CSS and code to play with 74/esr24. 12th.10.2014, guenter. To do. Preview existing MIMEtypes, guenter. Merged with code and strings from K-Meleon's mtypes 0.5.1 extension by alain, kko and guenter and restricted the code to use features known and used by K-Meleon 1.6. Hannover, 08th.01.2009, guenter.
# K-Meleon Macros (http://kmeleon.sourceforge.net/wiki/index.php?id=MacroLanguage) # ---------- rvjmimeedit Extension (MIME Type Editor) ------------------------------------------------------------------- # # Dependencies : main.kmm (OpenURL) # Resources : - # Preferences : - # Warning : to use it, don't forget to uncheck mtypes.kmm in preferences # no more needed, as install disable it # ------------------------------------------------------------------------------------------------------------------ # We always want this as separarate Window so that we can drag it before an open mimeType.html minetypes{ macroinfo=_("Edit mimeTypes.rdf"); $OpenURL=($tux==""?"chrome://rvjmimeedit/content/pref/pref.xul":"file:///".getfolder(RootFolder)."/browser/extensions/{fb4eaeed-d1c9-45d1-a2bb-f2876142daf0}/chrome://rvjmimeedit/content/pref/pref.xul"); &OpenURL_InNewWindow; mytypes{ macroinfo=_("Addon Manger"); $OpenURL="about:addons"; # In case you have a modified version of main.kmm which allows to open About items in new tab instead # of new window. Just comment the first line to come, and uncomment the next one &OpenURL_InNewWindow; #setpref(BOOL,"extensions.rvjmimeedit.openinwindow")==true ? $ExecMacros="OpenURL_InNewWindow":$ExecMacros="OpenURL_InNew";&ExecMacros_Frames; } mimetypes{ macroinfo=_("MimeTypes Information"); $OpenURL=($tux==""?"chrome://rvjmimeedit/content/pref/mimeType.html":"file:///".getfolder(RootFolder)."/browser/extensions/{fb4eaeed-d1c9-45d1-a2bb-f2876142daf0}/chrome://rvjmimeedit/content/pref/mimeType.html"); # In case you have a modified version of main.kmm which allows to open About items in new tab instead # of new window. Just comment the first line to come, and uncomment the next one &OpenURL_InNew; #getpref(BOOL,"extensions.rvjmimeedit.openinwindow")==true ? $ExecMacros="OpenURL_InNewWindow":$ExecMacros="OpenURL_InNew";&ExecMacros_Frames; } # ----- PRIVATE _mytypes_BuildMenu{ # edit menu setmenu(KMAbout,macro,_("Edit mimeTypes.rdf"),minetypes); setmenu(KMAbout,macro,_("MIME T&ypes Info"),mimetypes); setmenu(Preferences,macro,_("Addon Manager"),mytypes); } $OnInit=$OnInit."_mytypes_BuildMenu;"; # ------------------------------------------------------------------------------------------------------------------ $macroModules=$macroModules."rvjmimeedit;";
Quote
guenter
To do: find out why original mtypes.kmm still does not work side by side.
Quote
siria
You can remove me from the history, since it doesn't contain any contributions by me. And even if there were a line, that would be peanuts not worth mentioning considering it would be 0.0x % of that whole extension.
What I still keep riddling, what's your "modified version of main.kmm" thing about? Some trick requiring frames?
(sorry am lazy too and too bothersome to get the offline machine out of the closet ;-P)
PS: please do occasionally a quick test of your published macros. Mistakes happen, but for the x-th time the menus are still mixed up, although you even had noticed it meanwhile
PS2: What do you mean with that?
Quote
guenter
To do: find out why original mtypes.kmm still does not work side by side.
I hope you don't mean that both extensions shall run at the same time, because you keep disabling that fully intentionally.
PS3 ;-)
And is there some automatism now that every 74 extension gets an own window pref by KM? Because I cannot find the definition in this package.
Quote
JujuLand
here is the modified main.kmm which allows to have functions like about, ... to be opened in a new tab instead of a new window (but which also allows new window. Now we have the choice ...
$OpenURL=($tux==""?"chrome://rvjmimeedit/content/pref/pref.xul":"file:///".getfolder(RootFolder)."/browser/extensions/{fb4eaeed-d1c9-45d1-a2bb-f2876142daf0}/chrome://rvjmimeedit/content/pref/pref.xul"); &OpenURL_InNewWindow;
Quote
JujuLand
ok, but if someone wants to change this behavior, he must change the macro, else just a pref, which can be done if Dorian accept to reintroduce it, with a included macro or in kmprefs.
Quote
JujuLand
&OpenURL_InNewWindow = opens a new window.
That's not exactly "guru" stuff guenter! Even you can do that, after ten years of user support with 8000+ postings
# We always want this as separarate Window so we can drag it before an open mimeType.html
Quote
guenter
You are right, that's not exactly "guru" stuff, alain
Quote
guenter
the reason is IMHO in the XUL code. Both items called by the two macros have the name "pref.xul" and the same "ID". IMHO that is the deeper reason. Since Your macro works around this problem You have found this out too..
Why only remove the kmm??Quote
guenter
and finally we need a solution so that the kmm can be inside the add-on so that it can be removed with the addon..
Quote
guenter
Both items called by the two macros have the name "pref.xul" and the same "ID". IMHO that is the deeper reason. Since Your macro works around this problem
Quote
guenter
You IMHO knew why You used pref-filetypes.xul instead of pref.xul in Your macro.
So do I. That elegantly avoided the problem, same name, same ID.
# K-Meleon Macros (http://kmeleon.sourceforge.net/wiki/index.php?id=MacroLanguage) # ---------- kmimeedit Extension (MIME Type Editor) ------------------------------------------------------------------- # # Dependencies : main.kmm (OpenURL) # Resources : - # Preferences : - # ------------------------------------------------------------------------------------------------------------------ mytypes{ macroinfo=_("Edit mimetypes"); $OpenURL="chrome://kmimeedit/content/pref/options.xul";&OpenURL_InNewWindow; } mimetypes{ macroinfo=_("MimeTypes information"); $OpenURL="chrome://kmimeedit/content/pref/mimeType.html";&OpenURL_InNew; } KMimeEdit_new{ macroinfo=_("Add new file type (MIME Type), open with MIME Type info list"); &mimetypes; &mytypes; } aboutaddons{ macroinfo=_("Addons Manager"); $OpenURL="about:addons";&OpenURL_InNew; } # ----- PRIVATE _mytypes_BuildMenu{ # edit menu setmenu(Preferences,macro,_("Edit mimeTypes.rdf + Types Info"),KMimeEdit_new); setmenu(Preferences,macro,_("Addons manager"),aboutaddons); } $OnInit=$OnInit."_mytypes_BuildMenu;"; # ------------------------------------------------------------------------------------------------------------------ $macroModules=$macroModules."kmimeedit;";
(the native macros do follow this, there are no _() in their setmenu lines)Quote
kko
Note that <menuName> and <itemName> are translated automatically if possible. In regard to the browser's startup performance, do not use the _() statement in conjunction with setmenu().