Any new development updates?
Posted: 2022-09-19, 16:18
Was just wondering if there was any since the old thread got locked.
Discussion forum for the Pale Moon web browser
https://forum.palemoon.org/
*cracks whip*athenian200 wrote: ↑2022-09-20, 02:23I am kind of bad about staying on top of things unless I have someone reminding me I need to be doing stuff.
A forum I used to frequent had one subforum for an entire generation of vehicle model. I organized it with a giant sticky thread that acted as a table of contents. It worked very well.athenian200 wrote: ↑2022-09-20, 02:23Also kind of trying to decide how I want to organize all this now that I have a subforum. Like maybe I should have one thread for releases, etc.
I mean, in theory all the hooks in the codebase should be in there to do that. The problem is that I don't really have the knowledge and skill needed to deal with making that happen, I probably need to ask others for help, and I'm kind of introverted and don't like being a burden on others. So it's like, when I'm dealing with stuff I know how to do, I try to get it knocked out as fast as possible... but when I'm in a situation where I'm out of my element, my natural inclination is to put off dealing with that situation as long as possible. And the majority of what this project has involved after I got it to compile against UXP has been almost all the kind of thing I am not very comfortable dealing with. I do think it will get a bit easier after I have the initial setup done, though.back2themoon wrote: ↑2022-09-20, 10:36I guess it's still a bit far from a 'stable', auto-updating release?
Looks like a lot of people want it (count me in but haven't tried yet), Moonchild included, There may be one or another who might want to help with automatic updates, for selfish reason One thought about this, if it requires a dedicated website, would github be suitable? You'd give all the code to M$ as a present but since it's open source and publicly available, they may already have it if they are interested.athenian200 wrote: ↑2022-09-20, 19:15I mean, in theory all the hooks in the codebase should be in there to do that. The problem is that I don't really have the knowledge and skill needed to deal with making that happen, I probably need to ask others for help, and I'm kind of introverted and don't like being a burden on others.
Oh my that sounds so familiar *looks @ mirror* At least I'm not aloneathenian200 wrote: ↑2022-09-20, 19:15... but when I'm in a situation where I'm out of my element, my natural inclination is to put off dealing with that situation as long as possible.
I understand your line of thought buuut since a bunch of people are interested, everybody who's helping does a Good Thing (say, in terms of karma), so yeahathenian200 wrote: ↑2022-09-20, 19:15and on top of it I would have to ask others to put effort into making it happen, which makes me doubly uncomfortable.
athenian200 wrote: ↑2022-09-20, 19:15It doesn't take much to snap me out of that, like even just this thread being created and people asking questions is enough to get me to try and make something happen. Looking at it more closely, I'm thinking I might be able to make a release soon, it's really just a matter of making sure everything is lined up.
I'd be glad to help out with the auto-update server if you need. I had to configure one for Basilisk when I took ownership of that project so I am familiar with both configuring the auto update server and the code for it.athenian200 wrote: ↑2022-09-20, 19:15I mean, in theory all the hooks in the codebase should be in there to do that. The problem is that I don't really have the knowledge and skill needed to deal with making that happen, I probably need to ask others for help, and I'm kind of introverted and don't like being a burden on others. So it's like, when I'm dealing with stuff I know how to do, I try to get it knocked out as fast as possible... but when I'm in a situation where I'm out of my element, my natural inclination is to put off dealing with that situation as long as possible. And the majority of what this project has involved after I got it to compile against UXP has been almost all the kind of thing I am not very comfortable dealing with. I do think it will get a bit easier after I have the initial setup done, though.back2themoon wrote: ↑2022-09-20, 10:36I guess it's still a bit far from a 'stable', auto-updating release?
Yeah, I have a place to host one now, the main thing I'm getting stuck on is really the code for it. Like, I did figure out a way I could just inject an XML file directly into the build system and force it to update, using app.update.url.override, but as far as understanding how the "normal" url works and all of that, I am at a loss.Basilisk-Dev wrote: ↑2022-09-25, 14:31I'd be glad to help out with the auto-update server if you need. I had to configure one for Basilisk when I took ownership of that project so I am familiar with both configuring the auto update server and the code for it.
The short summary is that the application (Pale Moon/Basilisk/Epyrus/etc) sends a request to the AUS with params containing information about the application. These params will be things like the application name, the OS, the CPU architecture, etc.athenian200 wrote: ↑2022-09-25, 21:33Yeah, I have a place to host one now, the main thing I'm getting stuck on is really the code for it. Like, I did figure out a way I could just inject an XML file directly into the build system and force it to update, using app.update.url.override, but as far as understanding how the "normal" url works and all of that, I am at a loss.
That's actually very close to what I was planning to do, create some kind of directory structure that includes major version and OS in it and make sure the builds I put out all point to the right ones for their version and OS. For instance something like <URL>/1/win32/update.xml would be for the 1.x series and win32, but then something like <URL>/2/linux/update.xml would be for the 2.x series and Linux. That would basically mean if someone was on an older major version, I could leave an update file pointing to whatever version that older version should update to, before updating to a later version.
Oh nonono that's not needed at all.athenian200 wrote: ↑2022-09-26, 16:33The only difference was, I would have thought I had to hardcode this, manually change all the version numbers with every major release, and rely on ifdefs to determine what it should be for each OS.
Code: Select all
https://aus.palemoon.org/?application=%PRODUCT%&version=%VERSION%&arch=%BUILD_TARGET%&flavor=%BUILD_SPECIAL%&toolkit=%WIDGET_TOOLKIT%&buildid=%BUILD_ID%&channel=%CHANNEL%
well that's what we moved to to make things as minimal-effort as possible when updating. uploading a json with meta-data (conveniently generated by the build system.... ) and a .mar will prompt the php script living at https://aus.palemoon.org/index.php to generate the XML and serve it back to the requesting client. It's then also written out as a manifest once generated to save on processing.athenian200 wrote: ↑2022-09-26, 22:28It's just that there's really not an XML file, it's generating it "on the fly" somehow.
Hey athenian200, any updates on whether FranklinDM's Moonscape is still being ported to Epyrus 2.0? Thank you.athenian200 wrote: ↑2022-09-20, 02:23Well, the good news is, progress on the theme seems to be picking up again.
https://repo.palemoon.org/FranklinDM/ep ... evelopment
Also, there is an add-ons site.
https://addons.epyrus.org/extensions/
I was thinking I would wait until the theme was done and I figure out a better way to deal with updates before announcing a new release, but the reality is that... I am kind of bad about staying on top of things unless I have someone reminding me I need to be doing stuff.
Also kind of trying to decide how I want to organize all this now that I have a subforum. Like maybe I should have one thread for releases, etc.
What's the problem? As I've written elsewhere in this forum, I've been using it as my one-and-only email client for 2-3 weeks.