From mboxrd@z Thu Jan  1 00:00:00 1970
From: erik quanstrom <quanstro@labs.coraid.com>
Date: Fri, 19 Feb 2010 16:58:50 -0500
To: weigelt@metux.de, 9fans@9fans.net
Message-ID: <48ff49f6665b00f0d9ef428a3017f681@coraid.com>
In-Reply-To: <20100219213613.GB491@nibiru.local>
References: <20100218163513.GA491@nibiru.local>
	<4B7DAE24.30008@orcasystems.com>
	<20100219213613.GB491@nibiru.local>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Subject: Re: [9fans] Vector graphics device
Topicbox-Message-UUID: d7216712-ead5-11e9-9d60-3106f5b1d025

> In this model the client doesnt actually draw an image, but just
> operates on an (changeable) vector graphic. Things like scaling,
> resizing (even funny effects like deformed windows while moving)
> all are done by the display server - the client just sees object
> vectors in an continous 2D space.

that model expired in the 60s.

if you want to support scaling, you'll likely need to support something
more complicated than vectors.  (vectors scale trivially.)

once you branch beyond vectors, life gets a bit complicated.
and generally one jumps immediately to 3d.

doing it this way seems like the hard way.  why not just redraw
the display at the given resolution?

- erik