World: r4wp

R3 droid is a nice work. Hope to see it with nice GUI elements.

MaxV: we apreciate your work but I personally prefer a MediaWiki 
page because upgrading the engine we will have true international 
language support.

its nice that Carl is willing to hand over control of various rebol 
main sites to the community... this is a big deal everyone.  :-)

Cyphre and Robert! Thank you so much for the Android release. I can't 
wait to try it out.

Hello MaxV: Congrats to your first R3GUI app! ;-) I have some questions/notes 
though:

1. Why one needs to download the two DLL files to get R3B running?? 
(not much user friendly IMO)


2. On your Blog page you say: "First of all there are some bugs, 
most of them depends on R3GUI, for example this one: https://github.com/angerangel/r3bazaar/issues/8"

I bet this is not related to R3GUI at all but more to your R3B build. 
The REQUEST-FILE works without any problems in our Saphirion build 
(and I think also the "official" Carl's build works well but haven't 
tried it). I tried to download and run your R3B binary and I can 
confirm the bug is related only to this version so it would be fair 
enough if you remove your R3GUI blaming from the blog entry if possible. 
I know R3GUi is not perfect so maybe you can just change the blame 
for some other which is really related to the framework. Or better 
feel free to ask any questions in RgGUI group here!

3. I've looked into the EDITOR function code and comparing to the 
R3 editor code (which is still twice as big as the R3GUI version 
- but I don't know if they match the features though) the R3GUI code 
looks much cleaner and abstracted that the R2 style even if you are 
not expereienced writing R3GUI apps. Some notes:


3.1 I'm curious why are you accessing the internal AREA style value 
like face/names/tb or aa/names/tb/state/value? Is that for some reason? 
Why you don't use the AREA directly like:
do-actor/style face 'on-key arg 'area
instead of
do-actor/style face/names/tb 'on-key arg 'text-box

or

write (to-file AA-INFO/OPTIONS/text-edit) get-face aa


write (to-file AA-INFO/OPTIONS/text-edit) aa/names/tb/state/value 


3.2 There is "classic" but anoying bug. If you open file requester 
and close it without selecting a file the editor errors out. (but 
you probably already noticed)


3.3 Would be great if you add keyboard shortcuts. It's easy to add 
them. See the layouts-15.r3 file in R3GUI Saphirion package as an 
example.


3.4 Maybe you could try to write your first R3GUI style - MENU It 
would be handy in the editor(and also in other apps) instead of the 
buttons on top.


Anyway, thanks for promoting R3 and R3GUI. I appreciate all your 
efforts!

1. Saphirion public source works that way, I didn't change anything. 
So if you have some trick to make it better, your are welcome to 
contribute. I use MinGW to compile it.


2. "official" R3 has no graphic support, R3B is the public Saphirion, 
so some investigation is needed.


3.  Thak you, but I never found a R3 editor, I don't know of what 
are you writing. Where is R3 editor?


3.1 I'm a total beginner and too much documentation is missing. I 
just copied the "on-key" area action. I would strongly appreciate 
if you send me your version.

3.2 TO-DO list


3.3 I added F5 shortcut to execute code, but I have trouble to add 
keys combinations. How to control CTRL+S for example? There is anymore 
the old event/control and event/shift.

I'll never blame R3GUI anymore.

re 1. Saahirion's builds never needed to have such libraries copied 
in the program dir. I'm using MinGW includes in combination with 
MSYS make to build R3. To me it looks like some problem in your make 
procedure.

re 2. REQUEST-FILE native! has nothing to do with graphics. It is 
present even in the "official" R3 release.

re 3. by "R3 editor" I meant eht EDITOR function you have ennounced

re 3.1 here is quickly cleaned-up version: http://cyphre.mysteria.cz/stuff/editor.r3

re 3.3 Note the keyboard shortcut code stub in the link above, this 
is the way how to support shortcuts in R3GUI. Easy, isn't it?


As I said feel free to blame R3GUI where appropriate, there are surely 
bugs around...the REQUEST-FILE bug just simply have really nothing 
to do with R3GUI but more with your compiled exe.

Rebol3 on Trello is nice Graham. Could you add me? I'm "semseddinmoldibi" 
on Trello.

Added :)

Great news Kaj!

Kaj - cool! So R3 got improved R2/DLL interface we wished for :-) 
(not everyone is fluent with C, thought R3 native extension mechanism 
is not difficult to understand)

Kaj, did not run the example, but you export 'hello, but you call 
'do-hello. Isn't it bug (leftover from R/S version?)

Kaj, very nice work! Hope this would inspire others to write R3 extensions 
in Red using your binding.

Pekr: the `hello` symbol exported to R3 is mapped to index 0 in RX_Call, 
so from there you can map it to `do-hello` or whatever Red function 
you want, no bug there.

Kaj - is your binding different to Doc's one, or the same stuff?

I started my binding first, to try to help Doc make progress towards 
supporting Android. He used some code from it, but he doesn't need 
a complete JNI binding in Red itself

My binding implements the complete JNI interface now, at the lowest 
Red/System level. Doc's bridge binds only a handful of JNI functions, 
but he is building higher levels on them now towards a bridge with 
Red

thanks, Kaj. Then keep your work, more complete binding might become 
handy to those who maight need it ...

Kaj, thanks for your work. I haven't looked but are there any examples 
that I can try on my devices?

For the R3 bridge, there's a Red example and a Red/System example 
in source form. No binaries at the moment

Those are the Hello examples?

Compilation depends on a Red development branch, so I can't integrate 
it with my build runs for binary downloads yet

hello-REBOL-3-extension.*, yes

I see. Thanks, Kaj. You and Doc are something else.

Thanks

The example for JNI is hello-JNI.*, but you have to compile two parts. 
The Red/System part needs to be compiled like the R3 bridge, as a 
library. The Java part needs to be compiled by Java, similar to Doc's 
instructions for his Java bridge

Kaj, you seem unstoppable!

Kaj, great work on OpenGL!  Question: Am I understanding correctly 
that the OpenGL backends currently available don't use the hardware 
rendering in the GPU?  If this is a correct understanding, do you 
have a roadmap for including hardware rendering capability?  Just 
curious.

Yes, there's some way to go to implement other backends, but I've 
taken up work on that again

@Kaj, so you static binding could be wrttten as a r3 extension as 
well?

GrahamC - interesting question :-)

Yes, you should be able to mix library and executable functionality 
in all sorts of ways now

Not sure if Red can #import libraries from other libraries, but it 
should

Haven't tested that yet, I guess it should work on Unix, not sure 
for Windows.

Kja, nice progress on OpenGL support!

(Sorry for the typo, low caffeine level ;-))

Low sleep level here; home improvement day with Freddy

so, can you make a GUI out of all this?

OS-mesa

You have to build it yourself out of 3D particles such as triangles, 
polygons and textures. Or use an existing one and write an extra 
binding for that

Of course, we already have GTK+

There's also the other way around: most GUI toolkits such as GTK 
have an OpenGL widget, so with my multi-backend design I can make 
OpenGL backends for the widgets of those toolkits. You'd have your 
regular widgets and then the option to use part of the window for 
3D

I'm struggling with a fully built r3gui so I might just wait a bit!

I'm eying some libraries that could be used for medical applications 
:-)

most of the stuff I've needed I've had to build myself :(

In REBOL or in medical?

medical stuff for Rebol

Yeah, not much support there

well, there's a billion$ out there for medical apps

Paying customers?