World: r4wp

Perhaps some discussion about forming a Red foundation would be helpful 
to organize anticipated future actitivies involving community relations 
or other activities that will keep Doc and other core developers 
from focusing on code.

Yes, the hope is that we can rally support to do the things, like 
web sites, forum moderation, etc. so core developers (i.e. Doc) can 
focus on development.

Thanks for thinking about me, Nick. I'll refrain from asking for 
donations until Doc is in a good position, then I'll set up a website 
for the bindings to give sponsors a chance to influence my priorities

Thanks for your work and vision Kaj.  It's so appreciated!

Thanks

Arnold, you want me to give a list of things that you would need 
to get a Raspberry going?

Doc, we're just back from Hardware Freedom Day. My talk turned out 
mostly about the Raspberry, because little Red was working. I haven't 
looked into the causes yet. When I've caught up on sleep I'll start 
sending in bug reports

It's quite possible that it's callbacks, but I'm not sure yet

http://www.youtube.com/watch?v=susYvYoUnUQ

Bas: it says "Video is private", so it can't be seen.

Nick: thank you very much for this initiative, it certainly helps 
me keep focused on Red and not have to worry about how to pay my 
bills next month! I hope others will continue to donate, so Nick 
won't need to take all the burden on his shoulders.

Kaj: I noticed Unicode characters rendering does not work on my Linux 
ARM running on QEMU. I'm not sure yet why, I'll investigate that 
in the next days.

The video is now accessible

 after running around all week buying additional needed equipment.

 that sounds like a shopping list comes in handy when purchasing a 
 RaspberryPi, there are some surprises like needing a VGA monitor 
 where the standard videoout on the Pi is HDMI.

OK, just checking, not sure what you meant

You don't need a VGA monitor, to the contrary, it's hard to get a 
VGA monitor connected, you need an HDMI or DVI monitor

I read your post the other way around.

Doc, on BodhiLinux I had full fonts when opening hello.red in an 
editor, including Chinese

Still surprised that you still needed to buy additional stuff to 
get it working.

Weren't you running bare Debian? That would probably expect you to 
install and configure more yourself

Arnold, the Raspberry is just a motherboard, you'd need a power supply 
and cables at the least :-)

I know LOL!

Kaj: sorry, I wasn't accurate enough, I was referring to hello.red 
output when compiled.

(when run)

The adapter cable I talked about from HDMI to VGA turned out not 
to work. It probably works in the other direction, although I thought 
that wouldn't be possible

Doc, I thought that couldn't be because I can't run any Red code 
on ARM. hello.red crashes hard for me, even taking the terminal program 
down

Does it crash on your RPi?

Yes

(I haven't yet had the chance to test on mine)

Are you running wheezy on it?

Yes, are you running an ARMEL or an ARMHF architecture?

I'm unsure, but as we do support hardware floating points, it should 
be ARMHF I guess.

We support the hardfp ABI. IIRC, Andreas reported that it was working 
on softfp ABI too, but I don't remember exactly, so better wait for 
him to give the right answer.

Anyway, we planned to support more ARM ABI in order to spread on 
more platforms.

Better spread on one platform first :-)

All I can run is empty.reds, Fibonacci, PeterPaint and SQLite

And hello.reds, but not hello.red

I'll look into that as soon as my RPi is set up properly.

Got Mandelbrot to work

Good work.

I see update of docs typo in red-system-specs.txt saw in this file 
that mat operators including % are supported yet in BNF on line 1076 
it is not mentioned.

Also saw a typo, I read the document further tomorrow and note all 
typos I see.

Maths op missing in BNF rules: good catch. You can add them and submit 
a pull request on the master branch.

I will try that, I once did a pull request but it pulling doesn't 
make sense in my mind. I think it means the Github must be pulling. 
I will try again (with possible other improvements. If I am not succesful, 
I will put a file with my improvements up somewhere. Now to work 
(my job waits)

Well I changed some text in this file, I changed it online in a black 
background box where I could not see my cursor nor the arrow pointer, 
so it sucked :( 

I thought it would be possible to edit the file offline but that 
is something to find out how to do next time ;)

Now I added a comment and it says I want to commit 182 changes into 
the master branch, which is not what I want, but Github says I want 
that. Including my comments it could be I typed in total 182 characters 
including the ones I deleted (?) but the 182 are the commits from 
the 0.3.0 branche I think. 

Me and my friend Github >:|

Going to need to shorten that phrase cause I will need it often: 
mamfg!

:-) They are plenty of git / github tutorials online, you might want 
to go through one of them. Having basic git understanding is required 
if you want to contribute code to Red, otherwise, it would take us 
much more time to review and accept it. Anyway, I agree that git 
is unnecessarily complicated, even Linus says it's not for everyone. 
We'll see how Red can solve that once it is mature enough.

Agreed did one today but it was for git not for github. As github 
doesn't support OSX10.5 with her github for mac program I am temp 
stuck. maybe a REBOL script can take over the git commandlines for 
me. I go and try that to take me over the githurdle.

I can't accept your pull request, it's a complete merge of different 
branches (you're probably mixed up several branches, or you haven't 
rebase before submitting the pull request). You need to submit only 
the changes you did. For that, you need to have a clean codebase 
and up-to-date wrt the branch you're modifying.

Looking at the 182 commits you've submitted, it seems, you haven't 
checkout'd to master branch before making the change, so you are 
submitting the whole v0.3.0 branch to merge with master. You need 
to check carefully on which branch you are before doing any change.