Page 1 of 1

OpenWith v6.8.6 Legacy & Basilisk

Posted: 2018-01-27, 02:37
by kelendral
OpenWith v6.8.6 Legacy & Basilisk

For those like me who are running Pale Moon and Basilisk side-by-side and are totally insane about trying to get things to match this may help you out.
One of the first things to note in Basilisk when setting this addon up is that the 'Tool bar' and 'Developer Tools' options are missing from the setup page.
There is also a lack of the icon under Customize.

To fix these issues and enable the same Developer Tools and Tool bar button functionality and features one sees with this addon in Pale Moon:
content/about-openwith.js wrote: 91 -

Code: Select all

		if (appname == 'Firefox' || appname == 'Pale Moon') {
91 +

Code: Select all

		if (appname == 'Firefox' || appname == 'Pale Moon' || appname == 'Basilisk' ) {
content/openwith.js wrote: 202 -

Code: Select all

		if (appname == 'SeaMonkey' || appname == 'Pale Moon') {
202 +

Code: Select all

		if (appname == 'SeaMonkey' || appname == 'Pale Moon' || appname == 'Basilisk' ) {
content/openwith-fx.xul wrote: 41 +

Code: Select all

	<toolbarpalette id="BrowserToolbarPalette">
		<toolbaritem id="openwith-toolbarbox" class="chromeclass-toolbar-additional" label="&openwith-name;">
			<toolbarbutton id="openwith-toolbar" class="toolbarbutton-1" label="&openwith-name;"
				image="chrome://openwith/content/openwith16.png" type="menu">
				<menupopup id="openwith-toolbar-menu" />
			</toolbarbutton>
		</toolbaritem>
	</toolbarpalette>

Hope that helps. I prefer the XUL extension since it can find one's browsers without an external app, plus well, now it matches my Pale Moon install. :)

Re: OpenWith v6.8.6 Legacy & Basilisk

Posted: 2018-01-28, 17:32
by gracious1
Wow! Thanks for this!

Re: OpenWith v6.8.6 Legacy & Basilisk

Posted: 2018-02-03, 22:17
by Trapper
These directions are EXACTLY what I'm looking for....thanks kelendral for taking the time to post this. The problem is I'm failing miserably at implementing them.

I've deleted the appropriate code in lines 91 & 202, then replaced the 2 code lines with the new code & saved both files.

I've appended the supplied code to line 41 of the "content/openwith-fx.xul" file (since the instructions don't indicate to remove the existing line 41 code first). So in effect, I've added the new code starting on line 42, then saved this file also.

Lastly, I zipped all the files (making sure to only zip the files, not including the folder they were extracted to), then renamed the zip file to .xpi

Every time I try to install this new .xpi file, I'm told it's corrupt & won't install.

What am I doing wrong?

Re: OpenWith v6.8.6 Legacy & Basilisk

Posted: 2018-02-04, 00:47
by coffeebreak
Trapper852 wrote:Every time I try to install this new .xpi file, I'm told it's corrupt & won't install.

What software did you use to edit the files?
It needs to be a plain text editor such as Notepad or Notepad++.
If you used a word processor, or rich text editor (like Wordpad) it might cause such a problem.

Re: OpenWith v6.8.6 Legacy & Basilisk

Posted: 2018-02-04, 00:51
by riiis
FYI both Browser View Plus and Open With Edge, IE, Chrome, and More install and work out-of-the-box in both Pale Moon and Basilisk.

Re: OpenWith v6.8.6 Legacy & Basilisk

Posted: 2018-02-04, 03:17
by Trapper
@coffeebreak
I used EditPad Pro, an all purpose text editor used by programmers and non-programmers alike. I've used it for years without any problems. It's similar to Notepad++ in function.

As a test, I tried compiling the .xpi file in Notepad++ with the exact same results... corrupt file, won't install. It has to be something stupid I'm doing, not the fault of the text editors.

@riiis
Thanks for suggesting your versions. I tried Browser View Plus & it does give me the toolbar button that I'm after, but I'm looking at the big picture, which is trying to find out what I'm doing wrong, so that I can apply that knowledge in the future.

Re: OpenWith v6.8.6 Legacy & Basilisk

Posted: 2018-02-04, 05:15
by kelendral
Trapper852 wrote:Lastly, I zipped all the files (making sure to only zip the files, not including the folder they were extracted to), then renamed the zip file to .xpi

Every time I try to install this new .xpi file, I'm told it's corrupt & won't install.

What am I doing wrong?
Corrupt XPI
Are you using WinRAR for your zip creation?
I usually just replace the files in the existing XPI rather than try to create new one.

Re: OpenWith v6.8.6 Legacy & Basilisk

Posted: 2018-02-04, 20:48
by SpockFan02
Also make sure that the files aren't in a sub-folder within the xpi.

Re: OpenWith v6.8.6 Legacy & Basilisk

Posted: 2018-02-06, 22:28
by Trapper
I've spent the last several days meticulously dissecting this problem by testing each and every step I've done, to find what failed. To my utter amazement, the problem seems to be Winrar itself.

When I unzip the contents of the original xpi file, then immediately rezip the contents to a new xpi file (without making ANY changes), the xpi installation fails as usual, giving me a corrupt message. I made sure not to include any redundant or empty duplicate folders in the new zipping process by only selecting files themselves. I checked Winrar's settings to make sure that it's set to remove redundant folders from the extraction path (it was).

As a test, when I tried to create a new altered xpi file, incorporating the changes posted by kelendral (OP) using other compression tools, the xpi creation & installation worked perfectly on 2 separate occasions. All the new features are present & work perfectly.

Does this Winrar issue make sense to anyone?! I've always thought Winrar was the gold standard, now I'm not so sure. I feel like I'm in the twilight zone.

The good news is that it (apparently) my practices were sound & it wasn't something stupid I was doing.

Re: OpenWith v6.8.6 Legacy & Basilisk

Posted: 2018-02-08, 14:14
by kelendral
I've experienced the same thing with WinRAR.
That's why when using WinRAR I don't create a new XPI, but rather just replace the existing files in the current XPI.
I do not if or what the correct WinRAR settings are that allow creation of a new ZIP as XPI without it showing corrupt.
However, WinRAR will update an existing one OK.

Re: OpenWith v6.8.6 Legacy & Basilisk

Posted: 2018-02-08, 19:14
by Trapper
Well, this has been a real learning experience for me, namely, something is really wrong with Winrar & shouldn't be blindly trusted.

I dug around the Winrar site looking for answers, but nothing addressed this issue. No matter, all the other compression tools I used worked perfectly, so I'm moving on.

@kelendral
Thanks for all your input