World: r3wp

And I agree, it is a one way ticket. Carl was way too long away from 
the GUI topic. RMA surely is going to use its own gui for its own 
apps. And the official R3 GUI? Who knows, but I bet ppl will prefer 
RMA's work, than having nothing in the end ....

... after all - anyone can have suggestions to R3 GUI, so even general 
R3 community should get what will mot probably fit us all ....

mot= most

I watched Carl's AmiWest talk ... and he again calls for simplicity.

The trouble is, simplicity doesn't scale ... as seen with VID and 
IOS

ie. the case for simplicity in this format remains unproven

I wouldn't say that about VID. VID is simply incomplete. A completed 
VID would not be much more complex.

that's my point

The simple approach leads to incomplete product

I thought your point was that "simplicity doesn't scale". Simplicity 
is not the same as completeness.

doesn't scale means doesn't complete

That doesn't make sense... The VID Extension Kit won't entirely prove 
simplicity, because it needs to work around a buggy View, but when 
building all the necessary subsystems, the principle of VID is sound 
for highly scalable apps.

Unproven assertions

Not unproven. Take REBOL functions for managing series. Are they 
incomplete?

Making simple architectures is hard. It requires an understanding 
of how to design systems that will work both in the big and in the 
small, while remaining simple. If you don't have this understanding 
(or don't get enough time to finish the design), you will tend to 
add more systems to cure the symptoms or counteract existing systems 
for scalability. I thought this was pretty basic?

That's also my point, achieving the necessary simplicity has been 
too hard so far and has failed.

You might get 80% there with this approach ... but not all the way

The 80% however makes it seem that you can get all the way...

I'm not sure what that means. The 80% rule is part of good design 
for where you need to be, not for where we currently are with VID. 
VID does not follow the 80% rule since its incomplete.

load-gui.r must be update to check the Rebol version and print an 
error if it is not compatible.

what was the last version compatible with load-gui?

Work in A96, doesn't in A99. I don't have A97 nor A98 to check !

The last version it works under is: R3-a97-3-1

I'd say complex systems out there have proven that they don't scale

We have setup official R3-GUI download place: http://www.rm-asset.com/code/downloads/files/r3-gui.r3.zip

To access all our stuff directly: http://www.rm-asset.com/code/downloads/

Thanks, Robert!

Maybe provide a unzipped download for the r3-gui as well? So that 
we can directly DO the url?

Ok, that's possible as well. I just wanted to avoid any encoding 
clashes. Will add it. One second.

Ok, done. We will add more stuff like the style browser. I need to 
talk to the guys how to best do it, so that it all works right out-of-the-box.

Great, thanks!

Constructive feedback for current release always welcome.

Maybe I'm doing something wrong...

R3 current version: 2.100.110.3.1
It was released on: 2-Nov-2010/3:55:04.875

Your version is current.
>> do %r3-gui.r3

Script: "R3 GUI - load and start" Version: $Id: $ Date: 9-Dec-2010/10:32:04+1:00

>> change-dir %test-framework
== %test-framework

>> list-dir

core-tests.r   cpl_2_100_110_3_1.log         docs/          flags.r	test-framework.r
>> do %test-framework.r
Script: "Untitled" Version: none Date: 16-Jul-2010/13:05:26+2:00
Testing...
file: core-tests.r
LOAD/next removed. Use TRANSCODE.

Done, see the log file: /C/Documents and Settings/striker/Bureau/R3/test-framework/cpl_2_100_110_3_1.log
Total: 1 Succeeded: 0 Failed: 1


Log file :

file: core-tests.r

failed, file parsing unsuccessful
Total: 1 Succeeded: 0 Failed: 1

Why ?

This setup will raise the release frequency of R3-GUI a lot as we 
will use automatic scripts to update it on the server.

Nice, direct DO of r3-gui works fine for me (with custom-built A110 
view).

If you are worried about encoding issues have the web server serve 
.r3 files in binary mode. DO reads the files in binary.

There shouldn't be any unless you use binary compression or a checksum 
without compression.

I meant: There shouldn't be any encoding problems to worry about 
even without that unless ...

Nicolas, the expression:

do %test-framework.r

surely does not behave as you described

(unless you changed the original file)

I see the same behaviour Nicolas describes.

Using the (older) test framework sources published on the RM Asset 
website:

http://www.rm-asset.com/code/downloads/files/test-framework.zip

Aha, that is an old version, OK

We need to update this one too.

Juste re-download R3, r3-gui.r3 on another computer...

>> do %r3-gui.r3

Script: "R3 GUI - load and start" Version: $Id: $ Date: 9-Dec-2010/10:32:04+1:00

** access error: cannot open: shape reason: "module not found"

>> upgrade
Fetching upgrade check ...

Script: "REBOL 3.0 Version Upgrade" Version: 1.0.1 Date: 7-Apr-2009
Checking for updates...

R3 current version: 2.100.110.3.1
It was released on: 2-Nov-2010/3:55:04.875

Your version is current.
>>

nve, you need a "view" build of R3 in order for the GUI to work.

I think I will add the R3 build we use to the web-site as well...

You can either build one from the Hostkit yourself, or use e.g. the 
pre-built one provided by Henrik:
http://94.145.78.91/files/r3/gui/r3.exe
http://94.145.78.91/files/r3/gui/r3lib.dll

I'm going to upload our internal build in a couple of minutes.

Ok, loading r3-gui.r3 is ok now.
Still have failed for test-framework.