211–220 of 276 posts
This is interesting for sure. Kudos for bringing this capability to the web! One issue the demos reveal is, it doesn't _feel_ like the web. That is, I can't hit Ctrl+F to find text on a page. I can't select text with my cursor. I can't copy the address of a hyperlink. On my phone, I can't hard press on an image and share it to others. Screen readers can't handle it. I can't press a shortcut key to make everything lar…
Earlier quoted context omitted.
The answer to that is well known: Windows division builds WinUI/Win32 as their native C++/COM API, Office division went to React on their path to the web and the dev division fills gaps (WPF) and provides tools for external and internal devs (Maui for cross platform uis). It is history not the lack of will. At one point the windows division was in shambles (remember vista) and WPF pops up. At another point, the windo…
This feels a lot like the Linux desktop ecosystem where many apps have a different look and feel (GTK, Qt and a bunch of others).
I would have much preferred a React-Native-style approach, where they render to true HTML instead. Even then, WASM files are too heavy for quick loading times without good internet (and sometimes even with).
The projects I see that would most benefit from something like this are complex internal apps that need to be used in different places but aren't worth porting over/rewriting, but they would also suffer from terrible UX given the constraints of this design.
For all other projects, it makes for more sense to use React Native.
Earlier quoted context omitted.
That's not pedantic at all! Indeed, without these capabilities, it is by some definition not the real web. This hits into that concept of what exactly the "web" is. Is it just a media transport system? Or is it something more than that. Of course, we could cite Tim Berners-Lee here or Roy Fielding in this discussion. But at minimum, I think a lot of us are tired of the app-lification of the web and somewhat wish we c…
It's also an interesting question, why, in traditional rich desktop applications, I can't say I have ever missed the ability to select and copy text from the UI chrome - whereas on the web I'd definitly miss it and in badly designed mobile apps, I often do. I think some part of UI design degraded with the web, where there used to be a clearer distinction between "user data" and "app chrome" areas than there is today.…
Good heavens. I boggled at this.
It's not every single day, but probably at least once a week I am frustrated by this, and have been since the rise of PC GUIs -- so, coming up on 35 years now. It was often doable on DOS-era PCs, especially if you had a mouse, or a multitasking environment like DESQview, or best of all, both.
Earlier quoted context omitted.
Not using the standard web stuff usually means it's also an accessibility nightmare, tried using a screen reader on the demo and it doesn't work at all unfortunately
I'd just like the PgUp, PgDn, and arrow keys to reliably scroll a web page.
I want every app and every web page to be 100% navigable if I do not have a pointing device attached to my computer.
And I want this enforced by law, by large rich countries. Accessibility to people with disabilities would be a good way: if your product or service is not accessible to people who can't see, can't use a mouse, or can't use their hands at all, then you can't sell it.
In case anyone is confused > Using .NET MAUI, you can develop apps that can run on Android, iOS, macOS, and Windows from a single shared code-base. This new development adds Linux and Browser to that list. I recently tried out .NET MAUI to see how easy it was to build a hello world app. It was quite messy getting it setup on Mac but eventually I got a simple hello world app working. Nice to use XAML again after all t…
Earlier quoted context omitted.
The answer to that is well known: Windows division builds WinUI/Win32 as their native C++/COM API, Office division went to React on their path to the web and the dev division fills gaps (WPF) and provides tools for external and internal devs (Maui for cross platform uis). It is history not the lack of will. At one point the windows division was in shambles (remember vista) and WPF pops up. At another point, the windo…
Well summarized, and just as shocking today as it was every minute while it developed. Someone needs to remind those cats that they own the platform. Being able to sanely develop apps for and on that platform should be possible, and UI kinda-sorta matters for that. At a certain point with the MFC they had it dialled in, while pioneering asynchronous browser tech, with many best in class tools. Decades later with a cr…
These kind of announcements always suffer from 'creator knowledge bias' and never define their terms ;-) "What is the Avalonia MAUI Backend? At its core, the Avalonia MAUI Backend enables you to keep your MAUI codebase while replacing the rendering layer with Avalonia." Which tells me exactly nothing. what even is MAUI, maybe some polynesian deity? :-P I know, I know, I can google stuff. But still...
It's a nice idea, but the execution is taking the wrong path in my opinion. By rendering everything to a ` ` they're sacrificing any hope of accessibility and compatibility with browser standards for UX. I would have much preferred a React-Native-style approach, where they render to true HTML instead. Even then, WASM files are too heavy for quick loading times without good internet (and sometimes even with). The proj…
Would you complain that Qwasm/Dwasm doesn't follow HTML standards of accessibility?