World: r3wp

Draw should be the same, afaik, which isn't that far. Have the parse 
improvements helped?

not so much ;-)

but the new grad-pen command of draw is awesome

Cool :)

that was seriously missing in R2 draw.. happy its in R3  :-)

By the way the DRAW function can't render that, it's crashing.

The DRAW function is still there? I really need to pay more attention 
to the graphics stuff.

i wonder why it's crashing. I thougth gobs was using the DRAW function 
in background, but seems not...

They probably call the same code internally, but the draw function 
may be crashing in a non-shared portion of its code.

to image works though?

sometimes ;-)

hehe

I'd put a :( on that.

I know we haven't been focussing on graphics or GUI bugs lately, 
but you should at least write the graphics bugs down somewhere.

You know it's a problem when you can't replicate the bug and focus 
clearly what the problem is.
Carl put a spell on me because of that (in his last note)

Heisenbugs are the worst :(

There is another problem with draw in Gobs.

When there is an error in the commands, nothing is showed but you 
don't know where it comes from.

blank page, that''s what you got

it usually renders up until the error occurs

that's not what i got.
i got a blank screen when an error occurs.

it depends on the error... its the same in R2.

yep it depends... Brian"s heisenbugs are everywhere in draw

well, it should do the same in R3. at least it did in earlier builds, 
but does PARSE have anything to do with that?

why parse ?

doesn't DRAW use the other fast dialect making parser? don't remember 
its name.

delect

yeah that its.

meant... yeah  that's it...

wahoo ... lot to read .. T___T  basically there is in Draw/AGG some 
limitations due to gradient  system and matrix translation bugs i 
don't know if they have been solved  since i pointed a them ...

steeve is working on annimated splash screen logo animated in svg 
for the next version of viva-rebol :P

rebol even our splash screen are ass kickers ;P

i'm fighting with several e-commerce solution (free ware) for a client 
i want to die ... how can web 2.0  without rebol can be such a pain 
T___T

Oscommerce, thelia, virtuemart, prestashop, magento, zencart, OSCC 
... have cool back offcie cool functionnalité but when you don't 
want to fit to the header, menu, left_col, document, right_col, footer 
design  you are face big troubles allmost all the engine in those 
product is to be remade....

why clients wants those shits ???? 

because they read that apache + php + mysql + ajax/css  was the top 
of  art .... yurk ...

can't anyone shake that area and put rebol in it ....  something 
like a rebol os-commerce all strong and mighty in 200Ko ... Ok you 
can go to 2Mo last limit... lol

(and yeah you will say to me but why you don't do your solution os-commerce 
like based in rebol ?)

hum the amount of  capabilities in a e-shop web site clients are 
used to see now in days  are big...

Stat tools,  catalog edition, shiping, card. And then the hosting 
solution simply doesn't know about rebol so if it's not apache/php/mysql 
or apache/java/mysql  you are fried unless you have full access to 
the hosting solution and you are able to install what ever you want....(cheyenne!/rebol/mysql-protocol 
etc...)

congratulation steeve anyway  ^^

on my computer your annimation is lighting fast ... (maybe too fast) 
it's a very lively lizar lol

As far i am, i made some useful tiny mezz, perhaps some could be 
in R3.

reuse: funco [b [block!]][head reduce/into b clear []]

** REUSE, reduce a block, but re-use always the same block 

** Actually, 3 time slower than a reduce block, but save memory and 
GC recycles if used massivly.
** I use it to pass small blocks of coordinates.

mulm: func [

 {multiply a matrix [a b c d e f] by coordinates x y, return coordinates 
 [x' y']}
	x y m [block!]
][
	reuse [x * m/1 + (y * m/3) + m/5 x * m/2 + (y * m/4) + m/6]
]

atan2: func [

 {Angle of the vector (0,0)-(x,y) with arctangent y / x. The resulting 
 angle is extended to -pi,+pi}
	x y
][
	if x = 0 [x: 0.0000000001]
	add arctangent y / x pick [0 180] x > 0
]

Project: func [

 {orthogonal projection of a point P on a line AB, return coordinates 
 [x y]}
	ax ay bx by px py
	/local sx sy ux uy ratio
][
	sx: bx - ax
	sy: by - ay
	ux: px - ax
	uy: py - ay
	ratio:  sx * ux + (sy * uy) / (sx * sx + (sy * sy))
	reuse [ratio * sx + ax  ratio * sy + ay]
]


vector-length: func [x1 y1 x2 y2][square-root add x2 - x1 ** 2 y2 
- y1  ** 2]

REUSE might run into problems with multitasking. Ladislav has talked 
about adding a native atan2.

Probably should be implemented with a closure!

Yeah, a closure that returns a function is a good pattern. However, 
a closure by itself won't reuse the block. It's the reuse that is 
the problem - the block probably won't be task-safe.

To be task safe, the module should reinitiate the function like this:
reuse: make :reuse []

Obfuscated thing

or with
reuse: copy/deep :reuse

Then you aren't reusing, which is why it will be task-safe.

but it has to reuse the same block, in a context

n

no

not globaly

That reuse is what won't be task-safe. Only non-modifiable series 
will be sharable.