schmurtz wrote: > I'm not a big fan of Windows Store too. Most of my Windows PC doesn't > have online account connected so I've always use your drive to get > versions ;) > May be create a simple archive could be faster than create a full setup > package ? (just tried to get it from the store and it fails 3 times > before accepting to download : I don't like the store and it don't like > me too :D ) After the installation it require webview2 runtime which is > probably included directly in the standalone setup. > But I can understand your point of view about limited time ;)
OK, since that actually made me laugh, I just finished a traditional installer and put it all back into my automated build chain. The important thing to know about the WebView2 Evergreen runtime is that I do not have to include it in my app/installer. Webview2 is managed and updated automatically by the operating system as a true operating system component. Why this is important is because now I don't have to worry about keeping it updated. There are rules about having CEF embedded in an app on the store. It cannot be allowed to be more than two versions out of date before you run afoul of the security/compliance rules. Now with Webview, I can die, and SLX can remain compliant without me, haha, even if it never gets updated again. SLX does install a very small bootstrap WebView2 Evergreen installer, which it will call to install/update Webview2, if needed (but not likely as time goes on), and to save you the trouble. I no longer have to include that 200MB of CEF binaries in my installers. And that speeds up the verification process that is part of publishing and speeds up updates because the package is much, much smaller. One reason I prefer folks use the store is that I get a better idea of how many folks are installing and using the app. The Store tells me the count of people that have acquired it, almost 20,000. Most people do not allow the Store to collect any other metrics, but some do and it is occasionally useful to see if the application is crashing. I do occasionally see a flash of crashes, which I will see when I publish a new version because if the Store updates the app while it happens to be running, it will mercilessly terminate the running app and call it a crash. A time or two, I have seen statistics that told me I had an issue, but not recently. When I publish, if the changes concern installation or if they happen to be impact Windows 10 "Tablet Mode" or Windows 10 S-Mode, then I have to publish through the Store only to myself as that is the only way to get SLX on my Surface Go (it runs ins S-Mode (Store apps only) and usually in Tablet mode, too) to test the new version. Then if all is OK, I can publish globally. So sometimes you will see the increment number skipped because an only-me test version that I had to run through the store had a bug). I have a new version published only to me waiting for me when I get home tonight to test on the Surface Go relating to Full Screen mode. It will now hide the titlebar in Full Screen Mode for Material Skin and "Now Playing" view, but I just have to make sure all works on the Surface Go and in Tablet Mode (I screwed that up on the first attempt yesterday). Tablet mode is weird and sometimes difficult to handle. I had to write a C++ Universal Windows Platform (UWP) dll, just to create a function I could call to determine if the O/S was in tablet mode because that is the only way you can do it, only doable from a C++ assembly. Anyway, Microsoft has removed it in Windows 11, and I kinda liked it for using the Surface as a tablet. It made the start menu full screen and automatically would hide the task bar if you wanted, and would hide titlebars depending on the app. Anyway, I found it useful overall, but a problem for certain programs. But Tablet Mode is gone for Win 11 which motivated me to work on a real Full Screen mode for SLX. (its for me and my tablet, haha). Wow, I started rambling, sorry. Anyway, traditional installer is returning, even though I didn't want to bother with it, I guess it was not as big a deal or as hard as I thought. I just needed the installer to get rid of the old CEF binaries and cache files and Webview2 checking and update/install needed to handled outside the installer mostly anyway. I guess I pretty much implemented everything I needed a few weeks ago, but never tested, (and forgot I had done it). So, I just needed to test it an, thankfully, it worked fine. Building the installers is about 10 times faster now, since I am not dealing with 200MB of CEF binaries, too. R Greg Dawson Squeezelite-X ------------------------------------------------------------------------ rgdawson's Profile: http://forums.slimdevices.com/member.php?userid=65236 View this thread: http://forums.slimdevices.com/showthread.php?t=108550 _______________________________________________ plugins mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/plugins
