Open FrostKnight opened 1 month ago
Pale Moons add-ons/extensions wont work. SeaMonkey (SeaLion) is not FireFox (Pale Moon). The UI's are structurally different. I was able to convert some FF/PM extensions, and modify some existing SM extensions and themes. You can get them here: https://github.com/wicknix/SeaLion/releases/download/33.0.0/SeaLion-Extras-33.0.0.zip
Sadly SeaMonkey never got the interest of addon/extension developers like Firefox did and thus has fewer to choose from. Ask those remaining XUL extension developers to support SM, then we could make more of them work on SeaLion.
Pale Moons add-ons/extensions wont work. SeaMonkey (SeaLion) is not FireFox (Pale Moon). The UI's are structurally different. I was able to convert some FF/PM extensions, and modify some existing SM extensions and themes. You can get them here: https://github.com/wicknix/SeaLion/releases/download/33.0.0/SeaLion-Extras-33.0.0.zip
Sadly SeaMonkey never got the interest of addon/extension developers like Firefox did and thus has fewer to choose from. Ask those remaining XUL extension developers to support SM, then we could make more of them work on SeaLion.
Huh... okay. Well I got 5 working currently that are worthwhile. ublock origin legacy astroskipper's version 1.16.4.35 works.
palemoon's latest ematrix also works and then the rest of the addons you made seem to work.
I must admit, it looks nice so far.
Permissions plus could have been useful also. But no big deal yet.
How often do you make new builds of this? As often as Moonchild or more often or less often?
Oh and btw, I found a way to find all python2.7 links that I want to change to tauthon.
git rev-list --all | xargs git grep -F python2.7
not to mention I have a tauthon patch already that gets most of them fixed.
In any case, thank you for the web browser.
Oh btw, you should update those addons whenever you can.
Maybe I should ask xul devs to support sealion as well from now on as well. Idk... lol
Btw, this is the newest greasemonkey that would work with the userscripts I want:
Due to hardware limitations and lack of time i really only build for PowerPC Linux now. I quit building for MacOS and x86_64 Linux. Users of those OS's have a slew of browsers to choose from. PowerPC Linux doesn't. The UI is pretty much good to go, so that doesn't see many updates. If you want to stay current just rebuild every so often with the latest UXP.
As for GreaseMonkey, it was never 'officially' made available for SeaMonkey. The version i included was ported by someone years ago and is the only known version i'm aware of that seems to work with SeaMonkey.
If you get tauthon working, and have a clean patch, i'd consider adding it.
Due to hardware limitations and lack of time i really only build for PowerPC Linux now. I quit building for MacOS and x86_64 Linux. Users of those OS's have a slew of browsers to choose from. PowerPC Linux doesn't. The UI is pretty much good to go, so that doesn't see many updates. If you want to stay current just rebuild every so often with the latest UXP.
As for GreaseMonkey, it was never 'officially' made available for SeaMonkey. The version i included was ported by someone years ago and is the only known version i'm aware of that seems to work with SeaMonkey.
If you get tauthon working, and have a clean patch, i'd consider adding it.
I did get it working actually, but I had to change a few things and if I were to give you my patch, it would break with 2.7 for other people. This being all said, do you routinely with each update change the useragent? so if I keep building from source correctly, it will have whatever user agent you meant it to have?
Loaded question, but thought I would ask.
Oh and by the way, as a final note, I found a reliable way to find all python2.7 mentions in the source code. So I will have no problems now without going through endless searching. :)
I did a search earlier this week on my searx instance and found this:
git rev-list --all | xargs git grep -F python2.7
That helped me immensely in finding all that I needed to change. Problem of course is, you change it, then regular python2.7 doesn't work anymore. get what I am saying?
Btw, I thought you were no longer supported x86 as in 32 bit. I didn't realize you meant 64 bit too.
but anywho, with each upgrade, I still am curious each time I build your new version, will it have the useragent if changed for the new version? Just was curious
If you change the application version, that change will display in the user agent string. https://github.com/wicknix/SeaLion/blob/main/navigator/config/version.txt If you don't want to mess with that, just change the user agent string in about:config
If you change the application version, that change will display in the user agent string. https://github.com/wicknix/SeaLion/blob/main/navigator/config/version.txt If you don't want to mess with that, just change the user agent string in about:config
But I am asking if each time I build from source with your newest release, if that is sufficient to have the benefits of the new useragent. I assumed this is true, I was just asking.
Btw, I know you said x86_64 is not important given there are other options, but there isn't any Borealis like web browser alternatives online. In any case, I actually apologize, this question was probably a stupid one.
Of course if I build from your newest release and uxp, it will have the same user agent of the new verson. Sorry for bothering ya. Its a good web browser either way.
I checked and it uses less cpu power than palemoon.
greasemonkey fork newest https always and http inquirer sasuga ublock origin the latest of astroskipper's build if possible also.
Up to you, but yeah, I can't install from palemoon's addon area.