starting a new road when traffic is sufficiently high
>> that I used them to easily do exactly the same sorts of things you claim that SCGUI is required to do.......Change is only good when there is a need. <<
I never said "required".
Anyhow, the crux of the problem comes down to:
1. Is the need for remote GUI's common
2. Are existing tools/protocols sufficient to address #1
If a need is not common, then a "good enough" solution is often sufficient. However, IMO #1 is high. Thus, the industry needs something *dedidated* to that task.
Nobody here seems to want to claim that JS+DOM is near an OPTIMUM remote GUI solution. Thus, there seems to be an implicit admission that JS+DOM is not the ideal for remote GUI's. Our difference seems to hover around #1, the frequency of need.
In a good many B-to-B and intranet projects I dealt with, management keeps wanting the browser to be "regular" GUI. The arrow just keeps pointing back that way. They want data grids, dialog boxes, pop-up error messages, menu bars, etc. The need is plenty high enough to warrent protocols dedicated to that task.
