World: r3wp

putting barriers to use in an already very small developer base is 
counter productive

I hope R3 has no barriers ...

I mean after one buys a couple of sdks and /pro versions .. there's 
no real need to purchase any more.

It's a dead end as a source of revenue unless you have lots of new 
users

the first encap licensing scheme was very unusual

Pekr, tell us more about R3

will we be able to build networked games with 1000s of concurrent 
users ?  :)

Dunno :-) But - why not. Surely View is not the right engine to create 
games ;-)

I mean - supporting infrastructure - networking - why not ...

Gabriele wasn't able to get chord working

in R2

shouldn't be a problem in R3.

what about memory management?

is it better?  I used to get out of memory errors in encapped apps 
if I waited long enough ... days to weeks

Support for 64 bit windows?

can't tell yet. no tests that big have been run yet. there are a 
few recycle bugs that are being fixed.

my Cerebrus antispam program would eventually die from lack of memory 
... after some weeks of running

I would like to resurrect it if I can .. if memory management has 
improved.

the decompress function has a memory limit option. it's been discussed 
whether it should be removed or not, but such things will be necessary 
in an embedded environment.

overall R3 uses less memory than R2

do you know why?

More optimized datatypes, tighter code and GOBs.

and if you're running a non-gui app .. any difference?

I just started an R3 console. Everytime R3 starts, it displays a 
splashscreen with rich text, a picture and two buttons in it. When 
I close it, stats returns 1276368 bytes.

got a screenshot ?

of the rich text?

contains secret info, can't show it. :-)

I think there is a blurred one somewhere...

geez ...

secrets ...

http://www.rebol.cz/~cyphre/stuff/r3-alpha-splash.jpg<-- it's pretty 
old. the new one contains clickable links.

doing something in R2 would probably require 5-6 MB memory.

something like that

where's the rich text?

you're looking at it :-)

Ok, not video styles anymore?

sorry, I'm in fact wrong. it is in fact different lines. but it would 
be possible to do in rich text.

I should do some rich text tests and show you that.

rich text in an area gadget

not supported yet. will come.

I wonder how the different styles will be implemented .. perhaps 
as they do in web browsers?

probably something like that

I hope you are just trying to keep a secret from us all Henrik because 
it would be worrying to think such design decisions haven't been 
made yet.

which ones? :-)

How sttyles will be implemented.

do you think that it will be impossible to make such a design decision?

I was meaning how to enter the different styles inside a text box 
.. would it need a menu bar to pick the different styles

drop downs for emoticons etc

it probably would. there would be great value in a single text editor 
style with toolbar and things.

view [rich-text-editor]

looks nice :-) I think we should do that.