-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update & merge from PM's JSView Revive #3
Comments
@tmtisfree Is all of the above correctly about yourself? |
Yes. |
@tmtisfree Wow, you're tough to track down! Are you interested in keeping an open development repo of JSView Revive on GitHub, either here (as I invited earlier) or under yourself? I'll happily give you whatever rights you want here, if that's your wish. |
Sorry for not responding on the PM forum. The JSView code is not online anywhere and I don't plan to develop it further. So you can get the latest code from the Pale Moon repository, update here from it and take over the development if you wish. Some credentials are needed to update the Pale Moon repository with a new version. I can check with the PM staff to know if I can share them with you or I you need new ones. Is that OK? (Note that I plan to travel a lot in the next 2 months, so be patient.) |
The purpose of this So, giving me PM credentials will be counterproductive. Hang on to them somewhere safe, &, next time someone wants to update the XPI, we'll request the PM devs then. |
I'm not trying to offend anyone, but this repository has an older version (v2.0.8) of JSView Revive - the current is v2.1.8. Firefox will soon be using WebExtensions exclusively, so the Firefox version in this repository will soon be outdated. It might have been better to fork nekman's port to Chrome here since Firefox's WebExtensions will now work with that same code. I don't know anything about the Pale Moon browser, so I'm not sure if it is also being updated to use WebExtensions. Just to clarify, is this repository meant to target Firefox or Pale Moon, or both? |
Actually, @Mottie, this repo has the last version I could find of JSView that I could find before it was abandoned/discontinued/removed, before the Revive edition existed. 😁 The purpose of this issue is to update to the latest (last?) Revive edition, & the preceeding discussion is preparatory for the subissues in OP. But feel free to submit PR to speed up progress — the rate I'm going, This repo is exclusively for the XPI version, per terms of https://github.com/rejuvenate/rejuvenate. Other versions are likely to be more religiously maintained than this, & this serves those of us who don't wish WebExtensions on our Ff-related browser(s) — like Pale Moon. |
This add-on had never really been either abandoned nor discontinued, it had had a life between v2.0.8 and when I took it over (v2.1.2). Please see the release notes from the Revive version. |
@tmtisfree I really can't find those notes.… Are you the original author |
No, I am TMTisFree ;) Versions are listed in the (also attached) file named "mod-notes.txt" in the Revive version. |
Ahh, I see it: That means I'm gonna hafta find a way to credit "Philip Chee." Anyone got a GitHub handle? |
https://addons.palemoon.org/extensions/jsview-revive/
To Do:
csdev
"The text was updated successfully, but these errors were encountered: