World: r3wp

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

Not my call - ask Carl.

The function I added to my todo list yesterday is done. Two lines 
of code, though they are tricky :)

Brian, are you sure that R3 handles case-insensitiveness in Unicode 
text better than R2 with UTF-8?

I remember Carl being againist adding language-specific tables into 
R3.

Where do we find information on the new VID of R3?

http://www.rebol.net/wiki/R3_GUI

Thanks Henrik

I sure hope we are going to redefine many of the current panels  
such as alert.  Alert looks horrible.

Alert shouldn't present a scroller unless their is scrollable text. 
 Additionally the text on alert should be centered along with the 
button.  I know that alert is just preliminary for now.

Ah, I would not worry about that. Actually not sooner, than more 
important things get into the system. There are still some concepts 
missing ...

I don't know much about the progress of R3 GUI yet.

I like the fact that it was going to take on a CSS type of method.

The UI is _very_ preliminary.

The latest shots of the UI can be seen at http://rebol.hmkdesign.dk/files/r3/gui/
but it is still changing and far from done.

The layout engine still performs rather poorly so if elements appear 
off alignment, it's because the layout engine doesn't do this well 
yet. Don't worry, I want pixel precise alignment.

Henrik, do you need help?  Maybe I can get involved - if interested 
- just get me up to speed on it.

thanks, I don't need help right now.

Excellent Henrik!

R3 chat system user account creation reenabled.

Gabriele, I know that R3 handles case-insensitiveness of Latin1 characters 
in Unicode text better than R2 with UTF-8, but beyond that I don't 
know. There is still some stuff to do relative to Unicode. The implications 
of Unicode support on the rest of the system are mostly implemented 
though, with the glaring exception of PARSE.

Are there any good tutorials on using asyncronous networking in R3? 
 That changed from R2, right?

Good tutorials: Not yet. Turorials: Sort of. Changed: Drastically.

TimW, you can find some information on DocBase, notably here: http://www.rebol.net/wiki/Ports

Is there implementation information available for students?

Thanks.  The port information is pretty good.

alpha 37 is now available for OSX.

Brian: if it's just latin1, does it really change things? it won't 
always work anyway. but, there's plenty of code to convert utf-8 
to latin1 in R2, so why not just doing that if it's really important 
to have case insensitive accented character in the user names?

I'm wondering now if r3 eats a lot of CPU when running the upgrade 
procedure under linux or just by using READ with HTTP. It does so 
under OSX.

Gabriele, Unicode isn't done, so I don't understand this: "does it 
really change things?". I was just answering your question about 
R3. Whether R2 can handle case insensitivity of UTF-8 when third-party 
libraries are added is another issue.


I can't say what Carl's priorities are beyond where he had me mark 
CureCode tickets as urgent, so I can't say when or if Unicode will 
be "finished". User account creation is reenabled, so the whole reason 
this conversation started is moot now.

I noticed the GUI demo in R3 is very buggy.  Sometimes it just eats 
CPU and does nothing.

Paul, have you found patterns for the slowness?