Another alternative of course is to use some other client-server protocol such that only the “model” of MVC is on the server, and UI rendering instructions are sent across the network instead of actual rendered graphics. For example load QML over the network and run it locally. For some reason we aren’t putting much emphasis on that as a primary use case yet, but I wonder if anybody in the field is doing much of that?
It's called "The Web" and there are many reasons to hate it. However, one thing the relevant people in the field got somewhat right (IMO) is the level of coupling between the "model" and the rest of the application. _______________________________________________ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
