Support for Uno Platform
Opened this issue · 7 comments
It would be awesome if Uno Platform was also supported
Hi Martin! Thanks for stopping by!😄
As I posted the other day, at least it seems to work on WinUI and WASM.
uno-winappsdk-winui3localizer.mp4
Now, for the other platforms I guess I'll need to pick your brain. The location of the "Strings" folder, to be specific.
It could be anywhere as long as the app can access it by a given path when initialized. For example:
| App Type | "Strings" Folder Location Example |
|---|---|
| WinUI (Packaged) | ApplicationData.Current.LocalFolder |
| WinUI (Unpackaged) | Aside the *.exe file |
Where would it be for the other platforms?
Technically you should be able to use ApplicationData.Current.LocalFolder in all targets, that location is accessible (even via classic System.IO APIs) across all targets
Then, "Technically", it should work out of the box! 😀
I'll try to confirm it (in a couple of days).
It does work out of the box for WASDK but not for the other platforms. 😅
I'll take a look other lib (Live Charts maybe?) that supports Uno. Please let me know if you have any recommendation.🙂
@AndrewKeepCoding you will probably need to add multi-targeting (e.g. multiple target frameworks) - or you can create the library based on the Uno Platform Library project template.
I meed to create separate projects and packages, right?
AttachedProperty setter is not called in XAML when named Uid.
This happens on:
- Android
- WASM
- Desktop
- MacOS
It works as expected:
- on WASDK
- when the
AttachedPropertyhas other name - when the setter is called on C# code