Re: GTK+ scene graph
- From: Emmanuele Bassi <ebassi gmail com>
- To: Sébastien Wilmet <swilmet gnome org>
- Cc: GTK Devel List <gtk-devel-list gnome org>
- Subject: Re: GTK+ scene graph
- Date: Sun, 3 Aug 2014 12:57:39 +0100
hi;
On 3 August 2014 11:08, Sébastien Wilmet <swilmet gnome org> wrote:
Thanks for the explanation.
On Sun, 2014-08-03 at 01:13 +0100, Emmanuele Bassi wrote:
<snip>
yes, it was considered, and no: "depth" (or similar terms) won't be used.
people using a canvas with 3D transformations intuitively grasp the
concept of a Z axis, as well as that of a coordinate on that axis.
they understand rotations around that axis, as well as scaling and
translation.
using "depth" would be confused with the possibility of having "real"
3D objects, with a width, height, and depth.
Ok so there are good reasons behind that. "depth-axis" would be a
solution,
no, "depth-axis" would *not* be a solution, and I wrote exactly why it
wouldn't be.
the term "depth-axis" does not mean what you think it means, and does
not make sense in the context of a 3D space; it also is not a commonly
used term in any other relevant API.
but it's too long
that's not the reason at all.
and x/y/z is a widespread convention. I was
just wondering if the GSK API contains other conventions, maybe less
widespread.
the conventions are mostly well-established terminology mutuated by
projects like CoreAnimation, the Android view API, and Clutter.
ciao,
Emmanuele.
--
http://www.bassi.io
[ ] ebassi [ gmail com]
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]