Well, not sure about the styles, if you want to map to native widgets ...
I still remember Cyphre's remark in Brno - how many usefull widgets are there in the OS anyway? How cross platform are they? So we have fields, areas, buttons, images, radio buttons, check boxes. What about more complex ones, as grids? Win32 API apps look uglier, than old 70ish unix clone. And - design sells. Let's hope, that this time, we are going to dress that :-)
DocKimbel
Red has different needs, like willing to _compile_ as much code as possible vs run it through interpreter. So the actors above need to be defined differently so that the compiler can effectively find and process them.
"Win32 API apps look uglier, than old 70ish unix clone" On each Windows platform, you will get the native OS look'n feel, I don't know what you are talking about.
I had a preview of that in Windows 10... that's what I would call "ugly". ;-)
Pekr
:-)
Robert
Doc, if you use our release on Windows: >> source load-gui load-gui: make function! [[ {Download current Spahirion's R3-GUI module from web.} /local data ][ print "Fetching GUI..." either error? data: try [load http://development.saphirion.com/resources/r3-gui.r3] [ either data/id = 'protocol [print "Cannot load GUI from web."] [do err] ] [ do data ] exit ]] >>
DocKimbel
Robert, thanks, downloaded and decompressed it.
Robert
The few docs we have are on our development.saphirion.com web-site. And yes, R3-GUI targets something different then VID or Carl's idea. It's for long-maintenance, business applications. So, not for a quick & dirty approach.
I don't know how often I explained this... If you expect a VID on R3 don't use R3-GUI, it's for full-blown applications.
Pekr
I am not sure it differs much to what Carl prototyped? All R3 GUIs are light years ahead from VID, conceptually ....