World: r3wp

I have e.g. screen painter in mind ... but with screen painter you 
can save exact pixel position, not generating dialect at all ....

what if i tell you that it was the main objective of the second prototype? 
:)

:-) well, then I can tell that someone found it usefull. Now what 
is its practical use? :-)

should i tell you? ;)

btw - what did you mean by "new dialecting method of R3"? What is 
new on dialecting itself, if 'parse did not change yet?

there is another function to implement dialects. you will find out 
soon enough.

Just to split your thinking Gabriele, is the Beta going to have a 
REBOL/Core .so for us Linux people?  With enough docs to have a go 
at embedding in something like say a D program?

(i personally prefer parse, but the new one is more efficient and 
so better for simpler dialects like vid etc.)

beta will be windows only.

eh, so we got something else than 'parse? How can dialect be built 
without the parser?

docs on the DLL... i don't think Carl has written them yet.

DOH!  :)

... using new method is the answer probably :-)

Wine capable?

i share your pain, i use wine all the time, and there is actually 
one bug in r3 on wine that forces me to start the other pc with windows 
sometimes.

Rasasfrasa  :)  Vista or XP?  I was just about to completely remove 
my copy of XP.

also about docs... i plan to be available here full time for a couple 
days after release, to answer all questions and provide some kind 
of support.

i don't have vista and i don't even want to get close to it.

but, i assume it works on vista too.

I am on Vista right now ... it is a fine ... useless, mess :-)

Neither do I, but for an R3 beta I'll boot one of the boxes to...windows(tm). 
 Rasafrasa.

Vista is pretty much what I expected MS to come up with, and that's 
a terrifying thought.

hmm, those docs could be really posted, even if not complete .... 
of course we would have to promise not to bother you with question 
before you are ready to release ...

the docs that are available will be posted on release.

You've come to a sad realization...Cancel or Allow

but, i bet you guys will have a thousand questions anyway.

pekr, right now, posting docs would mean all docs, since they are 
all stored in the same wiki

Gabriele, personally I'm of the opinion that releasing VID3 early 
will pose too many questions. If released later, VID3 will speak 
for itself, and people will go "oohh" rather than "oh no! why?". 
:-)

yes, I just meant posting the link to docs could speed-up after-release 
phase, as ppl would at least theoretically know what is coming and 
what is particular design meaning of new things. IMO post-docs-one-week-before-the-release 
could be a good thing to consider ....

I'm a little concerned about the direction to take Desktop Library 
II.  I want to make Sunanda and the team happy, but I don't really 
want a product with a pre-expired shelf life.  It's getting close 
to 3/4s complete, but have a feeling it may be an R2 only code base. 
 :(

Henrik - what does it mean, later? I am for later release, if you 
say its vital ... just state it a bit bettern than 1.8. I would be 
fine with 1.9., or 1.10. if you ask me ....

In which case, R2 will get a stable release of ESMTP and LNS (he 
said with his fingers crossed)?

Brian - so you still think that R2 release is going to happen? Well, 
maybe it will, but so far my opinion lasts - there will be no R2 
release - there is no time for it, and it steals time from R3 issues, 
and R3 is next-gen for us. My suggestion is to concentrate upon R3 
already.

pekr, I'm just saying that the developers don't need to answer questions 
for things that are already planned. "what about this?" "what about 
that?" "why is X feature not there?", etc. Rather spend time finishing 
VID3 than talk about how to finish VID3. :-)

also - one of motivations for R3 was that LNS needed better networking 
model. So not sure r3 LNS release could be so easily backported to 
r2?

Henrik - you know me and you know what I fear - pekr coming to final 
r3 VID, playing with it for few minutes, asking - how would I do 
that? And getting the answer, that it was not inteded to do such 
a thing and that it would require VID rewriting :-))

Yeah, but a production release of R3 is what, 18 months away?

so much away?

imo release could be regarded production level, if features added 
are stable. And that is imo also the plan. e.g. iirc unicode will 
not be there for 3.0 ... it will come later. But that does not mean 
3.0 could not be used for many usefull things already, and being 
called a production release, no?

I don't think it's that far away. I think there will be a ton of 
additional work on extending R3, that could easily take 1-2 years 
after the first release of R3.

That's what I was thinking.  R3 won't really be mainstream for quite 
a while no?

everything takes its time :-) I'm just of the opinion that soon, 
an army of developers will be needed to take advantage of R3 to bring 
it to its full potential.

But what about the "user" community during that phase.  They won't 
wait around will they?  Not to say I don't plan on trying my best 
to help out with R3, but I don't see taking it to a construction 
site boss for quite few more days/weeks/months.

easily everyone in here could contribute to official parts of R3, 
given that the quality of work is good enough. :-)

we need new C coders ... it will be a tough task, to attract new 
ppl being able to contribute good C code to extend REBOL ...

brian, I'd start adapting simple scripts from R2 to R3. Do that by 
adding multithreading, adapting to async HTTP, etc.

pekr, driver developers will be essential.

So I'm still back to planning for say an Invoicing application for 
a site boss.  That will be R2 code base for quite some time, no?

Cheyenne, RebGUI, Rugby et al...it's kind of where I live right now.

brian, depends on the state of VID3, I suppose. Just right now, you 
can only build simple apps with it. I don't know the state of the 
networking. Actually I haven't work with networking at all in R3. 
:-)