World: r3wp

For getting rid of the DOS console, you should compile using the 
following option: -t Windows

The default target on Windows for Red/System apps is MSDOS (console 
mode). When Red will be there, I guess we'll switch the default target 
to Windows (GUI mode).

The icon file should go in the directory where you start the executable 
from, so usually that would be the builds/ directory that Red creates 
within itself

Alternatively, you could add a path to the icon in the program

There are no facilities in Red yet to add resources within executable 
files

I think that reshacker tool should work for that: http://www.angusj.com/resourcehacker/

Yeah, but it's very system dependent

An executable resources handling module for Red/System linker would 
be nice, if someone is interested in contributing.

An alternative to ResHacker, XN Resource Editor, http://www.wilsonc.demon.co.uk/d10resourceeditor.htm
Windows only I think.

Implemented the ability to maximise or fullscreen a GTK window

I squeezed both maximising and resizing into the dialect, but the 
expressiveness is getting tight

IIRC, you'll present Red on 09/12? (Syllable conf?)

Dec 10, GeoFreedomDay

http://www.geofreedomday.nl

Are your bindings ready for the show?

I hope they will be ready for the show, but they don't exist yet 
:-)

Adrenalin is the best drug to make them on ;-)

Oh, I see :-)

Thnx for the answers.

By the way, I added an extra error message when the icon file cannot 
be loaded

I have a basic binding with OSM GPS Map working

A simple OpenStreetMap browser goes like this:

#include %OSM-GPS-Map.reds

gtk-view [
	gtk-maximize
	"OSM GPS Map Browser"
	osm-gps-map ogm-new-osd
]

I've got a basic binding with LibChamplain to work, too

The code for an OSM browser is very similar

The presentation of the map bindings at GeoFreedomDay went well - 
that is, after I could coerce my Linux to display on the beamer

People immediately came up with the standard question of "Why yet 
another language?", but when I showed the GUI dialect and compared 
it to conventional development, they recognised that something special 
was offered

I'll make some screenshots tomorrow

Nice ..

http://red.esperconsultancy.nl/screenshots/OSM-GPS-Map-browser-on-RedSystem.png

http://red.esperconsultancy.nl/screenshots/Champlain-map-browser-on-RedSystem.png

Response from Twitter: "Good job. This makes even butt-ugly Gtk look 
cool."

My thoughts exactly

It seems that float support is bothering more than one RED supporter 
here, so we will see what's Doc's decision towards the priorities, 
once Doc is back ...

I've got my WebKit browser to work on my graphical version of Syllable 
Server, so I'll start using it for real browsing tasks

I've moved the GLib binding in the GTK+ binding to a separate project, 
here:

http://red.esperconsultancy.nl/Red-GLib

This is now needed by every GTK binding

For your information: A small code editor including lua scripting 
(GTK + scintilla bindings)
All sources included.
Low c footprint.
A good inspiration for further RED evolution.
http://caladbolg.net/luadoc/textadept/manual/1_Introduction.html

AKA an aspiring RED code editor

with RED scripting

Looks interesting, Steeve. Be sure to post what you find out about 
Textadept in the Editors group.

It's nicely integrated with Lua. Doc has a similar plan for Red, 
and I'm also looking in that direction

I've published the map bindings here:

http://red.esperconsultancy.nl/Red-GTK-Champlain

http://red.esperconsultancy.nl/Red-OSM-GPS-Map

Hi, I am interested into building an maintaining documentation for 
those programming languages based on REBOL.
It would be nice to have a DOCBASE for them.
What I search is:
- Someone ABLE to SETUP the Linux and the Wiki Software
- Someone which would share with me the cost of hosting.
Do you like the idea ?
Write me at [giuseppe-:-chillemi-:-eu]

I want to help with that too, when time allows, but I think we need 
the authors of the languages to be part of the decision of how it's 
done. If they all want to do it different ways (and we want their 
input), that may be difficult.

Hosting should be very inexpensive, and I am willing to help with 
that.

Hope all of the authors see the advantage of having a common infrastructure 
for documentation.