World: r3wp

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 ....

ah

>> ? delta
Found these related words:

   delta-profile   function! Delta-profile of running a specific block.

   delta-time      function! Delta-time - return the time it takes to 
   eval...

   dp              function! Delta-profile of running a specific block.

   dt              function! Delta-time - return the time it takes to 
   eval...

I note cd no longer requires a file type in R3 .. .can that be ported 
back to r2 console?

as for profiling, Gabriele mentioned, that it might be usefull to 
add timestamps to trace output. Would allow to build profiler ...

(related to R3 trace)

if not time-stamps, line numbers could be useful, if they are not 
already there.

Graham, the file management functions are still on the list to be 
included. I just didn't have the time for 2.7.7, so they'll be in 
2.7.8.

neato ..

Some of the R3 versions still need work, and I didn't have the time 
to review them to see which ones. I'll import the fixes that are 
solid for now, and the LIST-DIR after the R3 version gets some polish.

All of them have been backported already and are in R2/Forward.

Henrik, loaded code doesn't have line numbers, or lines for that 
matter. Lines are a string thing, not a block thing.

BrianH, I was simply thinking of a counter for trace outputs.

so I can point to or find entry 34672 quickly in a debug session 
dumped to a file.

>> s1: "    abc     "
== "    abc     "

>> trim/head s1
== "abc     "

>> s2: "0abc0"
== "0abc0"

>> trim/head/with s2 "0"
** Script error: incompatible or invalid refinements
** Where: trim
** Near: trim/head/with s2 "0"

>> trim/with s2 "0"
== "abc"

if  /with and /head can be combined together , Things will get better

/with is documented to imply /all in R2 (see help trim).  You might 
lobby for /with to be deprecated in favor of a new refinement, like 
/chars, which can be combined using /head or /tail or /all.  I agree 
it would be nicer.

Here's a workaround to remove leading zeroes which can be adjusted 
to remove any leading characters:

>> zero: charset [#"0"]    

 == make bitset! #{
0000000000000100000000000000000000000000000000000000000000000000
}

>> not-zero: complement zero

== make bitset! #{
FFFFFFFFFFFFFEFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
}
>> s2: "0abc0"              

== "0abc0"
>> remove/part s2 find s2 not-zero

== "abc0"
>> s2: "000abc0"                  

== "000abc0"
>> remove/part s2 find s2 not-zero

== "abc0"

To Fork: 

Just  use /with  , continue to imply /all with it. ,           Thus 
won't  bring   compatibility problems.
/with means /chars/all
/with/head  means /chars/head


So, /chars

Thus,   we don't  need /chars

I guess you've got all the bases covered if /with/head/tail works, 
but it seems to me that trim/with should behave like trim/with/head/tail 
by default (e.g. how trim behaves when the charset is assumed to 
be whitespace)

oh, I made a mistake. 
I thought /all = /head/tail  .  that's wrong

So, now I've noted two more instances of that crash I reported on 
29-dec-2009. Seems it's not bound to running REBOL in Parallels.

Fish, try here.

The SSL/TLS in 2.7.7 works exactly as well as it did in /Command 
in prior versions. The only change was licensing.

We didn't do anything extra to test the TLS/SSL in 2.7.7.

And there are no known examples of tls://

yeah, that's what I was asking.

ssl works fine

RT likely does some internal testing, but it wouldn't be anything 
new.

Presumably it is a port of the stuff Holger did for the Miami stack 
... which included tls, but .. no one has seen it working.

Spent last night updating R2/Forward - it was about 6 months behind, 
due to various issues, but R3 for those six months hasn't been focused 
on new functions so there isn't much to do. I should be done by today, 
and they should be portable to 2.7.8.

Gald to hear it.  Also, hoping to see some feedback from users.

Which reminds me .. I modified the help function for r2 so that it 
prints a url based on the naming scheme used for r3 functions

See the bottom of this page .. http://rebol.wik.is/Man

Might be useful if r2 docs could be given their own pages as well 
...

Carl, part of the goal of 2.7.8 is to replicate/reuse some of the 
R3 development infrastructure. Would it be possible to make a copy 
of the manual that you generated for R3 based on the Core 2.3 manual, 
for R2 this time? The same structure in an r2 directory minus the 
R3 changes would be best. Then we can change it for more recent R2 
changes, which shouldn't be as hard.