World: r3wp

The registry functions are unset before runtime in /Core and /View, 
for security reasons. They are available to SDK apps if necessary.

They are documented in the SDK docs.

call "demo.pdf" is the same as run "demo.pdf"

in my case, windows loads acrobat and loads demo.pdf

Are we going to get a free SDK for this version?

Afaict, RUN is basically CALL "start.exe ..."

You wish ...

Got ya.  That is what I thought it was.

I do wish.  :-)

Must be a bug deleting random groups ...

has the sdk encapsulators been updated too?

No, the SDK isn't free. I'm not sure what extras /Command has yet 
- I haven't tried the final release yet, just test releases. Just 
got home.

no ...

the SDKs will be updated next week I think

Is there going to be one for this version?

The SDK will be released later this month.

great

Don't know about other platforms yet - have to talk to Carl about 
that.

Since Reichart hasn't come back and said such and such deleted x 
groups .. I am presuming it is something quite different

Reichart might just not be working today. Who knows?

Whoops, wrong group.

Thank you Carl, Brian for updating the Rebol/View. SSL/TSL has become 
such key module of any serious internet trafic during last decade 
that it's important to be part of the widely available version. I'm 
sure there are plenty of other important Fixes and new features on 
this release, but at this point  with my  limited knowledge of Rebol 
variants (still trying to learn all there is at the 2.7... ) it's 
the thing for me.

we don't have TLS ...

Yeah, the SSL code is a little old. Holger wrote it, I think. We 
have to do a much better job with the R3 SSL.

Any chance of getting TLS instead?

Ah.. As I was saying..  I don't know enough of Rebol..  So it's SSL 
but not TLS? Ah well, as far as I know the sites, SSL is ok.

TLS drops back to SSS 3.0 if required

SSL

For R3, we can get TLS, because the code would be in the open source 
portion. For R2 only the mezzanine changes are open source. This 
means that you'd have to ask Carl about TLS support - and he'll probably 
point you to REBOL Consulting :)

Release announcement: http://www.rebol.com/article/0447.html
Simple change notes: http://www.rebol.com/docs/v2-7.html


I'm trying to post the more detailed release notes in the comments 
of the announcement blog, but I'm getting caught by the blogger limits. 
One more message and I'll be done.

Impressive list of changes.

And incomplete - I'm waiting for it to let me post again,

There, the list is done for this release.

Why is Carl saying he has released 2.7.7 with TLS ??

I use Ladislav's 'closure.  Does the one in 2.7.7 supercede this 
now?

Looks like there is no easily accessible documentation for the R2/forward 
stuff ....

There is easily accessible documentation on the R2/Forward stuff: 
The R3 manual. Any differences from the R3 behavior is documented 
in extensive code comments in the R2/Forward source, which you can 
get in R3 (for now) chat, aka DevBase.

The CLOSURE in 2.7.7 supercedes Ladislav's one, and is derived from 
it. Go Ladislav go!

I don't know much about the TLS support in R2, if any. I guess I'll 
find out when we migrate the old RAMBO tickets to CureCode.

Easy = web accessible.

I suspect the TLS thing is an error .. unless he has been hiding 
it from us all these years!

The R3 manual is web accessible. R2/Forward itself is only useful 
to programmers, and they can and should use DevBase.

I went to the wiki .. and searched on funct ... didn't find the docs

OK, now that we have 2.7.7 released (even though there is more work 
to do, i.e. platforms and the SDK), it is time to look ahead to 2.7.8 
- which is scheduled for release in one month on February 1. The 
primary goal of this release is to migrate to REBOL's new development 
infrastructure. This means:

- Migrating the RAMBO database to a new CureCode project and retiring 
RAMBO.

- Using Carl's generation code for the manual to regenerate the R2 
manual, so we can start to get to work updating it.

- Porting the chat client to R2 using the new functions and building 
a CHAT function into R2 similar to the R3 version.


The R2 chat client might be limited to the ASCII character set, though 
support for the Latin-1 character set might be possible. Still text 
mode for now, though if anyone wants to write a GUI client (Henrik?) 
we can put it on the official RT reb site accessible from the View 
desktop. The server is accessed through a simple RPC protocol and 
is designed to be easily scriptable.


It turns out that Carl already rewrote the installer for 2.7.something, 
but it was turned off because of a couple minor bugs that we were 
able to fix in 2.7.7. With any luck, only minor fixes to the registry 
usage will be needed and we'll be good to go.


As for the rest, it's up to you. Graham seems to have a good tweak 
to the http protocol, and others may want to contribute their fixes.

What's the best way of searching the wiki?

Which one, the manual or DocBase? DocBase: http://www.rebol.net/wiki/Main_Page
- the manual: http://www.rebol.com/r3/docs/

looking at the wrong one .. .I was looking at rebol.net

Right. The manual is the official docs (which need some work still), 
and the rebol.net wiki is for community stuff.

If you want to contribute to R2 development, get on R3 chat. The 
client is R3-only for now, but the server and message store will 
be the same when accessed from any other R3 or R2 clients, or web 
clients if we really want them.

For simplicity people refer to it as chat, but the server and message 
store is really DevBase 3. CHAT is just the name of the function 
built into R3 (and later R2) that calls a DevBase client script from 
some web server.