World: r3wp

Right now: Only one path at a time and it's monochrome. I'm not sure 
which path types are supported. You can't load XML files with it, 
only pure path data.

I will leave it up to someone else to make the rest work. :-) It 
wasn't that hard to get working.

I had a simple SVG -> Draw script which Shadwolf took and enhanced, 
but it barfed on more complex SVG's due to some inherent limits in 
draw ... Shadwolf can tell you exactly what the issues are. If they've 
already been solved or lessened under v3 then that's great news indeed.

Here's a line and ellipse intersection function:

load-thru/update http://anton.wildit.net.au/rebol/gfx/intersection-points-of-line-and-ellipse.r

do-thru/update http://anton.wildit.net.au/rebol/gfx/demo-intersection-points-of-line-and-ellipse.r

It's got some debugging lines still in it, so console will fill up.

The demo also has a problem with control of the ellipse - which turns 
out to be a tough math problem to solve. More difficult than the 
line/ellipse intersection. Maybe it will take me a week to do... 
 but anyway the demo works well enough for now.

i have a question related to the futur draw engine.

will exist a way to capture the current offset inside a draw block 
?

i give an example:
draw [ text ["test" red :off "red text"]]

having the variable off returning the offset between the 2 strings

would be a fantastic feature

i precise: the real offset inside the gob (not the carret)

i'm talking about that because i currently try to do a draw editor 
with R3 (like my old easy-drawer).

but to intercativly move or deform a draw block, i need to construct 
a serie of handles (gobs) at some calculated points. and so it's 
currently a tragedy to have to simulate the draw engine to get th

... to get th

... to get these coordinates.

i don't know if i'm clear....

in fact it would be the same feature than in parsing

offset: (to get the cur

...the current offset)

a set-word!

another question: in the current alpha, the matrix command seems 
not working like anounced in the wiki, is it normal ?

Steeve, if you can make some examples with the matrix command, we 
can make an entry in the bug tracker.

i have no examples, it doesn't work at all

Steeve, can you try it also in the public R3 release?

Sorry, it seems that you are.

well My svg engine is working and got trouble only with matrix calulations 
due to an odd bug in the adapted version. Next i don't like the way 
my SVG works  I wish to be able to do it  in plain parse way (My 
method in not really elegant but it works fine  in most cases SVG 
is an XML file so the XML data is converted to REBOL  objects using 
parse and then i process those objects to convert into draw/Agg instructions). 
That was the fastest way i found at that time since what was important 
to me was the result not the beauty of the processing way.

to tell you the truth parse gives me powerfull head haches  ^^ so 
if i can't use it I don't use it ... I know that's bad !!

http://shadwolf.free.fr/svg-demo-shad06.ris the lastest version 
of my SVG engine. Well in fact parse gives me head haches only when 
i have to parse XML  datas ...

since someone was enough kind to write a XML2object script why not 
reusing it for such a purpose  ^^

what i like too is that once you get the conversion to draw dialect 
 done you can keep simply the draw instructions instead of the SVG 
ones  ^^

i done a  guitare notes easy learning  rebol script  using that SVG 
engine (to save some time) http://shadwolf.free.fr/guitare-manche.zip

that show how you can input an svg image and use it to draw on top 
of it  using AGG (we can imagine too animation displaying too etc...)

Nice guitar notes script :)

yeah really cool  :-)

thank you  ^^

Agg spawns some interesting projects:


Cross GL - slovak library allowing some interesting things - http://www.crossgl.com/index.html


Fog GFX library - CPU instruction optimised AGG "add-on"? library 
from Czech author (author of AsmBlit and BlitJIT)
http://twopixels.blogspot.com/search/label/fog-graphics

From the CrossGL perspective, application demonstrates:

•	 	 Interactions with Hit Testing (buttons) at any angle and scale


What is missing in our AGG implementation, capturing events from 
gobs (?)  embedded in a draw design.

my R2 Glob engine does it  ;-)

so its something you can build using current engines.

but it should come out of the box... I agree.

I've been lobbying to have individual control over each draw element 
by word reference for years... it would make it so much easier to 
build all graphics apps.

agree

and we could extract data FROM the AGG image, like vertice points 
and stuff like that.

CureCode it :-)

yeah .... events applyed directly on draw elements or draw able to 
"map" and show directly other graphical organised video layers who 
be so awsome that way from example what is rendered on sub engine 
external like opengl one could then be applyed to a regular vid area 

In one hand you will have an easy way to interface events and on 
the other hand you can map rendering any kind of sub rendering

the idea so far is to be able to show anything using a draw pipeline 
and using events definition native in VID since it's the most accurate 
way so far to manage events.

the idea is to allow then any kind of visual layer to get an embeded 
acces to a VID  window and it's content. we go one stop further then.

(could be video, or 3D animation etc...) AGG will be just the entring 
gate and link for those contents

not having to separate the external graphical library from the main 
graphical library is what all the other widgets library are doing 
for example QT, wxWindows, TK, Gtk+ have all their own plugin and 
related object to embed a sub layer to their own window compositing 
system

on text without the size of each character you can't simulated a 
realistic text motionning. This works greatly with fixed font but 
fixed fonts are not supported on all OSes and they are pretty borring.... 

fixed font system forbid de coders to propose a font selector to 
their users in their programs one of  the feature all the common 
text editor have.

maybe a way to solve this and introducing in the area something new 
could be to map directly events t o draw  text idiom. the way you 
create one and for all a event handler you apply it to the text idiom 
 and any time you use i t in your draw definition then the event 
mapping is avaible.