World: r3wp

but I hate losing things, it's a dilemma. :-)

I suppose we're assuming material ownership here. I've converted 
my material goods into goodwill in the past years and feel pretty 
good now that it can't be taken away from me :-)

that's a good move, Kaj

Will R3 Richtext support "hot links"? 

I mean links which are able to open files / links in other applications, 
or run a Rebol function when clicked?
Something like:

view [

 text [ "More info on " link http://www.rebol.org". Clickable " action 
 "text." [print "You clicked me!"]
]

yes

Now that's a clear answer, Thanks ;-)

not sure if it's going to be exactly like that though, but there 
will be hot areas for text, where you can do some kind of action.

This looks like the easiest way for me, but if there are better ones, 
I won't complain.

What do you think about the following addition to trace?

trace/log %file


which would write trace output to a file, so it can be reviewed later, 
sent by email, ...

echo %file  ?

anyone know if alias will be updated in REBOL3 to support paths? 
 I would like to do something such as:

alias 'find/any "myfind" 

Currently, the alpha that I have gives an error that says:

** Script error: alias does not allow path! for its word argument

No, nor should it. ALIAS is just for aliasing words to other words, 
primarily for internationalization. What you want is function wrappers, 
made easier with the APPLY native function in REBOL 3.

Yeah I do that now with stuff such as:

>> myfind: func [s v][find/any s v]
>> myfind "God is Great" "G?e"
== "Great"


I'll look into 'apply as I have been wanting to dig deeper into what 
REBOL3 is offering.

http://www.hmkdesign.dk/rebol/files/4b1cf5b6f8dbd87dfc957a59e16dcf4e-107.html

so now we can do a little bit of skinning :-)

Henrik, that is sick (meaning very good).

now things are moving. yesterday: select new skin after closing and 
opening window. today: switch between multiple skins on the fly in 
the same window. tomorrow: .... multiple skins simultaneously in 
the same window. :-)

Are rebol2 core programs going to work on r3?  Is another alpha of 
r3 about ready to be released?

the next R3 release will be unicode based. It will not be very compatible 
with R2 programs. A few scripts and one-liners will run.

Louis, you may have read about it,  but at one point there was even 
a discussion that R3 could not be called REBOL anymore, due to the 
numerous changes in the language caused by Unicode. It was decided 
not to change it.

so yes, there will be many compatibility issues, but it will definitely 
be for the better.

I remember that. I wrote r3 because it's easier.  :>)   Perhaps it 
should just be called 3.  That  is even easier to write.

Will we have another alpha soon?

as soon as the Unicode internal alphas are debugged, yes

I don't know if the next VID3 will make it in there. View does not 
yet support unicode, AFAIK.

Unicode in core is what I'm wanting to play with for now.  Thanks 
for responding.

you're welcome

REBOL 3 Datatypes and Typesets http://rebollovesjerry.blogspot.com/2008/03/blog-post_15.html

Nice!  You put together that blog nicely.  Your illustrations are 
excellent.

Thanks Paul, I am doing my best.

:)

Jerry,


I'm actually reading your blog to improve my Chinese. I guess it's 
a  'side-effects' .

And I am actually reading Carl's blog to improve my English. It is 
a side effect for sure.

>> probe first jerry-rebol-blog/readers
== [self  yeksoon]

I wrote a lengthy post, hoping to start a constructive discussion 
on how we could increase Rebol's popularity and enbiggen (I know 
it's not a real word, but I didn't want to use "increase" twice in 
one sentense :P) it's userbase. I hope this is something more people 
are thinking about now that Rebol 3 is imminent. Please have a look 
at http://www.reboltalk.com/forum/index.php/topic,1513.0.html


(I'm not trying to draw people away from Altme, but I think there's 
a need for a good Rebol forum too! :))

; a wee difference people probably noticed otr is documented
; R2
>> form first datatypes
=="end"
;R3
>> form first datatypes
== "end!"
; there is also a difference with get
; R3
>> t: 42
>> get  't
>> get :t
>> get t
; in R2 only the first is not an error

; In R3
>> get 42
== 42

Interesting. I wonder if that is intentional.

; In R3
>> a: context [b: 42]
== object!
>> get 'a/b
== 42
; In R2
>> a: context [b: 42]
>> get 'a/b

** Script Error: get expected word argument of type: any-word object 
none
** Where: halt-view
** Near: get 'a/b

from !Altme

Anyone that wants to take part in the testing that is required for 
REBOL3, drop a note here and we can synchronize what words are in 
need of a test case file.  Don't worry, there are many.   All we 
need to avoid is redundancy (well not really as more tests are infinitely 
 better than no tests.)   If you are keen to start, of the word dictionary; 
I'm in the A's.  :)  So if you start at D or E of F we probably won't 
collide.

Carl's preferred method are small focused tests.   and: [
    [equal? 1 and 1 1]

    [error? try [1.0 and 1.0]]   ; and is not expected to handle decimal!
]

etc... for the gament of 56 types by 68 actions that REBOL needs 
to handle for us.  The test case files usually focus on few actions 
with lots of various types. 


Note;  A lot of the tests can be based on R2.  The basic operators 
need to function at or beyond R2, so an R2 test that fails R3 is 
important.


I'll find out if the basic-test-engine.r script these case files 
are based on is for public consumption for those that want ot help 
out.  It really is a fair grunt of typing and thinking about edge 
cases (after all the baby step core cases)

Note; with the recent blog post; this basic-test-engine.r  may wel 
become part of the build-basic-test-engine-scripts.r reflective test 
generator.  As Carl points out; these are not better than human written. 
 They may cover more bases but still require a lot of attention to 
detail.   My interest in all this is mainly to keep Carl and RT away 
from the potato peeling work, freeing them for building new things. 
 :)

Are we going to see a 'currentpoint type of word for 'draw in R3? 
 something that will tell us where we are on the drawing surface?

This is for using draw to do a print preview.

where we are
 - do you mean in rich text?

Not necessarily.  If using AGG fonts, I want to know where I am so 
I can calculate how much space I have left on a line.

Can someone set me up an account for R3-Alpha?

graham, that is in rich text then. i want access to metrix, text 
bounding box, and so on. hopefully we'll get that eventually.

Reflection in REBOL 3.0 http://rebollovesjerry.blogspot.com/2008/03/reflection.html
, For English version of this article, hit the "Google Translate" 
Link in the page.

the first OSX version of R3 is released internally. it's currently 
only for unicode testing purposes, so there is no networking or graphics 
yet.

While feeling stupid giddy today, starting working on the Zen of 
REBOL.  But
>> import 'this
doesn't have the same Zen oomph as
>>> import this
maybe I'll leave it alone.