World: r3wp

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.

Then I hope final browser plug-in will be released too ... containing 
new security model too ... etc. :-) Henrik - the thing is, that I 
did not expect R3 to come "so late"  (whatever late means here :-), 
as it was expected to come in June as alpha :-) My idea was simple 
- new architecture means lots of changes, but also changes for good 
- lots of open sourced code, probably even new security scheme, open 
sourced plug-in etc. - so those skilled could help.

I did not expect it to come in a year. If so, then of course 2.7 
still makes a lots of sense ...

I'm of course expecting an R3 alpha to come out sooner than a year, 
but I wouldn't expect or rely on having a production level R3 within 
a year. If it comes sooner than that, then fine. :-)

Desktop Help window still says Copyright 2001 - 2005. Maybe it should 
be a global string in system?

and who is saying its delaying R3  ;-)  Carl is not alone working 
on it... maybe the ball is in someone else's hands ATM.

I think doing all these new builds is a good thing in at least one 
regard; if it gets RT into the habit of doing quick builds and releases, 
it will be much better when early R3 builds come out. That is, if 
it becomes habit, and the tools are there to make it easy to deploy 
new builds, we'll make much better progress testing R3.

I'm just afraid this behaviour will fade out just like every promising 
thing in the past (RT Q&A thursday and so on).

Carl needs more indians.

would those be little indians or big indians?

hahaha  we truely are geeks  ;-)

I've posted this bug in the comments to 2.7.4 OSX build, but I'll 
repeat it here, in case it's being seen here first. It's a colour 
problem, when transforming in the DRAW dialect. Code example:

i: make image! [100x100 255.0.0]
draw i [pen green line 10x10 90x90]

view layout [box effect [draw [image i transform 0 -30x-20 2 2 0x0 
image i]]]

Do you guys see the same result in this script:
do http://www.fys.ku.dk/~niclasen/rebol/test/transform.r

if you try it on Mac, Windows and Linux (or any other View version 
supporting the DRAW dialect). The circle, line and triangle should 
be lined up.

They are lined up here, circle then line then triangle.

ICarii, using what OS and what version of View?

In new 2.7.4 build for OSX:
>> do http://www.rebol.com/speed.r
** Script Error: query has no value
** Where: halt-view
** Near: querying: to logic! query


Is networking turned off or something? It seems, I can't run any 
script over the net with this latest 2.7 build on OSX. It works with 
old REBOL/View 1.3.2 Core 2.6.3 build.

the bug is known.

work around is do read <url>

ok

There seem to be a problem with read/binary. Maybe it's the same 
bug!?
read/binary http://www.rebol.com
returns empty.

haven't seen that one.

I've reported it in comments to 2.7.4 - OSX build.

Any report of text support in DRAW dialect on OSX? Is it known by 
Carl, that text is missing?

yes, freetype support is not integrated in the OSX build, I think

it never was

I really need that one for Canvas RPaint!

I would really like to see the window fix that is posted in the blog 
somewhere to make windows open properly at the front in OSX. I wonder 
if Carl has seen it?

Maybe you should report it as a comment in his blog! I think, he 
sees it then.

it was actually reported as a blog comment about 2 weeks ago

hmm, as I can see, RAMBO needs "moste requested fix" voting mechanism, 
or we start missuing blog for that :-)

I assume, looking at the order of top-down, that the next Bus-OS-Stop 
for beta releases will be linux? :-)

Btw... Calr spoke about a different compiler used for Windows version, 
what C compiler is that? , just currious...

Yes, I'm curious about that also.

Geomal: WinXP SP2 + view 2.7.4 the circle / line/ triange worked 
fine.

Geomal: WinXP SP2 + view 2.7.4  it worked

It's funny, how you spell my nick! :-D

Does line-join in the DRAW dialect works with Windows version? There 
seem to be a problem with OSX version:


view layout [box 200x100 effect [draw [pen red line-width 15 line-join 
round line 10x10 90x10 90x90 10x10 polygon 110x10 190x10 190x90]]]

I think, they both should be with rounded corners.

only second one is rounded - View 1.3.2 on W2K here ...

What about line-cap?


view layout [box effect [draw [pen red line-width 15 line-cap round 
line 10x10 90x10 90x90]]]