General R3 questions answered...

What C compiler is used to build these releases?

MSVC 6. We use this for a few reasons:

1. decent results (although we know not perfect)
2. not complex to understand its workings, makefiles, and output binaries
3. the IDE is a smart and reasonable size (not multi GB like newer studios).

The chances are also good that we will do some builds using GCC, just to verify that we are compiling in that domain too.

What libraries are being linked?

rebol.lib agg.lib kernel32.lib user32.lib gdi32.lib comdlg32.lib advapi32.lib shell32.lib wsock32.lib But note that we use dynamic multithreaded lib linking (run time linking).

Is the stuff in the .exe going to be the open source part, and .dll the closed?

Yes, exe part is open source, and we really encourage developer help and contributions.

But just to note, we will be selective about contributions to maintain the principles of REBOL. In other words, if you want to build a 500MB exe for yourself, we won't stop you. But, the REBOL std exe will never be made that size, because we do not believe in the modern ignore-the-bloat methods of software design.

Someone asked in the blog, if the cursor icon can be changed.

Yes, it can be, and there is a very cool demo of it in the examples folder. It shows many different cursors and even a custom cursor with alpha transparency that you are sure to enjoy.

I guess, such things are going to be in the open source part?

Yes, that's where such things are implemented. But note, we are going to incorporate most of such things in the standard design, and it is too early for users to be questioning about what is and what is not in it. R3 is going to be a good system! If we miss something important, then you can help us to add it!

5 Comments