Steam installeren
inloggen
|
taal
简体中文 (Chinees, vereenvoudigd)
繁體中文 (Chinees, traditioneel)
日本語 (Japans)
한국어 (Koreaans)
ไทย (Thai)
Български (Bulgaars)
Čeština (Tsjechisch)
Dansk (Deens)
Deutsch (Duits)
English (Engels)
Español-España (Spaans - Spanje)
Español - Latinoamérica (Spaans - Latijns-Amerika)
Ελληνικά (Grieks)
Français (Frans)
Italiano (Italiaans)
Bahasa Indonesia (Indonesisch)
Magyar (Hongaars)
Norsk (Noors)
Polski (Pools)
Português (Portugees - Portugal)
Português - Brasil (Braziliaans-Portugees)
Română (Roemeens)
Русский (Russisch)
Suomi (Fins)
Svenska (Zweeds)
Türkçe (Turks)
Tiếng Việt (Vietnamees)
Українська (Oekraïens)
Een vertaalprobleem melden
I've not kept entirely up-to-date on Microsoft's proprietary UI stuff, but I'm fairly sure that if you build an app targeting WinUI using XAML, there's no way to port that to other platforms, which makes it a total non-starter.
Discord is also a web app. I don't know about Epic Games Store.
Every software which is loading stuff from the Net in their client is a Web app......most stores which have a native client/App just differentiate in the UI of it, and load just their Website (maybe in Mobile Mode) into the frame.
Would be the same as if you made a website which is just a menu and load other sites in an iframe/container
If you have display issues with the app, it is most likely something on your end.
Black bars and boxes etc. is a common issue.
It's just what happens when enough abstraction layers are piled together with a web framework running on top of chrome with odd bits of gl-accel and an app built partially well and partially with duct tape (they have multiple dev departments after all)
I mean, there's a longer explanation I'm sure, but that's basically it.
using XAML instead[/quote]
That's microsoft stuff, tldr it's usually not a good fit to actually get good stuff, especially if it's going to run on Linux, Mac, windows and even to an extent android/ios (the mobile apps clearly borrow some code from the base).
The best in class I've seen so far that works well, performs well, that runs on multiple platforms and is mature, well proven and stable, is Qt. It also inherently supports web views, so it could be used for a rewrite while retaining the web-based stuff and gradually phasing the latter out where it isn't needed.
Or one could keep it simple and accept that it's all web based anyway, and code the whole thing as a webpage from the get-go (they didn't), just use HTML5/CSS for the layout and run the whole thing in a browser. Kinda like exactly what they're doing, but without CEF as an intermediary (which is apparently pretty awful).
buuuut that's a full rewrite to get it done properly, I don't think they want to because "it kinda works and people put up with it because their games are here".
Heck, half the reason they ended win7 support was apparently because CEF support for that platform was ending, goes to show how tied in they are.
what wrong with building different native app on etch platforms? being ultra lazy ?
also avalnoia UI , and uno UI there
discord is msg app no one care if it was unstable because i can use any browser meanwhile if steam crash your game experience will be trash
valve aren't smarter epic is just stupid to throw all that money
no, its one-code one-thing one button to all platforms is "lazy" and garbage all time.
xaml isn't for MS ,its open soursce and you can fork it if they don't like it, id rather take QT than we current have , being unstable app and garbage is big no.
you know even right click to select the correct word isnt working with keyboard only just mouse
didn't steam drop mac support?
If the issue is so common then a lot more users would be affected by it, and that for sure would give a lot more "spam" in here then the "Mimimi Win 7 is not supported anymore" topics.
I personally would guess that a lot of people on older hardware (or a extremly misconfigured OS) have that issue.....
It costs money.
Not all frameworks support the same feature sets, and if that happens it could be that the app/software on one system might lack features which the other system has.
It is easier to maintain if the code is the same on all systems (like for bug hunting).
But i guess you would be smart enough to know that stuff yourself.
so they have billions if users not millions users and 3-4 app per platforms is "expensive" where the 30% cut go.
i dont care about crazy future i want an app that can run games ,msging the frind and enough which is just bad with current steam all is i got black and white thing every one hour.
that is the app offer hard thing like Photoshop which not the case with steam like
it's excuses ,now we got nitflex web-app gl with pc experience
hope something will replace it soon but seems wont be happend
It's also just not a good use of time. Consider what's preferable: building the UI for one feature three times, or building the UI for three features one time.
For one thing, they're all based on .net, and Steam is a C++ application, not a .net application.
The other thing is that what I said in my first comment still applies. Using something like Avalonia (presumably named after the original codename for WPF, which was "Avalon") is defining a UI in a text-based markup language (XAML), and using a third-party framework (Avalonia) to render it. It's really not that different from defining a UI in a text-based markup language (HTML) and getting third-party framework (CEF) to render it.
Steam's UI is all done by a separate process, the Steam Web Helper processes. Games only need steam.exe to not crash to not have problems. If the UI crashes, it'll just bring down the Steam Web Helper processes and they can gracefully restart.