3 ms·

If the issue is that implementations are feature lacking, that's a different story. The world is littered with half baked frameworks. Hell, I've used plenty of

If the issue is that implementations are feature lacking, that's a different story. The world is littered with half baked frameworks. Hell, I've used plenty of retained mode frameworks that lack all of those things too. My concern was moreso that there is nothing inherent to immediate mode that prevents all of those things. Someone just has to build it. RTL tends to be more of a layout problem and has little to do with UIs. Most of my experience with immediate mode UI frameworks is in proprietary applications. I will say that we had no issues with localization and we integrated well with screen readers though none of this was in a platform independent manner. And that's usually the root of all of these issues.

nox101 3y ago
I disagree that "someone just has to build it." For example, when iOS shipped it did not have spell checking, word lookup, translation, password insertion, etc built in as context menus on text. When those features were added by the OS, every app using the native widgets got those features for free with no work on their part. Apps that rolled their own though, had to re-release their app. If they don't have time or their app is abandoned then their users suffer. This is arguably one of the reasons flash was killed off. It was designed to render to a rectangle of pixels and it assumed a mouse and keyboard. Then smartphones appeared and no one was going to go back and fix millions of flash pages. Current apps doing their own thing will have the same problem with the next UI change (maybe vision Pro for example).
- xyzzy_plugh 3y ago
  Sure, I'm not arguing against using native widgets. I'm not suggesting that immediate mode necessitates eschewing all of those things or hand rolling them. There is a difference between native frameworks and cross-platform frameworks. Did Qt magically support all of those features on day 1? Xamarin doesn't completely support all of the iOS input properties, for example. This feels like a straw man.

nox101 3y ago

I disagree that "someone just has to build it." For example, when iOS shipped it did not have spell checking, word lookup, translation, password insertion, etc built in as context menus on text. When those features were added by the OS, every app using the native widgets got those features for free with no work on their part. Apps that rolled their own though, had to re-release their app. If they don't have time or their app is abandoned then their users suffer. This is arguably one of the reasons flash was killed off. It was designed to render to a rectangle of pixels and it assumed a mouse and keyboard. Then smartphones appeared and no one was going to go back and fix millions of flash pages. Current apps doing their own thing will have the same problem with the next UI change (maybe vision Pro for example).

xyzzy_plugh 3y ago
Sure, I'm not arguing against using native widgets. I'm not suggesting that immediate mode necessitates eschewing all of those things or hand rolling them. There is a difference between native frameworks and cross-platform frameworks. Did Qt magically support all of those features on day 1? Xamarin doesn't completely support all of the iOS input properties, for example. This feels like a straw man.