World: r3wp

well, there's only the one protocol included so far .. if you want 
your own, you have the option of including, or loading afterwards

Thanks Ladislav for confirming the lack of write access to the rebol.com 
wiki

Chris, how to include your own protocols http://jira.rebolsource.net:8080/browse/REBOLKIT-2

I don't know how much of a pain this would be, but I would like to 
consider overloading of words such as empty?


It would like to see if there were an 'empty? actor if noun is an 
object ...and use that.

in the same way that open, close etc are port actors

I presume that is something that needs to changed in the r3lib.dll 
and is not possible from the hostkit

Hmm... I guess I could just redefine 'empty ...

Afterall is it really necessary for me to write thousands of times 

empty? vidfield/text

when the language should allow me to write

empty? vidfield

I can confirm that I am able to edit pages in the rebol.com wiki.

Ladislav should also be able to edit them.

Message #6921 explains.

Graham: if you really have to write empty? vidfield/text thousands 
of times, it would probably be worth adding it as a keyboard shortcut 
in your text editor.

Message #6921 on R3 chat.

Well, Gregg and I are only 50

Ladislav has rank 70 .. and so either Carl reinstituted the edit 
facility just after ladislav tested it .. or it's broken

Peter .. vidfield was meant to mean any object which has a field 
attribute

text attribute

If I remember correctly, I was able to edit even when I had rank 
50. But, currently, notbody is able to edit, as far as I know.

Peter says he can edit

I'm able to edit as well

aha, hmm, I am still unable to log in, strange

Ladislav from the browser popup login or the web page form login?

Browser popup login

that is a public user/pass combination

editor:reb.ol

how am I supposed to log in as Ladislav, then?

there are two login forms. after the browser popup, a web form appears 
here asking you to log in with your R3 chat credentials

hmm, where did you find that info?

first I checked message 6921 in r3 chat. then I tried it in the browser. 
it worked.

aha, thanks

I am probably a bot, as it looks

I always thought that :-)

Am just getting started with Rebol; haven't spent some development 
time with TCL. Would like some direction on where to start: V2 or 
V3 (with the understanding that V3 has yet to achieve commerical 
level release).


Simply looking for the best way to get my head around it without 
the need to unlearn a whole bunch.

Rebol2 ... R3 is alpha

thanks..

The fundamentals will be the same, but some details will change.

I used to be able to edit the pages .. so looks like the limit was 
raised to above my rating.  Phew .. less work for me

Is there a way to open the Word Browser without the viewtop?

Have you looked at the source?

Yes. I want to browse the words really, and look at the examples 
too. Thanks.

Is there any rebol library that does continuations?

Are there any plans to have rebol run on moble platforms such as 
android?

android: should be possible, as it allows native C libraries, but 
not sure about GUI stuff.

rebol release 1 does continuations

If you can find it ... was released over 10 years agos

Answering to Petr's R3-GUI question, here, as it's not GUI related.

I don't know how many work it requires to get TASK implemented. So 
no idea if this is next.

IMO focus should be now on bug-fixing and closing open tickets. There 
is still some smaller things to do on the AGG side. And than get 
a V1.0 out of the door. Because I don't see any cause to not make 
an offical V1 release of R3 anymore. It's mostly ready for prime 
time.

I posted in R3-GUI as I consider it being "your group" :-) Well, 
1-2 month bug-fixing could be usefull, but I know ppl - noone will 
consider R3 ready, unless the basic infrastructure is in-place. And 
not having tasking/IPC is one big handicap - e.g. Doc will surely 
not start the Cheyenne transition (if he will port it at all) ..... 
that's how I feel about it. 'Call needs to be implemented too, or 
R3 stays in isolation for system related scripting. Your aproach 
limits R3 to only GUI realated usage ... if we are rushing to have 
R3 1.0 stamp on it, then priorities, or simply target feature-set 
should be discussed, and set ....

until R3 supports threads, I don't think we should consider it beta. 
 this is too big a hole in 2010 for it to be sidestepped and ignored.

adding threads *could* have far reaching implications in many little 
areas of R3.  I woudn't want to start a big project and then realize 
that its broken after a thread enabled release.