World: r3wp

Yup, it wouldn't surprise me if that would slow down your code.

Most important from my perspective:

- finish Extension enhancements
- finish Host enhancements
- move View to the enhanced command! interface

both to the state, that ppl can fully exploit those features.

- multitasking


... for Doc starting to port Cheyenne as mostly the only one REBOL 
killer product

- support porting efforts, get us to the mobile devices (ARM)


... as for Console and some other items - yes it sucks to not have 
them available, but I think that having strong infrastructure in-place 
is really important. But overall we need all the priority list implemented 
for R3 being worth calling a beta ...

... and someone damned fix the useless 'call function :-)

.... some ppl also requested enhanced /library interface being done 
as an extension. I started by donating 100USD, and now we are at 
someting like 400 USD ppl would pay for such a feature. So, what 
do we sponsor next? :-)

... but ... I think that A97 should lower the number of CC non-solved 
tickets. There is plenty of them added recently ...

A GUI table would be nice ...

nearly a month after Carl said he was going to work on a new alpha

>> chat
Fetching chat...
Cannot load chat from web.

Can't reach rebol.com and rebol.net ...

chat / com / net -- all working from where I am.

no problems here

Well, that was odd ... and I couldn't see any r3 updates either!

Hmm... still down for me after rebooting

So Carl .. hostkit ...

Yes?

that's what we feel you need to work on first!

concensus ...

Good to know.

Hostkit?  - we need some core bugs fixed.

those fixes started. Look at CC, first 6 bugs fixed, and I hope the 
list of fixes will be even bigger for next version ...

Good I hope so.

host kit will give a bit of parallel work done (Robert, Cyphre, BrianH 
and Maxim are all waiting), but I guess it's up to what motivates 
Carl currently.

If that is the case Henrik, then I'm all for hostkit to get built. 
 I just don't want to see us have to keep building hostkits for minor 
changes.  Better to make more changes to core and then less to hostkit 
unless the hostkit build will bring something new to the table as 
your implying.

host kit will fix remaining graphics issues, which Cyphre is already 
preparing. It will also help prepare for a better console for all 
platforms. Robert and Maxim has done various implementations (OpenGL, 
SQLite) and are doing general tests. BrianH, I can't remember what 
he's doing...

Fixed tickets now at 14 and counting :-) A good sign R3 is back in 
development, although over time we do have few tens of tickets to 
implement :-)

btw, I will start working on a public R3 /library extension as of 
next week, its now on my agenda.

are you claiming the bounty?

I guess I will.

I think it has to be delivered this year though ...

a good thing its only february then  ;-D

but seriously, I'll start work on this next week, I'll report on 
my progress.

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]