As we all frustratingly know there's no GUI being developed for Ren-c, which is the only actively developed branch of Rebol3. Atronix do have a GUI build on their website, but it's an old build which lacks many of the changes that exist in the current builds. We did discuss this before but that ended with the view that r3/view was imminent. Unfortunately it seems Atronix don't have the time to prioritize the move to Ren-c.
So, I was thinking how one could usefully build something with what we have, and I thought back to my GUI demo. So, I am thinking that there's a common set of functions which each client knows about. It could be a script present on the local file, or it could be embedded in the server. Each client then polls the server for a task. The server marks off each task as it is collected by a client so that another client can't take that task. A callback to update the GUI is attached to that task. The client then posts the results back to the server which marks the task as completed, executes the callback with the resulting data, and then removes the task. So, this would be totally asynchronous as the hard lifting is done by the clients of the GUI based server.
This means that the GUI could be Rebol2, R3/View or even Red when it gets TCP working. But how much more work would this create? Is it a feasible way of creating an application?