World: r3wp

The idea here is not build a prototype, but a "end-user" product.

Chinese new year  ... starts in 9 days ... you don't have much time

Maxim: great!

haha

I was going to have a look at the R3 gui sources but they're all 
flattened..  Is there a pretty print for r3?

A script can do the job, I forgot where I'd seen it

http://www.rebol.org/view-script.r?script=clean-script.r

Doesn't work on R3 source

Actually it doesn't work well on R2 source either!

ah...

chokes on 

obj/:word

which is new syntax inroduced after that script was written

Is it week in year day in year function available in rebol? I've 
found that very messy standards for week in year calculation. There 
are minimally 3 views to what first week in year really is, combined 
with the first day in week rule. (in different words there must be 
two switches to function would be universaly useable) funny but sometimes 
necessary.

There is /weekday

>> scalar!                          

== make typeset! [integer! decimal! percent! money! char! pair! tuple! 
time!]
>> to integer! 0
== 0
>> to decimal! 0 
== 0.0
>> to percent! 0 
== 0%
>> to money! 0   
== $0
>> to char! 0  
== #"^@"
>> to pair! 0 
== 0x0
>> to tuple! 0
** Script error: cannot MAKE/TO tuple! from: 0
** Where: to
** Near: to tuple! 0
>> to time! 0  
== 0:00

Should tuple! default to 0.0.0 ?

tuple 0 error:  It is consistent with R2 -- but that only does not 
make it right (see CC #666)

>> power 2 2
== 4.0

Shouldn't this return integer! where possible?

>> to-integer copy/part tmp: to-string  power 2 2 find tmp "."
== 4

:-)

Or:

	to integer! power 2 2

That produces an error for higher values of 2.

This should produce an int when it can, and a dec when it can't, 
though only for positive values of 2:

   pow: func [a b /local res][attempt [res: to-integer res: power a 
   b] res]

is Android and the iPhone platforms under consideration?

yes, it is in priority plan, to get build for ARM and possibly other 
platforms ...

hmm... is it possible to remove messages in R3 chat? I saw Ladislav 
posting this header:


> 6843   Re #6839: round/half-ceiling -$100.5000000    26 ladislav 
18m ago  

But now it's gone from my chat view.

Manual says remove is possible....Never tried it myself:

   http://www.rebol.net/wiki/RebDev_Quick_Start#Move_or_Remove_Messages

Graham:R3/Mezzanines>> 6843
#6843: skip from ladislav 3h ago:

Ashley, scalar! means that the type can be operated on by *, /, + 
and -, not that it can be converted from integer.

Phone platforms are in the priority plan, but that will likely have 
to be limited to platforms where REBOL will be allowed. So development 
for the iPhone would be possible, but running REBOL *on* the iPhone 
or iPad isn't allowed by Apple's rules. Other phone platforms would 
be fine though - they have no such restrictions.

>> length? read http://idisk.me.com/dobeash/Public/rebdb.r
== 12771
>> size? http://idisk.me.com/dobeash/Public/rebdb.r
== none
>> help size?
USAGE:
	SIZE? target

DESCRIPTION:
	Returns the size of a file.
	SIZE? is a function value.

ARGUMENTS:
	target (file! url!)

Good to know, I'll put it on the list for the http scheme.

>> result: write http://idisk.me.com/dobeash/Public/rebdb.r[head]
== [%/dobeash/Public/rebdb.r 12771 none]

How on earth did you come up with that!?

I've written a few schemes :)

so this should work inside the http scheme

		size?: funct [
			port [port!]
		][
			tmp: write port [ head ]
			pick tmp 2
		]

or just 

second write port [ head ]

>> #{0140} = #{0140}
== true
>> #{0141} = #{0141}
== true
>> #{0141} = #{0161} 
== true
>> #{0141} == #{0161}
== false

Oh, that's bad: EQUAL? is doing case-insensitive comparison for binaries. 
That's a bug - I'll report it.

Is this the same problem?

>> #{0159} > #{0158}
== true
>> #{0159} > #{015E} 
== true

Yup. Already reported.

So, it looks like Carl is in bug fixing mode  ....

Oh yeah, and it is much appreciated :)

The concensus was that the host kit should be the priority ...

perhaps the fixes are required for the host kit.

That's so nice of you Henrik :)

anyhow A97 is clearly marked before the hostkit in the priorities 
list.

He's still sing the queue-with-timeouts priority model. The hostkit 
got put on hold while some of the timed out items were handled: R2, 
the web site, and now bug fixes.

Well, the only bug that bugs me is http://www.curecode.org/rebol3/ticket.rsp?id=682&cursor=56

Agreed, that's a priority for me too (though not as high as TO or 
THRU charset not working).

I think using append/insert on binary should be a high priority.

Well, I think that problems with workarounds get a lower priority 
than problems without workarounds, but I agree.

The workaround for the binary issue is nested joins for me.

the main workround is to use R2