World: r3wp

yep. in fact ever since Apple starting selling "high-end" apps they've 
done everything in their power to hurt their most direct software 
competitor.

1ooo cows do not work? Time to rewrite cow as R3GUI style!

If everything goes well we could use the OpenGL on OSX to render 
R3 graphics so my guess is R3 performance shouldn't be so bad.

yes, it does not work. Cyphre's gfx test works though. I am interested 
in Amiga figures :-)

Pekr, I'll publish r3.exe with the opengl rendering by monday. I 
wonder how much fater will be the benchmark script on your machine 
:)

fater=faster ;)

BTW last night I added freetype font rendering to the hostkit so 
ssolie will be able to try render text on AmigaOS4.

yes, my machine is 4 years old Dell notebook, and the test was as 
fast as your OpenGL accelerated one. You really have to have an old 
machine, no? :-)

Freetype? Is that for Linux and other, non-windows OSes?

yes, thats more than 8 years old thinkpad notebook..I prefer to test 
performance on olde machines..it shows the bottlencks much easier 
than on some hi-end supercomputers.

Feetype: by this addition in the hostkit we can theoretically get 
font rendering on Amiga, Linux, OSX etc. For OSX it would be great 
to switch to native fonts(Quartz?) later though.

BTW It's a shame that AmigaOS will have View sooner than Linux! It 
looks like the Rebol comunity have no Linux 'power programmers', 
or noone needs View on Linux?

None serious Linux programmers would touch any non-GPL stuff ;)

yes, it is a pity. But mabe even more so - maybe many ppl would welcome 
View or at least Core on mobile OSes. Android and Wm6.5 are the biggest 
candidates imo ... (dunno what can be done about the iPhone)

Rebolek - really? Then why Linux folks are happy about some binary, 
non GPL drivers, etc.? :-)

Bolek: ah, you're right..I forgot about  'The Linux geek Ten Commandments' 
;-)

Maxim: "but is it really need since we have the internal OSX pdf 
reader." - I would like to say that, but unfortunately I have had 
to process some absolutely nasty PDF forms that would not work in 
anything, but Adobe Reader, due to various custom elements, encryption, 
etc. Where were they from? Our dear government, of course.

I've yet to meey any Linux programmers who have installed an open 
source BIOS.....So many of them have limits on where they draw the 
closed/open line for their software development stack. 

They and I just disgree on the best place to draw that line to create 
an appropriate marketing model for various projects (including REBOL)

meey ==> meet

Let them die in peace :-)

henrik:R3/Lobby>> help
sh: xdg-open: command not found
sh: x-www-browser: command not found
** Access error: external process failed: "Undefined error: 0"

** Where: browse parse try either either forever command-loop make 
context do catch either either -apply- do try chat
** Near: browse help-url

Seems these are broken in A110 for OSX.

Oldes - Carl seems to propose to export your requested functionality, 
if needed, so that it does not break with next internal changes. 
So please react accordingly in R3 chat = make your wish clear :-)

Henrik, opening a browser is not really implemented in the OS X port. 
The methods that are tried are Linux conventions

Kaj, it used to work, so I'm considering it a bug.

Ah, I didn't know that

>> browse http://www.google.com
sh: xdg-open: command not found
sh: x-www-browser: command not found
** Access error: external process failed: "Undefined error: 0"
** Where: browse
** Near: browse http://www.google.com

>> browse http://www.google.com
== none

A97 pops up a browser window.

Must have gotten mixed up with the general POSIX port, then

possibly.

Do you have another explanation?

since browse is native, I can't see what the problem else might be. 
no visible source change.

Well, the host kit has been heavily rearranged

You can see the native source code there

I'm trying to run the hello world example at http://www.rebol.com/r3/docs/gui/guide.html

Here is what happens when I try load-gui:
>> load-gui
i
Fetching GUI...
GUI Version: 0.2.1

(Developer test GUI theme)

** Script error: expected command! not font

 ** Where: size-text font-char-size? make make-text-style parse fontize 
 do do either load-gui

** Near: size-text gob

Is this a host-kit issue or ?

this is old Carl's gui. I am not sure it works, most probably it 
does not. Go into R3 GUI group here, and find some of Henrik's links 
and download RM Assets' GUI

http://94.145.78.91/files/r3/gui/r3-gui.r3

Yeah .. old GUI code

Thanks guys. GUI seems to function now after changing the fonts. 
I left a comment in REBOL3 GUI. Now I need to make the buttons actually 
work (more event work to do).

I'm really happy that someone is porting the host-kit to an alien 
host.


1) it proves that the design was pretty well thought out to begin 
with

2) might convince people that porting actually is possible, without 
much help from RT.
3) shows that it doesn't require 100 programmers 6 months

4) shows how Carl is cooperative with host-kit issues, even when 
one isn't in the "inner circle"

5) The amiga being such a different beast, its a good way to find 
any problems and make it a better API overall for all platforms.

We could use a Haiku or AROS person as well.

Yes ... but prefereably Android, Windows Mobile 6.x, ARM embedded 
:-)

Isn't WM6.x effectively dead? MS moved to 7 and I think it's not 
compatible.

effectively yes, but tens of millions of devices out there. WinCE 
will probably stay too. Well, this was my preference because I use 
Touch Pro2, but if we decide against it, I might buy different phone, 
although there is now no alternative to such a gem like Touch Pro2 
(full qwerty)

Win7 Mo is a toy OS, as iOS is. If someone is able to port it to 
such phones, it will be good, but dunno how difficult is it going 
to be, or if it is even allowed ...

Henrik: I think we should focus on a more mobile-oriented target 
next. Haiku could be interesting given its unique API. AROS is just 
an Amiga clone so I don't see much value in that one from a host 
kit testing point of view.

ssolie, yes, true. I suppose first goal would be an ARM port.

yeah, the ARM would allow us to use R3 on iphone and possibly Android, 
though the Android API is JAVA so it might be complicated to link 
into the GUi and stuff.

proper linux and osx ports would probably preferrable first :)

I may be missing something fundamental, but


1) am I supposed to be able to build a A110 r3.exe from the sources 
at github.com/carls/R3A110 on Windows with MinGW and gcc? The gcc 
makefile differs in a lot of places from earlier versions (A109 and 
below) and even seems to generate some .so's instead of .dll's. It 
fails for me with 

gcc  -c -O1 -D_FILE_OFFSET_BITS=64 -Wno-pointer-sign -I ../src/include/ 
 -o obj/host-main.o ../src/os/host-main.c

cc1.exe: error: unrecognized command line option "-Wno-pointer-sign"
before doing anything.


2) given that I somehow manage to build it and include my own changes 
in a clone of that repo, what happens to them if once there's a A111 
repo? I don't see how a A110 repo could be turned into a A111 repo 
- I would have expected to have a R3 repo on github and to have commits 
tagged as constituting a alpha version like A110, A110 etc.