Tom, I don't think what you're doing is a waste of time at all. You've been hands down the most significant contributor. I sincerely appreciate your efforts. I want to help with OXT Lite more, at least by testing and reporting and throwing my 2 cents in. I haven't had the time to do much more than that lately, and I have another busy weekend ahead so probably won't be getting much xTalk stuff going over the weekend.
I do think you should consider picking up more files from my build, particularly the Extension Manager related files because I fixed a bunch of things in there. For example if you click on the right-side menu for OXT MacNative lib item in the Libraries tab of Extension Manager there should be a Demo stack, if you select that it should open the stack but it didn't before I fixed it (and doesn't in OXT-Lite either), there's fixes in the Extension Builder stack too. Also the tabs in Extension Manager 'Snippets' and 'Sample Stacks' are empty (I removed those tabs completely since they were always empty in the before times), Extension 'Store' tab in OXT Lite sill points to a page on LC's server. OXT Heavy has an Extension 'Repo in there, which is actually a bunch of files in GitHub repo. That can be a little bit slow loading the first time loading because it downloads a copy of the 27mb Emscripten Engine from that GitHub Repo (It would be better if it could use the copy of Emscripten engine that is already in the standalones folder). The 'Store' and 'Sample Stacks' probably a good ones to change over into a regular stack instead of a web page. The 'Store' repo's 'database' is simply tab delimited data in a plain text file, that is read by the webstack that's running in that browser widget. The point is I did a bunch of work on this aspect of the IDE.
The more import thing is that crash when I click to open the 'Windows' or 'Help' menu, I don't know what is going on there.
Maybe the dmg I downloaded isn't 1.0f but some other 1.0 build? I'll have to check when I get home.
I'm not sure what it could be, unless it has something to do with sharing a prefs file with OXT Heavy or something like that?
But OXT Heavy (DPE) is still working fine on the same machine.
Apple's Disk Utility kind of sucks donke... er... now days is not particularly useful like it once was, IMO.
Newer version of APFS files system are not even compatible with older APFS drivers in earlier versions of macOS that did support APFS. What I mean is MacOS 10.14 Mohave can't recognize the partitions on drive formatted with Sonoma, HFS+ formatted still works fine on both, and I have a feeling Apple will likely have to keep support for HFS+ for a long time to come, so that's the way to go.
Here's a GUI tool for building fancy dmg files, the sort of DMG that present a splash screen (usually licensing info) when they're mounted, and can code sign them afterwards. This should be able to make 10.14 and lower compatible HFS+ disk images too.
https://www.araelium.com/dmgcanvas
All of what it does can also be done with command line tools that either come with macOS or come with Xcode Command Line Tools (someone could make a stack that is. UI for building distribution .dmgs)
I can't remember/or refind where I got that Code Signing utility app, but I know that it is using the command line tools underneath the UI to adhoc sign. I have collected a few tools for dealing with extended attributes (GateKeeper) and code signing and stripping signatures off and that sort of stuff. When Apple started really pushing it a few years back, then and I started researching. I did find a lot of useful tools and information articles about this sort of code signing and making certs and stuff from this site:
https://eclecticlight.co/mac-troubleshooting-summary.
Also this old tech note from Apple has a lot of details too:
https://developer.apple.com/library/arc ... index.html