| At some point, this would be come close to the AppleScript protocol or Symbian OS. > So the drawing part of an application would just be a process that sends the screen/compositor process a message describing the state of its window as a tree, and receives messages for events in response. I've been toying with an interpretation of this here - https://github.com/Imaginea/inai - and kind of having fun with it .. and even built a prototype internal app using it. Super early stage and so stuff won't necessarily make sense at the outset .. or possibly ever. Thoughts welcome though. > A big advantage is it makes the semantics of composing GUIs a lot more reasonable "replace this leaf of my tree with this other process' tree" ... The "dom" service in Inai pretty much feels like that. I felt like an idiot to try and (for lack of a better expression) REST-ify the DOM, but it seemed to work to my surprise. > An application could also "proxy" for a widget, including over a network link, so you get fairly simple network transparency this way too. .. yeah due to the "REST" nature, this becomes pretty straightforward. |
The Amiga had an interesting scripting model with ARexx and the ARexx port.