Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 


roytam1

My build of New Moon (temp. name) a.k.a. Pale Moon fork targetting XP

Recommended Posts

:no:

Let's not start this whole name changing bit again. There is nothing to be gained from it, and only more work to be created.

There's a relevant point in another thread (that thanks to the lack of a proper BBcode editor in IPB I can't just copy and paste here :realmad:) about how this may affect addons and related applications, requiring them to be modified to recognize the resulting renamed binary.

Share this post


Link to post
Share on other sites

Posted (edited)
14 minutes ago, LoneCrusader said:

how this may affect addons and related applications, requiring them to be modified to recognize the resulting renamed binary.

if only content of branding folder are changed, there should be no compatibility issue.

 

14 minutes ago, LoneCrusader said:

Let's not start this whole name changing bit again. There is nothing to be gained from it, and only more work to be created.

So I raised the hurdle to accept pull request only so hoping people won't try to flood this thread too much.

Edited by roytam1
  • Like 1

Share this post


Link to post
Share on other sites
Posted (edited)

Why not also change some HELP entries?

ekbVmsJU_o.jpg

Xnl5vHHb_o.jpg

____________________________________________________________________________

e7ATXJYN_o.jpg

Y5QQqV2l_o.jpg

____________________________________________________________________________

I have to disconnect, I don't have time to find the string in about: config related to the "Help"

KWGfHQyC_o.jpg

I'm sure some MSFN members will complete the missing puzzle.:hello:

Edited by Sampei.Nihira
  • Like 2

Share this post


Link to post
Share on other sites
Posted (edited)
12 hours ago, Mathwiz said:

How sensitive ('MAT') they seem to be about not calling unofficial builds "Pale Moon," it's amusing that their own Web page for unofficial builds commits that very same error ... FWIW, I do think @roytam1 should develop his own branding, but that has proven to be more easily said than done; we can't even come up with a browser name that everyone's OK with!

Yes, I think that your observations are correct. And, I think that to 'get out front' on this (Naming the 'NEW MOON' Browser and changing the 'successful install' SHTML page content) is the best strategy. And, in my view, the best three to 'work this out' (RT, VistaLover, Mathwiz) are now somewhat 'engaged' in that dialog. MAYBE you three should take this to a PRIVATE MESSAGING situation here on MSFN.org if possible. And even VistaLover noted that the changes that I orginally suggested them are NOT very difficult to implement them (Name the Browser, change the install SHTML message).

OR, you could wait around for a certain 'MAT' person to RETURN here again
to 'ingratiate' himself for 'Old Times' sake? :)

Edited by TechnoRelic

Share this post


Link to post
Share on other sites
1 hour ago, Sampei.Nihira said:

Why not also change some HELP entries?
(snipped)
I don't have time to find the string in about: config related to the "Help"
(snipped)
I'm sure some MSFN members will complete the missing puzzle.

It's controlled by pref app.support.baseURL

default value is http://www.palemoon.org/support/

When you choose "Help", the browser tries to load
http://www.palemoon.org/support/firefox-help
which then auto-redirects to 

http://www.palemoon.org/faq.shtml
 

;)

Share this post


Link to post
Share on other sites
9 hours ago, LoneCrusader said:

Let's not start this whole name changing bit again. There is nothing to be gained from it, and only more work to be created.

There's a relevant point in another thread (that thanks to the lack of a proper BBcode editor in IPB I can't just copy and paste here :realmad:) about how this may affect addons and related applications, requiring them to be modified to recognize the resulting renamed binary.

There are already bugs with existing addons (at least with Basilisk). Options dialog in GreaseMonkey doesn't work. Also this particular fork's default configuration breaks ColorfulTabs (it expects Firefox version number in the user agent string).

Share this post


Link to post
Share on other sites
1 hour ago, UCyborg said:

Options dialog in GreaseMonkey doesn't work.

Have you, by any chance, tried GreaseMonkey for Pale Moon

https://github.com/janekptacijarabaci/greasemonkey/releases/latest

(file greasemonkey-3.31.4-pm_forkBranch.xpi) ?

Personally, in Serpent 52.9.0 I'm using latest ViolentMonkey (2.10.5) as userscript manager (of the WE type, still supported in St52 - but not official Basilisk/UXP). ;)

  • Upvote 1

Share this post


Link to post
Share on other sites
18 minutes ago, VistaLover said:

Have you, by any chance, tried GreaseMonkey for Pale Moon

https://github.com/janekptacijarabaci/greasemonkey/releases/latest

(file greasemonkey-3.31.4-pm_forkBranch.xpi) ?

Thanks, this one works. Still find it odd; GreaseMonkey 3.11 doesn't have compatibility issues with Firefox 51. Waterfox on the other hand runs them all.

Share this post


Link to post
Share on other sites
21 hours ago, LoneCrusader said:

There's a relevant point in another thread (that thanks to the lack of a proper BBcode editor in IPB I can't just copy and paste here :realmad:) about how this may affect addons and related applications, requiring them to be modified to recognize the resulting renamed binary.

I too once suggested changing the names of the .exe files, but it turns out that requires too many other changes; so I think now we're only talking about changing the names of the .7z files on @roytam1's page, some default prefs (so various links would point to Web pages controlled by @roytam1 vs. MCP), the displayed names, and the logos. The .exe file names would remain the same, and the other changes shouldn't affect add-on compatibility.

12 hours ago, TechnoRelic said:

And, in my view, the best three to 'work this out' (RT, VistaLover, Mathwiz) are now somewhat 'engaged' in that dialog.... And even VistaLover noted that the changes that I originally suggested are NOT very difficult to implement (Name the Browser, change the install SHTML message).

It is a lot of work in total, though - as @Sampei.Nihira noted, there are several Help menu links to fix as well - and the work is probably best suited to a Web designer, which I am not. I've already suggested names (Titan; Apophis) and could probably even create logos, but not all the necessary Web pages based around them - at least not if you want them to look decent!

22 hours ago, LoneCrusader said:

Let's not start this whole name changing bit again. There is nothing to be gained from it....

The benefit to be gained depends on how likely Matt or MCP is to take drastic action (such as making PM/Basilisk closed-source, thus cutting us off from all future enhancements) next time they think @roytam1 is to blame for unwelcome New Moon/Serpent support requests. Rebranding won't end those unwelcome requests, but it would give @roytam1 a good defense against their likely future complaints.

  • Like 1

Share this post


Link to post
Share on other sites
13 hours ago, VistaLover said:

It's controlled by pref app.support.baseURL

default value is http://www.palemoon.org/support/

When you choose "Help", the browser tries to load
http://www.palemoon.org/support/firefox-help
which then auto-redirects to 

http://www.palemoon.org/faq.shtml

I think @VistaLover has a point, here. Changing both app.support.* strings to default straight here to this thread on MSFN is easy to do and might be a good 1st step. This @roytam1 might implement already in his next installment of the compiled versions of all browsers he's providing modded versions for XP. It's much simpler than rebranding, uncontroversial and breaks nothing, while being an incontrovertible proof something is actually being done to proactively prevent people from going to PM forums for support. :yes:

  • Like 3
  • Upvote 1

Share this post


Link to post
Share on other sites

uB0-legacy has just been updated to version 1.16.4.11; those without uB0 updater installed, should download and install manually:

https://github.com/gorhill/uBlock/releases/tag/firefox-legacy-1.16.4.11

Also, latest NM28-compatible language-packs have been (recently) updated to v28.6.0_RC2 :

https://github.com/JustOff/pale-moon-localization/releases/tag/28.6.0_RC2

:P

  • Like 4

Share this post


Link to post
Share on other sites
Posted (edited)

In my St 52 copy (dated 2019.04.19), app.support.baseURL still points to Mozilla! So it seems the default was only changed in PM/NM.

We can still change it (in both versions), along with browser.feedback.URL in NM (app.feedback.baseURL in St), which is opened when the user clicks Help / Submit feedback and currently points to the PM forums in both browsers. And as suggested long ago, app.releaseNotesURL should point to http://rtfreesoft.blogspot.com/search/label/browser vs. the Palemoon.org release notes.

That's only three prefs per browser, but would clean up the Help menu and reduce the number of unwelcome support requests going to the PM forums.

I believe all these defaults are buried somewhere in <install dir>\browser\omni.ja. It might take a bit of searching to find & fix them all; an easier approach might be to override them by putting a new .js file in <install dir>\defaults\pref.

Oops: Discovered a minor wrinkle with changing app.support.BaseURL: Help / Keyboard Shortcuts no longer works :( So it might be best to just revert to Mozilla for that pref.

So the final prefs I ended up with are:

app.feedback.baseURL;https://msfn.org/board/topic/177125-my-build-of-new-moon-temp-name-aka-pale-moon-fork-targetting-xp/?do=getNewComment
app.releaseNotesURL;http://rtfreesoft.blogspot.com/search/label/browser
app.support.baseURL;https://support.mozilla.org/1/firefox/%VERSION%/%OS%/%LOCALE%/

(change app.feedback.baseURL to browser.feedback.URL for NM)

Edited by Mathwiz
  • Like 1

Share this post


Link to post
Share on other sites
Posted (edited)

@roytam1 -- @VistaLover -- @Mathwiz  <--

http://www.palemoon.org/unofficial.shtml

Okay, I was 'over thinking' this (my view) for NEW MOON Browser.
What about to just 'blank out' (remove) this above listed URL ???
So, do NOT open ANY URL at all. Just have a 'blank' Browser Screen open.
That way, the reference to PALE MOON disappears.
And Users SHOULD then think to use the (Menu) HELP choices.
So, you make the HELP choices be URLs that aim at RT websites.

Which, there is a clearly misleading ERROR on the HELP = TROUBLSHOOTING INFORMATION
It references "New Moon" there, like this -->
" ... common questions about New Moon, check out our *support website* ... "
And the clickable URL for *support website* = http://www.palemoon.org/support/
Which, that clickable URL needs to instead be aimed at say the MSFN.org RT Forum Area (here).

As others suggested, the other (Menu) HELP URLs should aim at appropriate RT websites.
Finally, even the BOOKMARKS that come with the NEW MOON Installation, should be CHANGED
to aim at instead appropriate RT websites (or be removed), as opposed to PALE MOON websites.
Eventually, it will become clear to Users that NEW MOON is a FORK of PALE MOON anyway.

Hoping all three of you will agree that this is a good 'quick and dirty' fix for this overall issue.

Added later: @Mathwiz has posted just below, and seems to agree with views here.
And (thanks!) 'Mathwiz' has taken on the task of doing the 'Github Pull Requests' needed.
'Mathwiz' and 'VistaLover' now seem to share a common cooperative viewpoint.   
It appears that RT is 'engaged' too. I anticipate significant improvement soon.

Edited by TechnoRelic

Share this post


Link to post
Share on other sites

I agree; I never liked those "you've successfully upgraded" pages anyhow. I think simply blanking out the pref would prevent any such page from opening in the first place - not even a blank page. (Setting the pref to "about:blank" would presumably open a blank page, but that would be confusing.)

I looked over the UXP source tree and think I found where that pref is stored, as well as a couple of others mentioned above. So I cloned the tree, made the changes, and created a "pull request" as @roytam1 requested; but please keep in mind I'm a total noob at Github, so even though this was just a few simple changes, I'm not sure I did it right :blushing:

  • Like 1

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...