Jump to content

Mathwiz

Member
 View Profile  See their activity

  • Posts

    1,830

  • Joined

  • Last visited

  • Days Won

    50

  • Donations

    0.00 USD 

  • Country

    United States

 Content Type 

Everything posted by Mathwiz

  1. Mathwiz
    I suppose I should ask how you feel about RoyFox (perhaps with variations as @Mcinwwl suggested). I know you'd rather we not rebrand at all, but if it happens, we still want your opinion on what the new branding should be. I'll give mine: I like "Moebius" for Serpent 55. I've been labeling my Serpent 55 icons "Moebius" long before @Matt A. Tobin suggested using the name. The others, I don't have particularly strong feelings about. We could use all, some, or none of his suggested names. (Although if we go with Whistler, his suggested replacement for New Moon, we do already have a rather nice logo for it.) AIUI the name New Moon is a placeholder name built into the Pale Moon source repo and is automatically given to any unofficial builds of Pale Moon; it's not something @roytam1 came up with on his own (if it were we wouldn't be having this discussion in the first place). I think there's some confusion here. All of the browsers under discussion target Windows XP and up. There aren't different browsers for different Windows versions. AFAIK none of these run on unmodified Win 2000. (With KernelEx, some may work; I don't know.) That said, I do like your idea of using a "base" name like RoyFox with a "modifier," which could be @Matt A. Tobin's suggested names. So RoyFox Whistler would be @roytam1's Pale Moon fork, RoyFox Neptune would be his Borealis fork, etc.
  2. Mathwiz
    If you delve back into the original 200-page thread, you'll find plenty of suggestions for new names. None caught on, probably because we soon had far too many to choose from! I tried to avoid that this time, figuring @Matt A. Tobin's suggested names were good enough and I didn't want to start another avalanche of name suggestions So far the leading alternative suggestion seems to be RoyFox and variations thereon. Which would also be fine by me. ================ Well yes, but I think the immediate concern is rebranding New Moon, Serpent, Navigator, and Interlink (mail/news). The others (FF 45 SSE, Arctic Fox, K-Meleon) can remain as they are for now. So maybe four polls (five if you consider Serpent 52 and 55 separate).
  3. Mathwiz
    FF 45 probably looks at addons.mozilla.org, and uBO Updater is probably not hosted there any more. At least, a search doesn't bring it up, which would make sense because it's probably a pre-WebEx app (otherwise it wouldn't run on NM, PM, or official Basilisk, which are its primary targets) and therefore banned from AMO. I got lucky: my Serpent 55 (which also uses AMO) updated to the new uBO version on Dec. 16, when uBO Updater 1.6.7 was still working.
  4. Mathwiz
    You're right, of course; those languages are closely related and I just got them mixed up in my head. Actually I just remembered: it's rey in Spanish; roy is French! Apologies to speakers of both languages. It sounds like JustOff (author of uBO Updater) is essentially taking over further development of the legacy branch of uBO while Gorhill concentrates on the WE branch. Probably just as well.
  5. Mathwiz
    Anyone who finds the suggested "Whistler" branding for NM 28 objectionable, should let us know now, while there's still time to change it. Seems pretty innocuous to me, but you never know what might turn folks off unless you ask! For the @roytam1 NM browsers that are usually updated each week, the best way to do what you want would be to wait until the version number changes, then download the last build of the previous version. That would be closest to the eventual release version. OTOH, if you always want the latest, greatest version, @i430VX has an installer that takes the drudgery out of updating your browser! I'm sure it doesn't mean the same thing in Chinese, but in Latin, "Roy" means "king;" so for me, "RoyFox" conjures up an image of a fox with a crown on its head! Then again, that might trigger a "raccoon"-like reaction with some folks.... Edited to add that @caliber suggested a nice "RoyFox" logo a few pages back. No crown but it looks nice to me.
  6. Mathwiz
    I don't think that @roytam1's Arctic Fox for XP, FF 45 for SSE PCs, or K-Meleon builds are affected at all. Arctic Fox already has its own branding.
  7. Mathwiz
    Admittedly, there's zero benefit to me from new branding. At best, we'll get some spiffy new icons, and new artwork in Help / About, but the core functionality of our UXP-derived browsers isn't changing. The difference I see is that this time, @Matt A. Tobin is offering to do a good portion of the necessary work. And I don't see that we're sacrificing anything; if we are, please enlighten me. I'd be much more dubious about this if I though we were losing anything concrete .
  8. Mathwiz
    It doesn't matter, because Windows Media Foundation doesn't exist in XP. Microsoft added that feature in Vista. On Win 7, I often set media.wmf.enabled to false for testing (so the browser won't look for it, forcing it to use alternate media decoders such as Primetime). You might also set it false if your Windows version has a WMF bug you find intolerable; otherwise I'd leave it at true for normal browsing.
  9. Mathwiz
    OK that's progress; we now know the changes that broke APZ/tiled compositing came before that alpha release of FF 52. We know that SM 2.48 works, so it's pretty likely that FF 51 works too; but I haven't actually tested FF 51. Perhaps I should do that next, just to be sure.
  10. Mathwiz
    Learned a new word today! Although in these parts, we still call it, uh, a still... It's a bit belated, but I wanted to say thanks for that tip! It's finally given me a way to maintain multiple Firefox versions on the same PC, each with its own profile, without a kludge like setting up separate Windows users (and having to log out and back in) to access each version. Just make sure to include the intended FF version in the name of each profile you set up. Very useful when you want to test FF versions ranging from 45 through Quantum to "Firefox Browser" (or whatever the name of the week is). Even on XP, I now have FF 45 SSE, FF 52 ESR, and FF 53 (patched to run with XomPie) all coexisting in relative peace.
  11. Mathwiz
    I tend to agree. Perhaps @dencorso can move the last few dozen posts about branding to their own thread? Be careful, though; there are a few unrelated posts strewn among them!
  12. Mathwiz
    Branding is hard work. You don't need just a name; you also need artwork, and you need to make sure your artwork doesn't tread on someone else's IP. I for one am glad @Matt A. Tobin is willing to do that work (and seems pretty good at it, too); it's not a field most of us have much skill at. At one time I created an icon for Moebius (I spell it with the e so I don't need an umlaut on the o); I'll attach it here. For Neptune, I'd go with the planet; plenty of public-domain Voyager images to choose from, and Neptune's trident might be too suggestive of the Devil for some folks moebius-triangle.ico
  13. Mathwiz
    Oh, wow ... so did you have to move to a newer Windows version? OK, unpacked FF 52.0.a1 into a new folder. Installed the UOC Patch for FF 45. Created a new, clean profile for it and installed the UOC Enforcer for 45. Started it. (This version defaults to e10s on.) On Darksky.net I saw some of the same symptoms as you when scrolling up: black rectangles and/or incompletely-redrawn parts of the page. (Scrolling down seemed OK.) Turned e10s off in about:config. (There seems to be a bug with the checkbox in about:preferences: it sets the wrong pref, and e10s stays on.) Much better; apparently e10s is incompatible with APZ and/or tiled compositing. But, one problem remained: I couldn't get that dark grey overlay to completely disappear. Often it would cover the whole graphic, but if I scrolled up from below slowly, it would just cover the bottom part, as in this example. As a control, everything looked fine on Serpent 55 (Moebius). Do you remember if those were the same kinds of problems you had with SSErpent 52?
  14. Mathwiz
    Aw, man ... that's too bad. It didn't take the HDD with it did it? Can you just replace the MoBo and reactivate XP instead of reinstalling everything?
  15. Mathwiz
    OK, so my test plan for tomorrow is: Download and unpack @roytam1's FF 52.0.a1 build linked above Install the UOC Patch & Enforcer for FF 45 Scroll up & down in some web pages and look for the issues seen above. Try both with e10s off and on. Any suggested Web pages to try? Is MSFN enough?
  16. Mathwiz
    The name "New Moon" was built into the Pale Moon source repo as a placeholder for anyone making an unofficial build of Pale Moon. It was always recognized as a temporary name. In the original thread, I and many others made many clever suggestions for a permanent name, but none caught on, so @roytam1 just kept using the New Moon name. I'm reluctant to restart the cacophony of suggested names again. "Whistler" may not be that inspiring, but it's not bad and fits a theme. Let's get this done at last.
  17. Mathwiz
    Adobe's online installer isn't a Trojan AFAIK; it's only problem is that it doesn't work on XP. As for Avast, I'm aware of their snooping: As I hinted in the last line, sometimes that's the price of a "free" product. So they bumped the revision up to 68.9.... No idea why @caliber wants to be version 2 though; that's pretty a old FF version.... I'm still using version 60.9 on my user agent; most sites don't seem to complain about an "outdated dinosaur browser" as long as they think you're running a post-Quantum version. Must have been changed by July 19; that version reports Basilisk/20190719 In the 20190719 build, toggling it false has no effect: you still get Basilisk/20190719. But by build 20191115, toggling it false works: you get Basilisk/52.9.0. So they must have fixed it somewhere between those two points. I doubt many sites check for a "Basilisk" UA segment, but there may be a few.
  18. Mathwiz
    It is true. The online installer downloads and launches, and on Win 7 it runs fine. But on XP this happens: The offline installers at the links @Bersaglio posts work fine on XP.
  19. Mathwiz
    Online installers for Adobe Flash no longer work on Windows XP. Use the links to the offline installers posted by @Bersaglio here:
  20. Mathwiz
    Yep - mine auto-updated and I didn't even notice until I read your post.
  21. Mathwiz
    That's hopeful news for FF 51, which is on par with SM 2.48. Of course we don't have an SSE-only build of FF 51 for you to test. But I could test it on Win 7, if I knew how! If APZ/tiled compositing work in FF 51, that would narrow the search significantly for where they got broken (must've been between FF 51 and FF 52).
  22. Mathwiz
    Thanks for the heads-up; that will surely affect my browser downloader batch file and, I suspect, @i430VX's installer.
  23. Mathwiz
    Were you able to confirm that APZ and/or tiled compositing are not broken in SM 2.48?
  24. Mathwiz
    Well, I'm home for the weekend, so I decided to try on my home system (also Win 7), but discovered that here, I already had the v1.4.9 installed that has been so elusive on my Win 7 work PC.... But I'm sure you're onto something. I noticed with interest that Serpent 52 is "lying" to the Mozilla server and claiming to be FF 60. Serpent 55 claims to be FF 55 (even though it's closer to FF 53), and as you noted, it's stuck with v1.4.8.... (I suppose the proper "lie" would cause the server to download v1.4.10 , although it wouldn't work since Basilisk and Serpent don't have the required hooks yet....) The only question is, even if you migrate a profile from another browser (a practice I'm aware you're implacably opposed to, as you first made clear when I migrated my profile from Serpent 52 to 55; but my migration from FF 52 to Serpent 52 occurred long before then), defaults don't get migrated - only user set prefs do! So if it's wrong, I must have changed it manually, either back on FF 52 or an early version of Serpent 52. But why on Earth would I have ever modified that obscure pref? So I went searching, and am rather sure I found the answer. The following is in a "spoiler" at the Adobe Primetime thread: Thanks go to @mixit for keeping those obsolete instructions for "historical" reasons! Turns out Primetime works on both FF 45 and FF 52, but neither of those versions supported it officially, so to get the server to download it, you had to "lie" and tell the server you were running the closest supported FF version! That "lie" is no longer needed or useful with Primetime, but it would have the side effect of downloading Widevine v1.4.8. So I'm sure when I get back to work Monday, I'll find that pref user set to spoof FF 51 vs. the default of 60.
  25. Mathwiz
    Yes, that color is much more readable; thanks! Actually I have v.1.3.0; at one time I tried v1.4.0 but IIRC it didn't work correctly, so I rolled back to v1.3.0 and it worked fine.
×
×
  • Create New...