Anyway; being lazy; so this is kind of a GUI layer on top of HTML/CSS?
Anyway; being lazy; so this is kind of a GUI layer on top of HTML/CSS?
Chrome UI on Windows, ChromeOS and soon Linux are comprised of a few layers:
Views (widget toolkit abstraction) - tabs, buttons, textfields, etc. Aura (window/"native widget" abstraction, event dispatching, what most code at layers above would consider to be the XWindow, except the XWindow is abstracted (and there is only one XWindow per top level browser window)) CC - (Chrome Compositor, also used for web content.)
They're all in native code since being able to drop down to the metal (& grab the app's toplevel XWindow) is often useful when building a desktop UI. HTML/JS/CSS binding to CC is limited to Blink.
If the browsers used something like XAML, with proper support for components, it would be great.
Maybe web components will eventually get us there, but it is surely a very bumpy road to get to something that only now starts to resemble Smalltalk/Lisp environments.
Aye, that would be so nice!