World: r3wp

I wonder if gaberiele ever feels like the fortune teller at a fair 
- all these rebolers coming up and asking about their future :)

More like a tease

:-)

what info was supposed to leak? :-)

dunno. just kidding. :)

Gab, when thinking about the next generation GUI stuff for Rebol, 
take a look here: http://www.cs.cmu.edu/afs/cs/project/amulet/www/amulet-home.html


The thing that's (was) really cool about Amulet is the usage of constraints 
to keep everything updated. Perhaps a bit what Max has done with 
Liquid. But very nice to use.

perhpas someone has the answer to these questions? -> 

* Is Rebol3 a product beside or instead-of current Rebol?


* Is support still valid for Rebol2 products after release of Rebol3?

* Do puchaged licenses still work on Rebol3?


* Do commercial SDK / View / etc.. users need an upgrade? does it 
cost?

* Will Rebol2 product be still enhanced?


* What is adviced to do? Stick to Pre-Rebol3-versions or go with 
Rebol3?

Guess
1. b
2. a
3. no
4. yes
5. no
6. r3

Is that an official Carl/Cindy 6 rules for Rebol3 list? ;-)

No, it's my best guess :)

this was a poll wasn't it ?

:)

Could be a poll indeed ;-) But i dont hope its b,a,no,yes,no,r3 although 
i think it could become..

R3 will eventually replace R2, but for a while both will be available 
and supported.

R3 does not need licenses, there's no need to pay an upgrade etc. 
Some plugins may cost money though (eg. ODBC). However, nobody stops 
people from doing alternative free versions of them.

(RT does not plan to make money directly from R3. Notice that the 
stress is on the word directly.)

I'd advise to go R3 as soon as possible for you, for many reasons.

Note, my answers are not official answers, but I think they are very 
close to what Carl would say. If you need official answers please 
contact RT directly thru usual channels.

Gabriele - is it already known, which parts will be commercial? You 
said ODBC - really? Wasn't it mentioned in the blog, that DBs come 
free?

i used ODBC as an example - i don't really expect that to be commercial 
(but probably left to third party)

anyway, no plan was discussed yet about commercial plugins. (RT probably 
has a plan already, it just has not been discussed with us)

Gabriele - how goes VID+ specs creation? :-)

also, keep in mind that the commercial part is mainly going to be 
AltME 3, not plugins.

Commercial plugins - well, the API was introduced, no? Is it available 
in alpha?

VID - we hope to have something by end of this week.

I expect altme 3 being kind of IOS, which will allow mixture of free 
as well as commercial apps

plugins - the alpha does not load them dinamically, but it's basically 
what the host program does (defining devices, natives, and so on)

can R3 handle digital certificates? (it was discussed in regards 
to plug-ins, SDK ...) - I think it might be crucial to get rebol 
out to the public, trusted ...

also, Carl has said he wants to finish rebin before working on plugins 
as separate dlls etc.

and it will load them dynamically later?

ah, that is exactly what I wanted to ask - rebin ...

R3 does not have encryption modules yet, they will probably come 
later. but notice that nobody stops people from linking to OpenSSL 
and provide a complete SSL solution.

not sure if correct, but I can see rebin as kind of "packager" for 
rebol? Will it allow us to pack various things - e.g. libraries, 
scripts, images, or other resources, and add it to the rebol.exe?

(maybe RT will do that, or maybe we'll use the SSL module in R2...)

rebin is a binary format for rebol values. like now we have a text 
format (produced by mold), then we'll also have a binary format useful 
both for storing (when user-readable is not needed) and for internal 
communication with plugins

but... Carl hasn't said much more about rebin...

nobody stops = it is not available yet. With R3 spreading like fire, 
we might need it sooner than later, or we will not be able to provide 
lowered security apps, letting users feel safe, because they will 
know, it comes from some trusted party ....

Services requires encryption so you can bet release version of R3 
will have it.

but, SSL is more than that.

and, R3 might just use the same module found in R2 for SSL

if you need more, you just make your own SSL device.

SSL is specific protocol. I am not speaking about encryption here, 
but about the trust, that is what certificates are for. IIRC the 
api for them is inside, it was not just exposed. And IIRC2, Ladislav 
once mentioned he will do it? But I could misunderstood him ...

certificates are just signed files with public keys.

so... there's nothing really special.

ie you can do that in R2 with mezz code.

what you can't do with mezz code is cert handling for ssl://

so that what i was talking about :)

Gab, you want to tell me, that I can check for certificate validity 
or actually sign something using my certificate, in let's say, PKCS#12 
format?

why not?

R2 has RSA, DES, etc.