World: r4wp

sizeof(fltk::Widget) == 60.

The "core" (the "hello" program compiled & linked with a static FLTK 
library using gcc on a 486 and then stripped) is 82K.
The FLUID program (which includes every widget) is 352k.

Still fits on a 720K disk

That's nice, but it's still C++, and mandatory 3D hardware, I think

They also have conflicting development branches, worse than SDL

Support for OpenGL overlay hardware on both X11 and WIN32. Emulation 
if none

So hard to get on other platforms and less supported PCs

http://www.fltk.org/doc-2.0/html/index.html

FLTK (pronounced "fulltick") is a LGPL'd C++ graphical user interface 
toolkit for X (UNIX®), OpenGL®, Microsoft® Windows®, OS/X, and several 
other platforms.

Trying to see what other platforms means

LGPL couldn't be integrated into R3 because of conflicts with the 
Apache licensing model, right?

Yes, the major three, Linux only if you have drivers for your hardware, 
and little chance to get on other platforms

No, Apache only has a problem with GPL

Heh, also available on AmigaOS4

In contrast to libraries like Qt and wxWidgets, FLTK uses a more 
lightweight design and restricts itself to GUI functionality. Because 
of this, the library is very small (the FLTK "Hello World" program 
is around 100 KiB), and is usually statically linked. It also avoids 
complicated macros and separate code preprocessors, and does not 
use the following advanced C++ features: templates, exceptions, RTTI 
or, for FLTK 1.x, namespaces. Combined with the modest size of the 
package, this leads to a relatively short learning curve for new 
users.[citation needed]


These advantages come with corresponding disadvantages. FLTK offers 
fewer widgets than most GUI toolkits and, because of its use of non-native 
widgets, does not have native look-and-feel on any platform.

SDL binding for R3 shouldn't be too hard. (Of course that doesn't 
help with the SDL 1.2 vs 1.3 issues Kaj nicely summarised.)

Bo - I wonder if you know about Cyphre's intent to accelerate View 
anyway, so imo Carl just misses important info on what is actually 
going on ;-)

https://groups.google.com/forum/#!topic/rebol/6MMlv-E3j-E

I don't think you would gain anything by using SDL to get R3GUI faster. 
AFAIK SDL has no 2d graphics support...it's just low-level lib for 
handling the OpenGL or 2d framebuffer. There is no support for 2d 
vector graphics, font rendering etc. so you'll end with the same 
needs for the UI engine in the end.

As Pekr mentioned above, with the new R3 graphics code reorganization 
I'm working on it will be possible to even create a compositor based 
on SDL though if anyone is interested in doing that.

or use OpenGL directly ;-)

@Kaj, you are unstoppable!! 
So many times as well I have no clue what it is all about. :\

I found out I do not need JNI though, no  need to program my fridge.

Java is way too bloated for fridges; they should run on Red :-)

I want red fridge :-)

There you go - cheap at half the price - http://www.very.co.uk/swan-sr9051r-60cm-fridge-freezer---red/1119903640.prd

:-)

That's a pretty small fridge compared to what we are using.

It's a [Red]uced fridge

Bo: In Europe there are "Fridge" (like the Red one above) and "American 
fridge" like

http://www.very.co.uk/samsung-rsg5ucrs-american-style-frost-free-fridge-freezer---stainless-steel/1195012798.prd?browseToken=%2fb%2f4536%2fr%2f100

Moving to ~Chit Chat.

Thanks, Robert and Saphirion team!

Robert, it would be useful if everyone on your team adopted the same 
mdp style and template

I was parsing your mdp docs to convert to epub and found some have 
authors or not, dates or not, tables were done differently etc

Robert, you've uploaded the reactors documentation ... but I was 
under the impression reactors have been removed!

So, shouldn't we just delete that reactor stuff?

MDP style: Well, we need a pretty printer ;-)

Reactors: I just packed everything on the docs dir we have as a start. 
So, yes, we need to sort it out, get rid of the old stuff etc. So 
feel free to delete it and send a pull-request.

And is there any point in uploading the html docs?  Since they have 
to be generated

No, as said I just used the docs dir and didn't went through it. 
Well, seems next time we prepare it a bit better.

Ok, I'll figure out how to send a pull request on these

As long as other people agree .. it would be painful for you to have 
to update the html docs each time the mdp ones are changed

This coult be done with a commit hook on our side, but yes, HTML 
is not needed.

Looks like a number of other docs are not there.

validation-proposal, dialog-system, gob-capture, save-state etc

or I just missed seeing where they are :(

Thanks for noting the blog update Petr. Nice to hear he's enjoying 
himself so much. Maybe we'll get him back into REBOL when he sees 
that he can build Roku stuff in Red.

Well, I wish him well too. OTOH he contradicts himself. He says, 
he is interested in Rebol, yet he is addicted in something completly 
else, not finding free time for rebolling. I hope you will meet him 
at Devcon, so that he gets excited about Rebol againt too :-)

I don't think it's contradictory. He focuses deeply on one thing 
at a time, and everything else is lucky to get any time at all. It's 
just that now, Roku is his focus.

OTOH, his work there may lead to new thoughts for REBOL and other 
languages targeted at small devices in a networked world.

It's a bit odd that his creation is so fantastic that he can't use 
it

Perhaps it was never designed to be use in memory constrained embedded 
devices

Perhaps it was never designed to be used?