4 ms·

It's .NET, mentions Windows and native, yet none of the screenshots look anything like native Windows controls.

by userbinator 3y ago

jeremycarter 3y ago
I could be wrong, but it might be able to host native components or draw your own.
- francoistanguay 3y ago
  Indeed, an Uno app is a native app, it uses UIKit on iOS, Views on Android, HTML on Web, except on Linux where you only have access to our Skia renderer. Therefore you can embed native controls.
  - KacharKhan 3y ago
    "on Linux where you only have access to our Skia renderer" ... means what? Can I make a basic GUI app on Linux with Uno. If yes how ?
    - francoistanguay 3y ago
      Yes, on Linux it behaves similar to Flutter and draws directly to a Skia Canvas. It used to have a dependency on GTK but no more since the 5.2 release. There's just no notion of "native controls" that you can embed in an Uno Linux app like you could have if you wanted to embed a 3rd party native UIKit control on iOS.
pjmlp 3y ago
Uno is based on UWP, on Windows it uses the native UWP stack.
- neonsunset 3y ago
  [flagged]
  - pjmlp 3y ago
    [flagged]
    - neonsunset 3y ago
      Uno is a third-party open-source project. It is not related to UWP beyond the fact of being a .NET GUI framework. It's like complaining that a particular Yamaha bike is bad because a Yamaha digital piano of particular model is bad. Do take pills before posting, thanks.
      - pjmlp 3y ago
        [flagged]
- jlaban-uno 3y ago
  Uno Platform maintainer here - Uno is compatible with both WinAppSDK/WinUI and UWP API sets. Our default project templates have been on WinUI for two years now, UWP mainly being supported for temporary upgrade scenarios to WinUI.
- sasakrsmanovic2 3y ago
  Nope it is not.
alkonaut 3y ago
I don’t think native here refers to the control styling being similar to Win32 on Windows.
humzashahid98 3y ago
Uno wants applications to look the same across platforms (as Flutter does) but still wants to use native controls. So their approach[0] is to have default styling applied to every control which makes the native controls look the same on each device [0]. I think the main benefit with this approach is expected-behaviour (like how different desktop operating systems have different textbox behaviour), and that whatever accessibility you get by default with native controls is there. [1] I don't really find their approach to GUI development compelling though, with them choosing a middle ground between "wrapper around native controls" and "implement everything yourself". [0] Except on Linux and web, where Uno draws everything itself, imitating controls that look like GTK (on Linux) or UWP/WinUI (on web). These are the platforms I briefly tested on and I didn't have an enjoyable experience with the output due to non-native/non-expected behaviours. [1] Page on accessibility: https://platform.uno/docs/articles/features/working-with-accessibility.html https://platform.uno/docs/articles/features/working-with-acc...
- pjc50 3y ago
  That's the choice people face: "native" (different on all platforms) vs "synthetic" (looks the same but loses true native functionality).
  - sasakrsmanovic2 3y ago
    Correct - and with Uno you get to chose either one of those approaches - https://platform.uno/pixel-perfect/ https://platform.uno/pixel-perfect/
- jlaban-uno 3y ago
  Uno Maintainer here - Thanks for trying out Uno! At this time, the default render mode is provide a uniform look across platforms, and it's possible to alter the theme using Material, Fluent or Cupertino, or to design your own theme using control template styling, or even use native controls directly where applicable. On Linux, we've just released our support for X11, removing the need for GTK. As we're drawing the whole app surface, we're always interested in adjust the UX of our controls on individual platforms. If you have examples, let us know. Finally, for WebAssembly, our current rendering backend is using the HTML DOM, which means that accessibility and other native behaviors are functional. Same here, if anything accessibility related is missing, we're all ears!

It's .NET, mentions Windows and native, yet none of the screenshots look anything like native Windows controls.

jeremycarter 3y ago

I could be wrong, but it might be able to host native components or draw your own.

francoistanguay 3y ago
Indeed, an Uno app is a native app, it uses UIKit on iOS, Views on Android, HTML on Web, except on Linux where you only have access to our Skia renderer. Therefore you can embed native controls.
- KacharKhan 3y ago
  "on Linux where you only have access to our Skia renderer" ... means what? Can I make a basic GUI app on Linux with Uno. If yes how ?
  - francoistanguay 3y ago
    Yes, on Linux it behaves similar to Flutter and draws directly to a Skia Canvas. It used to have a dependency on GTK but no more since the 5.2 release. There's just no notion of "native controls" that you can embed in an Uno Linux app like you could have if you wanted to embed a 3rd party native UIKit control on iOS.

pjmlp 3y ago

Uno is based on UWP, on Windows it uses the native UWP stack.

neonsunset 3y ago
[flagged]
- pjmlp 3y ago
  [flagged]
  - neonsunset 3y ago
    Uno is a third-party open-source project. It is not related to UWP beyond the fact of being a .NET GUI framework. It's like complaining that a particular Yamaha bike is bad because a Yamaha digital piano of particular model is bad. Do take pills before posting, thanks.
    - pjmlp 3y ago
      [flagged]
jlaban-uno 3y ago
Uno Platform maintainer here - Uno is compatible with both WinAppSDK/WinUI and UWP API sets. Our default project templates have been on WinUI for two years now, UWP mainly being supported for temporary upgrade scenarios to WinUI.
sasakrsmanovic2 3y ago
Nope it is not.

alkonaut 3y ago

I don’t think native here refers to the control styling being similar to Win32 on Windows.

humzashahid98 3y ago

Uno wants applications to look the same across platforms (as Flutter does) but still wants to use native controls. So their approach[0] is to have default styling applied to every control which makes the native controls look the same on each device [0]. I think the main benefit with this approach is expected-behaviour (like how different desktop operating systems have different textbox behaviour), and that whatever accessibility you get by default with native controls is there. [1] I don't really find their approach to GUI development compelling though, with them choosing a middle ground between "wrapper around native controls" and "implement everything yourself". [0] Except on Linux and web, where Uno draws everything itself, imitating controls that look like GTK (on Linux) or UWP/WinUI (on web). These are the platforms I briefly tested on and I didn't have an enjoyable experience with the output due to non-native/non-expected behaviours. [1] Page on accessibility: https://platform.uno/docs/articles/features/working-with-accessibility.html https://platform.uno/docs/articles/features/working-with-acc...

pjc50 3y ago
That's the choice people face: "native" (different on all platforms) vs "synthetic" (looks the same but loses true native functionality).
- sasakrsmanovic2 3y ago
  Correct - and with Uno you get to chose either one of those approaches - https://platform.uno/pixel-perfect/ https://platform.uno/pixel-perfect/
jlaban-uno 3y ago
Uno Maintainer here - Thanks for trying out Uno! At this time, the default render mode is provide a uniform look across platforms, and it's possible to alter the theme using Material, Fluent or Cupertino, or to design your own theme using control template styling, or even use native controls directly where applicable. On Linux, we've just released our support for X11, removing the need for GTK. As we're drawing the whole app surface, we're always interested in adjust the UX of our controls on individual platforms. If you have examples, let us know. Finally, for WebAssembly, our current rendering backend is using the HTML DOM, which means that accessibility and other native behaviors are functional. Same here, if anything accessibility related is missing, we're all ears!