World: r3wp

e.g. translate 100x100 rotate 30 text "something"

or set up a straight line "spline" for the text ...

possibly

Well, seems to me it should be changed.

changed in AGG or in the code?

Text should rotate at the point where it is being drawn

in AGG.

boxes don't rotate around 0x0

why should text?

or do they ??

well, if you did that, how would you rotate around another point? 
I won't argue for one solution or the other, but this approach seems 
natural enough to me.

I think they do

which approach?

1. first you draw
2. then you rotate
3. then you translate

in classic REBOL order

which means start at 3. :-)

speaking of which, it could be fun to see a LOGO like dialect for 
DRAW. fun for the kids.

Gregg has one.

that's good. I don't have to do it then.

do you have to create the kids first?

got plenty of those around, not mine though. I don't know how interested 
they would be in it yet. I spent countless hours in COMAL80 when 
I was a kid drawing with the "turtle".

Comal80 - a Danish product?

I remember I had a Comal80 interpreter for my C64.

I don't remember what it was. I think it was for several platforms 
but I used it for my C64.

I think it was a great drawing tool. very straight forward approach 
to drawing.

then I got an Amiga and was exposed to the horror that was Amiga 
Basic.

I've got my graphing utility written now in my postscript dialect

just labelling the y-axis is a problem because of the way AGG does 
the rotate vs PostScript rotate command

and there's no way to save a graphic state in AGG.

ah, yeah that could be a problem

Graham, AGG rotation: that's just an effect of the way AGG does its 
transformations which apply to the whole image. The rotate command 
is just a shortcut method of specifying just the rotation angle of 
a transformation.

transform (origin) (angle) (scale-x) (scale-y) (translate)

What you want to do is set the origin to the centre of your object, 
then change the angle and translate as you wish.

I agree that it is a bit uncomfortable at first. I was also expecting 
something simpler like in flash, but I suppose this way is more powerful.

Anton is right. DRAW works on lower level than FACE so there is only 
one tranformation matrix per DRAW block (ie. it is applied on all 
rendered primitives). OTOH you have relatively wide range of commands 
how to control the transformation matrix or even use the mtrick stack 
to push/pop different trnasformation states to apply  nested transfromations.

(Note that due this lower-level approach the drawing is also faster.)

The transformation handling is more simmilar to OpenGL in that way. 
See some OGL docs to get the idea and you will see the benefits.

Is there a reason, why SPLINE doesn't draw anything with just two 
points?

view layout [box effect [draw [pen black spline 10x10 90x90]]]

Well, SPLINE is only drawing straight lines for me. Maybe you want 
CURVE.

Geomol: the SPLINE has currently 3 and more points allowed as it 
was meant to use more as spline not line  but we can change this.

Cyphre, it makes sense to have spline draw a line with only two points 
in a gfx application, where the user start a line with two points 
and may continue with more points or may just end the line after 
only two points.

can't the drawing application change it to a line if it ends in two 
points?

is there any way to extract curvature X/Y data  from any of the primitives?

example, sliding objects on a path, connecting lines along splines, 
etc...

Maxim, maybe a Bezier curve is what, you're after? Try
do http://www.fys.ku.dk/~niclasen/rebol/fysik/bezier.r
You can find the Bezier function inside the script.

Maxim: I have been thinking about that feature many times. It would 
be great to be able get back the X/Y data of DRAW shapes. This should 
be part of R3 for sure. Don't know if Carl would like to backport 
it to R2. We will see. At the moment you can compute the curves in 
rebol directly (like Geomol does).

will they be pixel perfect?

Cyphre, was has to be done for R3 IMHO is a way for us to probe values, 
just like a 3d package allows you to get point, edge, curvature info 
out of transforming and deforming geometry.

although some will argue this is slow, its actually VERY fast, since 
the slow part is usually the calculation and drawing.  once that 
is resolved, probing is insignificant.

using liquid I am already able to build a draw network, which recycles 
values and allows multiple elements to cooperate.  but I can't get 
that within each element itself.

Maxim, there will be some possibility to access/modify the internal 
representation of DRAW shapes in R3 so you can 'bypass' the DRAW 
parser and just rerender what is already in the 'pipeline'. This 
could be handy especially when reusing big and/or complex DRAW shapes 
etc.