World: r3wp

map! will be used for fast unique lists. And it's too soon for multimedia 
datatypes... I think audio/video will not be datatype at all, rather 
a scheme I guess.

Don't forget user-defined datatypes, which will also be in R3. Some 
of the missing types will be added that way.

Will we be able to use find against a  map! ?

I think so, but you probably won't need to - map! is optimized for 
this kind of task without needing find.

There starts to be series of VID3 blogs. So - those who want to affect 
some design principles, can share their opinion there ....

Is there any way we can have a hybrid R2 with the new graphics system 
and the old core?

Some of us are tied to R2 because of networking

I wouldn't bet on it. That might be a month's worth of work, but 
I'll ask for an official statement.

At the moment, I'd like the opposite -- new core, current graphics 
: )  I don't want the new graphics system before it's ready.

I suspect the former would be more easily done than the latter

After all one starts with core and then builds view on top of it

Then how do you complete the new view without the new core underneath?

I suspect view is not really dependent on core

the event system is different, which I believe also has something 
to do with ports, which are a different concept in R3.

it's more for networking ( async ) and LNS

oh .. ok.

LNS is high priority for R3. Needed for Devbase.

Just seems to be a lack of participation in the R3 process ... and 
I'm wondering if it's because the changes are too great

If there were a way we could incorporate the changes into projects 
we are currently working on ... it just might make it easier

I think it's because the changes are very large, yes. It's rather 
impossible to do any real GUI work as long as VID3 is sitting in 
this current state, where we're trying to figure out how VID3 should 
work and that things might change from week to week.

What's the best way to get started?

with what part of R3?

There's just too much information there at present ...

playing with Vid3

I see Carl's current intention is to nail Vid3 down

probably get one of last year's builds and simply toy around with 
the layout dialect. current builds have VID3 left out.

yes, there are some design issues in that style creation is too complex 
and must be simplified. Carl and Gabriele are sorting that out in 
private.

we need an dummy's guide to vid3

we have one, but it's too complex :-)

well, actually I don't think it fits with the latest VID3 build

Ok, an idiot's guide then!

the dialect itself is easy enough.

it's probably a good idea to study it in order to find out how faces 
can work together and such.

I suspect we are only going to find it's limitation by starting to 
build small apps and see how it scales

it's probably mostly limited by the number of styles currently.

which build has Vid3 in it?

the public release

which is where?  I'm getting circular links

http://www.rebol.com/rebol3/=> http://www.rebol.com/article/0347.html
=> http://www.rebol.com/rebol3/

http://www.rebol.net/wiki/R3_Releases

Ok.  Thanks.

gotta go to bed. there are some more docs about VID3 in Docbase.

My take is VID3 will not stay way it is now ...

Meaning?

too complex?

Is there much point at looking at it until Carl has decided where 
it's going?

I think not ...

I was told to hold off on documentation for VID3 months ago; pre 
Unicode release even.  And I may not be the best tech writer for 
the task anyway; as I didn't really "get it" to a level required 
to write the good end-user docs REBOL deserves.  We'll see what happens 
in the upcoming days.

Perhaps we need a "rebgui" for R3 as well ... ie. a simplified gui

That's what I hinted to on the blog.