I'm starting a new app based on MXP (for mac) and UXP for windows. But I've been asked to not use the Pale moon forum for questions about the app I'm making. So i was wondering if i could ask around here instead. The app is called Noob Music and will be a replacement for iTunes since apple has stopped developing iTunes and i think apple music is very crummy. The app is far along and will hopefully be released soon but I'm having an issue with an javascript library I'm using called jsmediatags. i've posted an issue on the maintainers git describing the issue: https://github.com/aadsm/jsmediatags/issues/146 but i was thinking it couldn't hurt to ask around if anyone knows what the difference is between XHR requests done with the file:// protocol and the http:// protocol. Since the issue is that I'm trying to load the tags from audio files and for some reason large files cause a allocation size overflow when using the file:// protocol

The add a new post page will not load on my WordPress.com blog using both Waterfox Classic & White Star, the rest of the site seams to load just fine. I'd rather use White Stare to post on my blog, so my question is is there some setting or configuration that I can set or change to get the page to load or is this a problem with WordPress.com and mot something I can resolve in White Star. Thanks for your help in advance.

A little bit late, but here's Silver version 1.2.1

https://www.noob.software/downloads/silver-v1.2.1.dmg

silver source: https://github.com/siggi90/NoobSilver

platform source: https://github.com/dbsoft/UXP

So I have gotten a request from the Pale Moon team to rename the White Star platform to something besides UXP to avoid confusion.

So I never really planned for these forks, and I was thinking I would just be doing builds of White Star... UXP would be in the source distribution and that was that.  But apparently having White Star and the platform (UXP) separate on GitHub makes them worry there will be confusion.... and with the Silver builds of Basilisk that noobsoftware has done it makes me ponder on the new name I should pick for the platform.

The most simple idea is just to call it "White Star Platform" but if noobsoftware or I continue to make Silver builds that might be a bit of a misnomer.

Does anyone have any suggestions for the new name for the platform (UXP)? 

If I don't get a better suggestion by next week I'll just go with "White Star Platform" (WSP) or "DBSoft Platform" (DBSP)

Thanks!

Brian

This build is no longer available for download.
Release Notes

Enjoy!
Brian

I am going to be out of town for a few day and when I get back I'll be working on getting the next version of White Star ready, since Pale Moon should be releasing on this coming Tuesday.   But I wanted to put this idea out there after a private conversation with someone...

The original plan was to keep White Star completely aligned with Pale Moon, just continuing the Mac releases I had been doing.  However since the Pale Moon team by ripping the Mac code out of the source base immediately has forced me to fork the code base... therefore since I have to do tons of work with each release picking and choosing what commits to include which to skip... I have no reason to follow the Pale Moon teams choices completely.

With that in mind, White Star is for the former Pale Moon Mac users, what would be best for you all...

Are there any ways you want White Star to diverge from Pale Moon?

Things that have been discussed were putting the old Dual System back in allowing unmodified Firefox extensions... enabling some experimental options that Pale Moon has disabled by default. 

Please post your ideas here... and why you want/need them.  If you don't want something that someone else has suggested... please let me know and why you don't want it. 

If a consensus can't be reached I might release two versions... one that follows Pale Moon as closely as possible and an experimental version with these other options included.   

Not sure if I will be able to incorporate the changes for the Tuesday release or not, but if there is a set of changes people want I might release an update later in the month with the changes.

Brian

I got a new Mac with Big Sur.  The user-agent reported by White Star (and SeaMonkey) has the OS as version 10.16 where it is really 11.4.  Why is that?

https://www.noob.software/downloads/silv...ntel64.dmg

I've updated the default appearance of Silver (square tabs, and a more modern mac look), if someone prefers the old theme it would be cool to have that as an optional theme if anyone has experience with theme making and interest in making it. The only rules I added to the old default theme are:

.titlebar-placeholder {
display:none !important;
}

#titlebar {
height: 55px !important;
}

I don't know why but when i added the only other theme available on the Basilisk web page (the Photonic theme) to Silver it overrides these rules so I assume that these rules would be necessary in a macOS specific style somewhere for a theme.

After updating to the new theme I've notice photonic does not render correctly with the new theme because I've changed the tabs a bit, I'm not used to theme making but I'm assuming this can be fixed if Basilisk theme-makers intend to target Silver.



Please comment if you have some thoughts, dislikes or ideas for improvements.

This build is no longer available for download.
Release Notes

Turns out it didn't take as long as I was thinking, so was able to get the repository fixed up and a build done on my dinner break.

Update: Rushed it a bit since Tuesdays are my busy day, didn't notice the warning about un-preprocessed files. Please redownload it if you grabbed it in the first 6 hours.

Enjoy!
Brian

Figured I'd take a moment to post an update on the progress being made for Dynamic Windows 3.2.

3.2 is mainly going to be a platform support update... adding support for the following platforms: GTK4, Wayland (GTK3), iOS and Android.

GTK4 is mainly ready to go, the only missing piece is HTML support since webkit2gtk does not yet support GTK4. Several other features are unavailable due to their removal in GTK4, like the already deprecated MDI and taskbar support. (Wayland also has more limitations like no window positioning support) Here is a GTK4 screenshot running in Fedora Linux using Wayland instead of X11:



iOS is also very close to ready with a few caveats.  The container widget only displays the first column currently, since the UITableView only has one column on iOS.  I am debating having an optional custom UITableViewCell with the data from all the columns displayed. There is no tree control in iOS so this widget is completely unavailable. 

I am stuck on two bugs that have me completely confounded, first the calendar widget is implemented, but when I enable the code... all DWBox (UIView subclasses) in my view hierarchy get a size of 0x0.

Second context menus are implemented, but whenever one tries to display I get the following error on the debug console:

[Assert] Failed to find a presenting view controller for view (<DWContainer: 0x7fa413046200; baseClass = UITableView; frame = (6 696; 1344 200); clipsToBounds = YES; tag = 100; gestureRecognizers = <NSArray: 0x60000012c630>; layer = <CALayer: 0x600000ff55e0>; contentOffset: {0, 0}; contentSize: {1344, 176}; adjustedContentInset: {0, 0, 0, 0}; dataSource: <DWContainer: 0x7fa413046200; baseClass = UITableView; frame = (6 696; 1344 200); clipsToBounds = YES; tag = 100; gestureRecognizers = <NSArray: 0x60000012c630>; layer = <CALayer: 0x600000ff55e0>; contentOffset: {0, 0}; contentSize: {1344, 176}; adjustedContentInset: {0, 0, 0, 0}; dataSource: <DWContainer: 0x7fa413046200>>>) in window (<DWWindow: 0x7fa412604db0; baseClass = UIWindow; frame = (0 0; 1366 1024); gestureRecognizers = <NSArray: 0x6000001fde30>; layer = <UIWindowLayer: 0x600000f80e80>>). The interaction's view (or an ancestor) must have an associated view controller for presentation to work.

There is a presentation view controller on the DWWindow (UIWindow subclass) that is the toplevel ancestor, so not sure why it thinks there isn't one. 

Here is a screenshot running on an iOS 14 iPad in dark mode:



Finally Android has the furthest to go, I have the basics working right now: Buttons, Check/Radiobuttons, Entryfield, MLE, Comboboxes, Listboxes, Notebook, and HTML are functional.

Still left to go: Container and Font.

Boxes are implemented with LinearLayout which has a weight option for expanding like my system, but it isn't divided up into horizontal and vertical.

Here is a screenshot of Android with its (slightly) incorrect layout:



Update: May 11, got much more working... almost everything except containers and fonts... and presumably a lot of bugs.

I had been using Xamarin and C# for doing mobile development, but hopefully in the next few months I can completely move over to using my own library for cross platform development on Mobile as well as desktop! 

Brian