Replies: 1 comment
-
#StoryCAD booting and editing stories Auto/Releasebuilder would require updating to build UNO projects Replace System.Drawing in NRTF Remove WinUIEx and CommunityToolkit.WinUI.UI.Controls.Core Replace MySQL Package with MySqlConnector Some classes require partial adding to them Printing implementation needs be changed/modified Single Instancing needs to be changed/removed File/Folder Openeing needs to be tweaked Tweaks in App.xaml.cs to work with Uno Manifest Resources must be placed at the root of a project instead of in a folder, Im reporting this to the UNO Team. Per platform incompatabilities Certain future projects might have issues porting to uno |
Beta Was this translation helpful? Give feedback.
-
In order to attract as wide a user base as possible, StoryBuilder must run on as many devices as possible. Currently, WinUI 3 only works on Windows Platforms.
According to Wikipedia, for desktop and laptop computers, Windows is the most used at 75%, followed by Apple's [macOS] at 16%, and Linux-based operating systems, including Google's Chrome OS, at 5% (thereof " desktop Linux " at 2.35%). With tablets, Apple's iOS has 55% and Android has 45%.
One way StoryCAD can run on more devices is to port the app to UNO.
Another would be through MAUI.
And yet another option is to consider Qt#.
This discussion started as issue #269.
See also:
https://platform.uno/docs/articles/uwp-vs-winui3.html?msclkid=f43a1190b58311ecb66a53d1aff6eb21
Beta Was this translation helpful? Give feedback.
All reactions