[Pre-release] LavaMoon Blue

[Halvar]

I would like to share a Pale Moon theme port currently in development: LavaMoon Blue.

This theme is based on the original LavaFox V2 Blue theme by Zigboom, adapted for modern Pale Moon and gradually cleaned up and adjusted for current builds and platform differences.

At this stage it should be considered a pre-release build, not a final release. The goal is to preserve the original look as much as possible while making the theme usable and stable in modern Pale Moon.

Source code:
https://github.com/Halvar666/lavamoon-blue

Download:
https://github.com/Halvar666/lavamoon-blue/releases

[Goodydino]

I cannot help bu† wonder: what is so great about text in poor contrast with its background so that it is hard to read?

[frostknight]

I would like to share a Pale Moon theme port currently in development: LavaMoon Blue.

This theme is based on the original LavaFox V2 Blue theme by Zigboom, adapted for modern Pale Moon and gradually cleaned up and adjusted for current builds and platform differences.

At this stage it should be considered a pre-release build, not a final release. The goal is to preserve the original look as much as possible while making the theme usable and stable in modern Pale Moon.

Source code:
https://github.com/Halvar666/lavamoon-blue

Download:
https://github.com/Halvar666/lavamoon-blue/releases

Would it be possible to make a variant of the red one that instead of being black was a medium gray. (not too dark not too light?

[Halvar]

Would it be possible to make a variant of the red one that instead of being black was a medium gray. (not too dark not too light?

Hi, I’ve already released a red version of the theme as well, but at the moment I’m not planning to change the colors compared to the original pre-Australis Firefox-era design. Maybe sometime in the future. Right now I need to finish the adjustments for Pale Moon, and we’ll see later.

[Halvar]

Hi everyone, sorry about this, but unfortunately I relied only on the information from the archived AMO page regarding the license. It turned out that the actual license does not allow the original theme to be forked.

The repository has been closed.

[frostknight]

Hi everyone, sorry about this, but unfortunately I relied only on the information from the archived AMO page regarding the license. It turned out that the actual license does not allow the original theme to be forked.

The repository has been closed.

That's a shame

[Halvar]

In the near future, I’ll try to convince the still-active author of the original LavaFox theme to allow a fork.

If that doesn’t work out, I’ll try to create a completely new theme for Pale Moon with a similar look.

[Halvar]

Good news.

Zigboom, the author of the original LavaFox V2 and LavaFox V2 - Blue themes, has kindly given me permission to continue development of Pale Moon fork/adaptations based on these themes.

The LavaMoon Blue repository is now open again.

The LavaMoon Red repository will be opened tomorrow after the necessary license and metadata updates are completed.

[Night Wing]

Good news.

Zigboom, the author of the original LavaFox V2 and LavaFox V2 - Blue themes, has kindly given me permission to continue development of Pale Moon fork/adaptations based on these themes.

Thanks for "going that extra mile" by taking the time and effort into contacting the author of these two themes and with him/her giving you permission to continue development for these two fork/adaptions for Pale Moon.

[frostknight]

Good news.

Zigboom, the author of the original LavaFox V2 and LavaFox V2 - Blue themes, has kindly given me permission to continue development of Pale Moon fork/adaptations based on these themes.

The LavaMoon Blue repository is now open again.

The LavaMoon Red repository will be opened tomorrow after the necessary license and metadata updates are completed.

What license will they be under?

And will you do a gray version?

[Lootyhoof]

Good news.

Zigboom, the author of the original LavaFox V2 and LavaFox V2 - Blue themes, has kindly given me permission to continue development of Pale Moon fork/adaptations based on these themes.

The LavaMoon Blue repository is now open again.

The LavaMoon Red repository will be opened tomorrow after the necessary license and metadata updates are completed.

Well done! Great to hear they're happy for you to continue.

Looking forward to seeing more on this!

[moonbat]

Btw, I've added your theme Aeon Moon as an external theme on the addons site since you've marked it as a release. If you manage to fix your other themes I can add them as well

[Halvar]

Update: LavaMoon Blue 2.2.0

This is the first stable Pale Moon release of LavaMoon Blue, based on the original LavaFox / LavaFox Blue 2.1.1 theme by Zigboom and published with the original author's permission.

Main changes since the previous pre-release work:

- fixed Permissions Manager geometry
- restored the missing Show Notifications icon
- matched the Preferences window geometry more closely to the default theme
- updated the Add-ons Manager layout while keeping the LavaMoon visual style
- cleaned up leftover internal development artifacts
- kept the original license terms and added the Pale Moon fork/adaptation permission notice

This release continues the original LavaFox / LavaFox Blue 2.1.1 line as LavaMoon Blue 2.2.0 for Pale Moon.

[Halvar]

Btw, I've added your theme Aeon Moon as an external theme on the addons site since you've marked it as a release. If you manage to fix your other themes I can add them as well

Thank you, Moonbat.

[Lootyhoof]

Off-topic:

Btw, I've added your theme Aeon Moon as an external theme on the addons site since you've marked it as a release. If you manage to fix your other themes I can add them as well

Why are you just adding externals? A qualifier for that should be that it needs its own update mechanism (i.e. update.rdf).

I've no particular allegiance either way, but in lieu of that, the add-ons site direct would be the best way. The themes as they are I'd say are of sufficient quality for publishing there.

[moonbat]

the add-ons site direct would be the best way.

How does that work? All I see in the control panel is a place to enter the link of the external site:

Screenshot_20260605_090219.png

[jobbautista9]

I think what Lootyhoof is trying to say is that you should let the theme developer submit the add-on themselves, and if they don't wish to but still want to get listed in the APMO, then an update.rdf should be setup in the XPI itself befote getting listed as an external.

[moonbat]

You mean an updateURL property. Update.rdf seems to be the file residing on the server that is queried for updates according to this.

[Lootyhoof]

Yes, I mean exactly that. Both are required to make that work. But either way, an external listing should be required to have an update mechanism in place, otherwise the developer should upload the add-on to the site where we obviously have infrastructure for that already.

This is true of both extensions and themes.

[moonbat]

So @Halvar - up to you how to proceed. If you upload the extension directly on the addons site, you'll have to manually publish updates it here in addition to Github. Else if you can host the update.rdf on Github and add an updateURL pointing to it in the install manifest, that works too. Either way it's important for users to be able to have their extensions/themes auto update if they want.