World: r3wp

That is 2 bugs rolled into one:


1. The script used to be called main.r, which is what it is called 
there.

2. The R3 GUI indicates an error in the dialect, when actually the 
file can't be read.

I just read about 'gather function and would like to ask about its 
area of usage? In the past, in FoxPro DB days, there was common method 
to get all for related data, via function called gather, and the 
reverse was to set a form from an array, via scatter fucntion.  I 
think that if gather takes just one field from objects, we might 
use good name for some limited functionality, whereas it could be 
good name for GUI forms (panels) and gathering of info from all objects 
in one run?

We don't really need scatter/gather for the R3 GUI, as it already 
works with SET-FACE and GET-FACE using panels.

GATHER was your request, Henrik, specificly for use in the R3 GUI. 
Are you withdrawing the request? I need to know soon.

BrianH, no, absolutely not. :-) Pekr asked, as far as I can tell, 
that he wanted to use GATHER for a specific form data collecting 
function and we shouldn't need that.

It should be enough to manipulate forms using SET-FACE and GET-FACE.

What is the gather function?

Good, because Carl has shifted his priorities for now to helping 
me by fixing errors that are blocking me. He asked me to change all 
of my worst pet peeves in CureCode to urgent last night, and he accepted 
almost all of my recent work in DevBase. GATHER hasn't made it in 
yet though - I am explaining its need to him now.

Paul, see rebdev message #1804

going now.

Ok, I see now.  It looks very specialized.

Specialized is good. Let the programmer decide what they want to 
do at programming time, not the interpreter at runtime.

Specialized functions are faster, simpler to write and easier to 
understand.

I proposed it, because I use it in many places to collapse chunks 
of 20-30 lines of code into one line and it works well in use as 
part of bigger functions.

Cool guys.

if we have gather, we might need scatter (the opposite). But also 
- getting just one field is unnecessary limitation imo :-)

I can imagine getting multiple fields. I can even imagine using 'extract 
to get block of result values from the block of objects. Hmm, I can 
imagine many things :-)

You may be right about an opposite to GATHER.


Getting multiple fields will complicate GATHER. What is the output 
format going to be? In the form it is now, it's a good allround way 
to get one set of values from a block of objects. Use GATHER multiple 
times to get different values. Then use a different function afterwards 
to manipulate the blocks you have made with GATHER.

Typing accented strings is ok in the command window,  but raises 
an error when read from a file:   a: "terminé"  syntax error invalid 
string {"terminé"}. Is there a new  write or read option for text 
files with accented letters ?

R3 assume text file are UTF-8 encoded. Probably yours is ANSI or 
something else

It's ok. It was not the case with R2.

Alpha 37 released.

coming fast a furious

It's BrianH's fixes that are going in. There are many of them. :-)

There are some things I can't understand in the demo : when you click 
on source, you don't get the full source but just a part of it.

Also, I've tried launching this script (from Dragger demo) :

REBOL [ ]

load-gui

view [

doc {
^-^-^-===Drag the boxes

^-^-^-Blue boxes are unbounded.

^-^-^-Red boxes are parent panel bounded.
^-^-}
d1: free-drag
d4: lock-drag red
panel 0 80.200.80.80 [
    d2: free-drag
    d3: lock-drag red
]
]

...and got a parse error : why ?

there is no free-drag or lock-drag style. they are substyles created 
in the demo.

Henrik: so what's the point having a 'source' button if these styles 
are hidden ?

that makes sense within the demo.

Don't you think a 'full source' might be better, it's confusing.

they are not "hidden". they are just not part of the standard style 
list. and you can't create free-drag or lock-drag items in your layout 
without creating a style.

Try this:

write %/c/demo.r read http://www.rebol.com/r3/demo.r

This lets you study the code for the demo.

I've understood this; I was just wondering why

including the free-drag and lock-drag style.

the style could be extreme complex and consist of other substyles. 
it doesn't make sense to have that code inside the layout.

Henrik : thanks; that seems really complicated code for me :)

have you studied how the R3 GUI works?

there is a strong separation between the layout and the style code.

I'm just starting reading the wiki.

The error that has occurred above is that the "demo-let" that kib2 
looked at is not properly documented. Its script header should declare 
what its dependencies are and in what environment it should be run. 
This is a constant source of time-wasting for everyone, as an undocumented 
script apparently advertises that it has no dependencies and can 
run on its own. So all new-comers to the script will try it in the 
console themselves and see it doesn't work. Now the wondering begins: 
"is it supposed to be working or is it still in development?" etc. 
It's not kib2's fault for not having studied how the R3 GUI works.

Let me just temper that - it just shows that the script is not complete, 
and this is understandable in a system which is in flux.

Haven't they fixed the unicode issue to allow new chat users?

Actually size of the image does not seem to be the prob as this works: 

SQL reduce [{insert into images values (?,?,?,?,?,?,?,?)} "img/1" 
"img/2" "img/3" "img/4" "img/5" pic "img/7" "img/8"]
where pic is a large 4000x3000 full color photo.
I get no error.

But if I loop 50 and insert the above data 50 times I get an error???

soory wrong Group

I went through the CureCode tickets and marked the ones fixed in 
alphas 35 through 37, that weren't already marked. You can see the 
changes in the Change Log section of CureCode, and some fixes are 
summarized on the R3 Releases page too.

Josh, the issue is that the chat server is running on R2 right now 
for reliability. R2 can't handle Unicode except as binary, and certainly 
can't do case-sensitive searches for user names in Unicode. The web 
client for mobile is even worse, and is also R2 since R3 can't handle 
CGI yet.


Right now we are focusing on getting R3 stable enough to use on the 
server-side. Hence the changes in the newest alphas.

If you think there were a lot of changes in the last alpha, you should 
see the next one. I have fixed most of the bugs in LOAD and DO :)

My next project is the begin bugs - there are many - I am just waiting 
on an info request.

R2-Forward has been updated to match alpha 37 as well, though that 
meant adding one more function to the todo list (and 5 more to the 
done list, and 6 more to the improved list) :)

Sorry, make that 18 more to the improved list - I forgot to include 
last night as well :)

I had another request to join R3 discussion. Couldn't some interim 
solution being made, e.g. refusing names with special chars? Returning 
error would be enough for ppl to know they ought to choose different 
name, no? Because - recent solution was meant to be interim one, 
but it typically became permanent one, without any resolution of 
when actually it gets fixed ...