Hi, On Thu, Apr 21, 2011 at 09:15:24PM +0200, Enrico Weigelt wrote: > * Sam Spilsbury <[email protected]> schrieb: > > since the majority of clients will do all the surface painting Client-side > > (cairo, Qt) or direct to the hardware (OpenGL). > > That's the main problem, IMHO. It leads to really a lot of unnecessary > code and data duplication. (btw: I'm glad to have all my systems free > of the Qt bloat ;-o). > > Alternative: let the clients just _describe_ their window contents > as vector graphics, that only get manipulated when needed (and NOT > repainted over and over by the client itself!). Most of the common > widget toolkit's code (and runtime data) would be simply obsolete > this way.
Which leads to massive and unpredictable latency since you've now thrown a full vector rasteriser into your display server, so any window management, cursor movement, etc, operations will be blocked behind rendering which may run for an unbounded amount of time. IOW, exactly what Wayland was (quite rightly) designed to avoid. Cheers, Daniel
signature.asc
Description: Digital signature
_______________________________________________ wayland-devel mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/wayland-devel
