World: r3wp

Does the new draw have a concept of current position on the canvas?

Which is also accessible to the user ...

only within the shape commands as per R2

pity

it would make it easier to do typesetting if we had a currentposition 
command as in postscrip

you can always store it manually i guess and process the draw block..

could probably make a type setting dialect around that. many new 
dialects are possible.

there is currently a dialect extension to make draw drawings automatically 
resizable.

graham, do you know if there is such a dialect for R2?

Nope.

I see that Apple plan on releasing an SDK for the iPhone in Feb ... 
let's hope R3 has some way of being ported to this platform.

http://www.apple.com/hotnews/

porting to the iphone/ipod is one thing i would try :) (my brother 
has an ipod touch). but, i'm not sure apple would allow a programming 
language in...

It'll be interesting to see what exactly they allow. Not being specific 
enough in this area worries me a bit, so we can't tell whether it's 
going to be completely free, but has to be approved by Apple, or 
if only the big boys with the big money are allowed to play.

Are there going to be any interrupts that are based on absolute times?

Or, are we going to have to run our own timers and count the time 
ourselves?

I have the need for long running server applications to do house 
keeping at night ...

Generic timer events will come, since this is needed for animation 
in VID3. I think you can use them for that, but Gabriele knows more.

I could post my little cron dialect for R2. It's been doing backups 
for months without trouble.

I used Bo's cron script some time ago and that seemed to work ... 
I'm just interested in knowing how the timer events will work.

Forinstance, my Cerebrus anti-spam script regularly ran out of resources 
and crashed after a week or so, so I was wanting to reboot it once 
a day as it were to prevent that happening.

I'd also like my emr script to start processing various tasks after 
mid-night - like sending out email reminders to patients etc.

I have the same need Graham, so I'll push for good built-in support 
too.

a bit more progress on DevBase today to allow uploading of many files 
in bulk. still a few more bits to do. DevBase will hold the code 
to itself, so we can help updating it along the way.

there are now a few extra useful mezzanines that haven't been added 
to R3 officially. perhaps they will go in there as well.

356 bug reports

http://hmkdesign.dk/rebol/files/2e7e2c962a9c8d14e93919f5b007e5f6-85.html
<-- a small blurp about DocBase

more news on DevBase folks ?

Carl is asking questions among developers privately on some final 
issues.

I really don't undersant why there is so many people crying... I 
have Uniserve runing for several months without problems, parsing 
about 50 pages two times per day to provide culture informations 
in the city I live, I use Rebol to build PHP sites, Flash apps, as 
a proxy server as, a clasic system console and for so many every 
day scripting and I really cannot imagine I would use something else 
than Rebol for such a job. And if you still think that you cannot 
do anything in R2 and have to wait for R3 to start, you can take 
a look for other technology. With computer languages it's same like 
with normal languages - the more languages you know, the better you 
are.

Oldes - to whom are you replying to? :-)

I think that noone is waiting. We simply got to the stage of nearly 
extinction of entire REBOL humankind :-)

Our community was always passionate, but not big enough. Each nice 
and good project was mostly a one-man show. Then - those more skilled 
rebollers got rebol related jobs. That is very nice, but also has 
some side-effects. Those ppl nearly vanished from public radar. Where's 
Doc, Cyphre, Ladislav, Gabriele, Voker, Anton? Well, Gabriele could 
be probably excluded from the group, as he is active even on ml.

And yes, awaiting new release has always the same effect. Ppl are 
holding breath, as they think new thingy is about to be released 
next day :-) Once there is new release however, I believe ppl will 
come from their holes and we will hopefully see nice activity once 
again.

If anything was to be communicated more than my suggestion to keep 
quiet, I would have liked to see very, very conservative schedules. 
Carl is always overly optimistic which is causing all this ruccus 
and damages the believability of RT.

I just had a though this morning about just how different R3 is going 
to be syntactically from R1-R2. For those of you using it, is it 
grossly different? I think I should just continue to study the current 
Rebol since I still have plenty of jobs to do, however, I'm still 
curious what it looks like myself. Personally I doubt if it can be 
so new that what I've learned so far will not be useful but I'd like 
to hear it from those who have real-world experience.

No the syntax is basically the same. There are no radical changes 
to syntax, but in the details, some things behave a little differently, 
some things are allowed and some are forbidden, but you only notice 
that after a while. If you use R2, you'll be able to use R3 immediately. 
The differences lies in the behavior of functions, dialects, etc.

Excellent Henrik. That's what I needed to know. Most of my issues 
are not that R2 doesn't do something or another; they have to do 
with knowledge and experience. Thanks.

Let me see if I can find an interesting mezzanine to post here...

move: func [
    "Move a value or span of values in a series."
    source [series!] "Source series"
    offset [integer!] "Offset to move by, or index to move to"
    /part "Move part of a series"
    length [integer!] "The length of the part to move"

    /skip "Treat the series as records of fixed size" ;; SKIP redefined
    size [integer!] "Size of each record"

    /to "Move to an index relative to the head of the series" ;; TO redefined
] [
    unless length [length: 1]
    if skip [
        offset: offset * size: max 1 size
        length: length * size
    ]
    part: take/part source length
    insert either to [at head source offset] [
        system/words/skip source offset
    ] part
]

not much difference, except for a new TAKE function. but there shouldn't 
be any trouble reading it for R2 users.

That's what I'm talking about...

For me, the 'unless'  was new but I see that it was just what I was 
saying; I need to learn R2 better, because there it did in fact  
exist in R2. Interesting, thanks.

just reading through the built in mezzanines in R2 can be very helpful.

That one is not in the dictionary page. What's your best  method 
to view those?

I usually use the word browser. It holds the newest and the most 
information.

but it did take a while for me to discover 'unless. There has also 
been debate whether it's needed. It makes code a very tiny bit faster. 
That's all.

Ah, I forgot about that one. Thanks.

I think this is also new:

>>>> head foreach [a b d: c] a [change d 'hello]
== [1 2 hello 4 5 hello]

damn... sorry

>> a: [1 2 3 4 5 6]
>> head foreach [a b d: c] a [change d 'hello]
== [1 2 hello 4 5 hello]