Re: [clutter] x,y,z coords
On Thu, Sep 03, 2009 at 09:57:38AM +0100, Emmanuele Bassi wrote: > because Clutter mainly (and currently) targeted at 2D elements in 3D > space, not at fully 3D elements. I'd be happy with 2D elements--for example a text entry area which can only be a rectangle, but there is no good API to place them or manipulate them 3D. I'm looking for the ability to mix opengl and GUI elements together. For example, rendering an editable text area on the side of a box, then doing opengl markup graphics on the text itself, overlayed onto the text which is context sensitive to the text layout. Of course, the box is a real object, so it can move around in an environment modeled by (as an example) the open dynamics engine. That sort of thing. Thank you. -pete -- To unsubscribe send a mail to clutter+unsubscr...@o-hand.com
Re: [clutter] x,y,z coords
On Thu, 2009-09-03 at 01:00 -0500, Peter Keller wrote: > Hello, > > I've noticed that the clutter api provides placement for actors, but > only oddly in the sense that the actors exists in a 3d space, but the > set_position calls only take shorthanded 2d coordinates. > > I find it weird that if I want an actor like a rectangle or text actor > rotated around the y axis I have to rotate it with the rotation api. Why > can't one specify the 3d coords for three of the points of the actors if > I happen to know what they are? because Clutter mainly (and currently) targeted at 2D elements in 3D space, not at fully 3D elements. > In reading and trying out the API, I get the sense that the API was a > 2d layout system that later got applied to 3d objects. no, it was a precise design choice that was made at the beginning of the project. ciao, Emmanuele. -- Emmanuele Bassi, Senior Engineer| emmanuele.ba...@intel.com Intel Open Source Technology Center | http://oss.intel.com -- To unsubscribe send a mail to clutter+unsubscr...@o-hand.com
[clutter] x,y,z coords
Hello, I've noticed that the clutter api provides placement for actors, but only oddly in the sense that the actors exists in a 3d space, but the set_position calls only take shorthanded 2d coordinates. I find it weird that if I want an actor like a rectangle or text actor rotated around the y axis I have to rotate it with the rotation api. Why can't one specify the 3d coords for three of the points of the actors if I happen to know what they are? In reading and trying out the API, I get the sense that the API was a 2d layout system that later got applied to 3d objects. Basically, if I were to design a 3d box with text actors on each face, it would be needlessly complicated to initialize it. Also, if I weren't to use the timeline to animate stuff and instead I animated it myself, there doesn't seem to be a good way to do that either because there doesn't seem to be a good way to get at the mesh points of any particular actor. The reference manual hints at the possibility, but doesn't explore it at all. Am I missing some large part of the API or something? I see clutter_vertex_* but no real way to create an actor and set the 3D verticies manually. Thank you. -pete -- To unsubscribe send a mail to clutter+unsubscr...@o-hand.com