World: r3wp

I tracked down the probable cause of the massive memory-eating behaviour 
of Christian's menu-system-demo.r

The problem depends on the user's file-system. In my case, I have 
many many files under my rebol/view directory.

The demo makes a huge nested menu by recursing every file, so that:
>> length? mold dir-data
== 717187

When I work around this problem the menu-system looks really nice 
!

(I have yet to examine the code, though)

I don't like gob; gfx and vis seem like better choices to me. Carl's 
limitation of three letters starting with a G limits us a bit. Under 
that rule, I would probably choose gfx.

So far proposed words:

(gob! face! gfx! cell! atom! layer! vis! sprite! bob! blit! )

the only which really applies is gob! or vis!  others are all pretty 
much non-related.

people you forgot the most obvious and pretty!

gel!

graphic element.


but I don't see the point of the heated debate over the name gob. 
 gob is chunk, a morcel of something.  in this case its pretty precise. 
 its a part of the gui, not the whole gui... and in another sentence 
its also meaningfull... when you say gobs of text, it means a lot 
of text... so in reality we WILL need gobs of gob to make up one 
gui.

(sorry I forgot gfx which is also related (and my favorite appart 
from gel! or gob!))

grob?

gels are used in lighting in front of spots to color the lighting... 
btw.

Gel relates to one of the first famous demos :)

Where it says: Grab the gel and drag it around.

btw, no more names, one day is over. the list has been sent to Carl.

I was thinking gel! too :)  Had I been here earlier...

(after all, I did suggest cel!)

I would like to know, how and if /library interface changed for R3. 
It was long promissed, that integrating external resources should 
be made easier (see Carl's answer in RT QA channel IIRC), and I could 
not find any mention of it in Carl's DevCon slides. I would excpet 
changes in at least how arrays of chars, structs are handled, as 
well as more than 16 callback support .... maybe even more datatypes 
supported. 


Maybe a rather weak state of library interface put REBOL into integration 
isolation. It is not easy enough for newbies to wrap to libraries 
....

one thing that I would love for R3 is the ability to directly access 
the image byte data of a rendered window - a read only ability would 
be fine - or even editing with a lock/unlock mechanism.  The main 
reason for this is the allow direct pixel analysis for non-standard 
interfaces - eg AGG/Draw based interfaces where colour can be used 
to determine function of an irregular shaped button.  The basic premis 
is that you draw your UI composite then rather than having to do 
cumbersome bounds checking you can simply test the pixel colour under 
the mouse and call an activation function based on that colour - 
eg 0.0.254 = a save function.

Without that ability pixel perfect analysis is only possibly by the 
slow process of rendering to an image then testing which is very 
processor intensive.

Perhaps a simple way to do this would be to implement double buffering 
by default and allow buffer access.

isn't View already double-buffered?

IIRC the problem is, that we currently use sw renderer only ....

view probably is double buffered - but getting access to that buffer 
is something that im not sure we can do

So, today is THE DAY? :-)

isnt it the 15th?

no, 1.6. R3 should be released to selected group of developers. I 
don't even want to be part of that group, but it is cool anyway :-)

15.7. should be public beta release?

ahh ok.  Doesnt sound like they've finished the bits im most interested 
in yet anyway (Draw etc)

well, not sure View is part of initial release, but who knows ...

at least with a core and async I can get the MMORPG server engine 
back up and running...

1.6 in this country

first day of winter

what? first day of winter? :-)

To late, but GLO! = Graphical Lowlevel Object

Too late.

how /library changed - no change yet, i see library! and routine! 
in R3 but i assume that is still using the R2 code... (or not, but 
Carl has not documented it yet). I think, this will be part of the 
open source code, so you should not need to worry.

petr, we actually put together a "micro vid" for today's release 
- just for testing / examples so you don't have to code gobs directly... 
done in less than a day.

i think those who have been good all year might get a nice present 
today. :P

Gabriele, if I may: Lucky bastard. :-)

:P

hey henrik, i thought you had been good this year, but i have to 
change my opinion now :P

where is the christmas tree?  ;-)

if you haven't made one, no gift for you.

nooo! :-)

I have many trees,  which one should I decorate!   :-)

Santa will drop the gift based on how good the tree is.

hummmm....

on how good the tree is at rebol?

gabriele has the docs (or even the dialect) for rich text been completed 
yet?

docs, not completed, dialect is running.

nice - any notes on its execution speed vs other richtext controls 
eg MSRichTextBox ?

don't think anybody has done benchmarks yet.

would you consider it a good idea for 3rd party developers to make 
an RTF importer or will RT do that?