World: r3wp

maybe Carl just likes oddities like this and makes them happen  ;-)

Anyone else have issues with this script? -- http://www.ross-gill.com/r/boston-cam.r

** Script Error: query has no value
** Near: querying: to logic! query
>>

got the same message!

The script itself seems quite benign.

it came very immediately. seems to come even before attempting to 
load the script from server

same with LOAD on the script

if I READ it first and then LOAD it, no problems

It seems to be in the HTTP protocol.

this is the faulty line:

img: load http://images.earthcam.com/ec_metros/massachusetts/boston/pru.jpg

same with any URL actually.

strange, using read/binary returns an empty string!

should it be reported? It doesn't seem all that important :-)

(empty binary!, sorry)

LOL

funny it didn't come up earlier

true!

REBOL/View 2.7.2.3.1 25-Nov-2006

same here

me too

Also, in the editor window, hitting the  'home' key produces a null 
character, and 'end' does nothing.

Nor Page Up/Down.

I guess it's early days :)

I'm putting the DO/LOAD thing on the blog

done

OSX version is out

Nice! I'll start doing some tests with View and OSX in the next days 
hopefully.

yet another build, this time with timers

my rotation zoomer finally works under OSX :-) A dream come true. 
but the colors are screwed!

do the timers exist in the win2.7.4 build or only the osx build? 
 couldn't seem to find any relevant ? timer* info..

or by timers is carl just referring to the VID based rate/time events 
rather than a Core accessible timer?

face/rate. afaik that didn't work in some osx builds.

will be the rate finally increased?

timers work alright. several demos in the Public/Demos directory 
use timers

Oldes? do you mean under Windows? That would be great.

Henrik: I know, one of these is mine...but there was(is) inbuilt 
limit how fast the rate can be.

looks like the windows version is at 2.7.4 now

still has the DO/LOAD bug...

I think we started really strange route. Now we will have nice toy 
to play with, spend our time, introducing new bugs, whereas 3.0 slips 
further in the schedule, as RT has to correct bugs present with 2.7 
and its changes ...

pekr, did you read the latest 3.0 blog entry?

yes, and?

that blog was probably provoked by my earlier comment in the blog 
... at least Carl confirmed, that 2.7 will see only mostly those 
changes, which could be used as a codebase for 3.0 too ...

I'm not sure what you mean by slipping. I wouldn't expect 3.0 to 
be usable for production work within a year anyway (I think I mentioned 
that before)

2.7 consumes RTs time probably anyway, not sure it is worth it, because 
as we can see, we are introducing new inconsistencies/bugs

so holding off 3.0 for a few weeks to get 2.7 out, gets my approval, 
particularly if some of my bugs are fixed :-)

well, it's not done yet so those inconsistencies might be ironed 
out.

I feel the other way around - produce 2.7 instead of 2.6.3 bugfix 
release, because posponning of R3 is already planned ...

I'm just glad that there will be updates to the 2.x branch

R3 can come when it's finished :-)

I am very happy with some of the bug fixes. Anyway, it's good the 
new compiler is being tested out.