World: r3wp

Joanna, there aren't a lot of docs on serial ports, but the basics 
are easy enough.


; port speed data-bits parity stop-bit (order is not significant 
IIRC)
port-spec: serial://port2/38400/8/none/1

p: open/no-wait port-spec

p/rts-cts: off  ; THIS IS REQUIRED TO TURN OFF HARDWARE HANDSHAKING!
update p

Then you can just INSERT and COPY on the port.

Graham, what are some of the "tweaks" you made to Http that BrianH 
has mentioned for inclusion in the next R2 release?

http://rebol.wik.is/Protocols/Http

You can confirm that it does what it is supposed to do by looking 
at the http traces.

Doc in the Core group: "this could be a really great addition to 
R3 (or even R2)"


Policy: Additions of new globally defined functions to new R2 releases 
almost always must get put in R3 first, go through consensus, testing 
and the REBOL optimizer, then be backported to R2 (usually through 
R2/Forward). Enhancements of existing functions in comparable areas 
of the code (not ports, View or library) also go through the R3 gauntlet 
first. If you want R2 /Core enhanced, get to work on R3.


Change to the semantic model of R2 isn't going to happen: No new 
port model, no new View, no extensions or host code - use R3 if you 
need those. New (real) R2 datatypes are unlikely, though faked backports 
of R3 datatypes are OK and have already made it into 2.7.7, with 
more to come. Natives that can be fixed without changing the semantic 
model or adding new datatypes are fair game though.


Bug fixes will be done though as long as code (that we can't fix) 
doesn't depend on the bug (no fix to PICK, POKE and AT's off-by-one 
error, for instance), as will backwards-compatible enhancements to 
R2-specific areas, like the port model, View/VID and library support. 
Backwards-compatible means we also test it against existing code, 
so if you want to test it against your favorite code, please do so 
and tell us what you find.


These fixes are coming, at least in theory - someone has to do the 
work. If you have a favorite bug you need fixed or enhancement you 
need, do the work yourself or pay someone to do the work (REBOL Consulting, 
perhaps). Changes go in as they are made, and they are made by people 
with priorities. If you have priorities too, act on them :)

If anything we do breaks your code, *please tell us*. We really don't 
want that to happen. Backwards compatibility is a top priority.

This is my attempt to link to the wiki docs

http://rebol.wik.is/Man

so,

man //

WIKI:
    http://www.rebol.com/r3/docs/functions/z-q-q.html

It's a hacked 'help ....

oop s.. that should be 

man ??

This assumes that the docs will be fixed .. currently  < maps to 
-gt and > maps to -lt in the docs.

Maybe someone can improve the parse rules for me

man -> help/doc

in R2?

An enhancement to an existing function that is compatible with R3? 
Absolutely, it will be added.

Totally within the rules :)

just need to get Carl to generate r2 docs in a similar location

Right. That's part of the the plan for 2.7.8.

I loaded the new REBOL/View 2.7.7.3.1 1-Jan-2010 down and tried to 
run it without installing.

It just writes a bypass-install file with true in it, but it does 
not run.

However starting it with the option --noinstall still works as expected.

Noted.

Have I read the blog correctly ? SSL ODBC and encryption added to 
REBOL/View Standard ? This is a nice news !

Indeed, a "YAY!" is in order :)

What is a YAY ?

A cheer. Your team just won, Yay!

I have to use 


call/show "cmd" to see the shell .. is that the expected behavior 
these days?

Yes.

That was a 2.7.6 change Graham. It bit me, so watch out.

Yes, I knew that and I wondered if we were going to revert back to 
the 2.7.5 behavior.

My recollection was that it was always just call until 2.7.6 ..

I campaigned to have it changed when it happened, but I think I've 
ported all my active code to the new syntax now, c'est la vie.

me too

Sorry, the 2.7.6 changes are sticking. In terms of functions that 
have affected existing code, that means the changes to CALL and EXTRACT. 
We're trying to be more careful in the future, but we're mostly concerned 
with compatibility with the previous version. If you have a favorite 
app that needs to keep working, get involved with R2 development 
and testing.

R2/Forward will be trying to backport as much of the current behavior 
as we can to versions as far back as 2.5.0.

Changes to natives are tricky to backport, so CALL is unlikely to 
be fixed by R2/Forward. I suppose that's alright since no platform 
for which 2.5.0 is the current version supports CALL anyways. C'est 
la vie.

Steeve, how's the R2 chat gui going?

Actually, the GUI can get started before the API is - the semantic 
model of DevBase is pretty well set already.

Agree. The project can be separated in two task.
- Working on a gui

- Refine the current chat app to extract a bunch of usefull functions 
(app API).


Idealy it should be 2 separated apps, so that we could write different 
GUIs for the same app.

what about   "dt"  function in Rebol 2.78?

dt: funct [
    {Delta-time - return the time it takes to evaluate a block.}
	block [block!]
][
    start: now/precise
    do block 
    difference now/precise start
]

Yeah, that's likely.

are there any docs about encription functions that are now enabled 
in view ... I could find some rsa-* and dsa-* functions by trying 
in console

http://www.rebol.com/docs/encryption.html

Do you know if the released /View has the "export version" restrictions 
mentioned in the docs, or whether it has the full encryption?

Nevermind, found it, full.

I'll whine quietly again about the name DT. <whine>

I agree it should have a better function name.

thanks doc, I swear I was googling for rebol encryption but didn't 
find it

Hmm... could be mistake there on export vs full. Will need to investigate 
that. Should be export by default. So, don't depend on full for anything 
until we can verify, which may not be easy to do.

On delta-time (dt), I tried to use it in R2 yesterday... Well, next 
time. G: yep, bad name, bad. But, easy.

'delta-time?

Note it is defined:
dt: delta-time: func ....