World: r3wp

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.

Ok, uploaded.

Seems to be better.  But what is final result expected ?

>> do %test-framework.r

Script: "Test-framework" Version: none Date: 19-Nov-2010/15:00:45+1:00

Script: "Line number" Version: none Date: 1-Nov-2010/14:21:20+1:00
Script: "Catch-any" Version: none Date: 3-Nov-2010/4:58:46+1:00
== make object! [
    log-file: none
    log: make function! [[report [block!]][
        write/append log-file to binary! rejoin report
    ]]
    skipped: none
    test-failures: none
    crashes: none
    dialect-failures: none
    succeeded: none
    failures: none
    exceptions: make object! [
        return: "return/exit out of the test code"
        error: "error was caused in the test code"
        break: "break or continue out of the test code"
        throw: "throw out of the test code"
 ...

nve, the test framework runs roughly 4000+ tests and reports the 
results. See the "testing & tools" group for more details.

I tried to use SciTe editor to run a simple gui script: rebol [] 
 do %r3-gui.r3 view [button]

What I got in the output pane is: REBOL 3.0 A110 2-Nov-2010/3:56:20
handler added

but no window appeared

running the same script from command console: "r3.exe testgui.r3" 
works just fine. It opens a new console window with the same output 
" REBOL 3.0 A110 2-Nov-2010/3:56:20 handler added" and another window 
showing the button

In Scite, I configured the command Go (F5) as:

command.go.$(file.patterns.rebol)=c:\Users\awi\Documents\rebol\r3.exe 
"$(FilePath)"
so nothing different here

Maybe anyone has a tip how to fix this, I know this is SciTe problem, 
but I wonder whether other editor has the same problem. Thanks!

Add this to your configuration, and you will be able to use Ctrl-5 
to run rebol3. Change the path as needed.
command.name.5.$(file.patterns.rebol)=RunRebol3File

command.5.$(file.patterns.rebol)="C:\usr\local\rebol3\r3.exe" "$(FilePath)"
command.subsystem.5.*=2
command.is.filter.5=1

Cool! Thanks a lot Edgar! I really appreciate this.

Could style browser be updated too? It basically crashes with any 
click I tried to the style's list-box ...

The same occurs here, so we'll have to wait for Bolek to fix it.

Pekr, that's list-box (text-list) style problem. This style is currently 
updated to support more columns than one (called text-table) and 
text-list will be only sub-case of text-table.

The new distribution channel may bring problems like this for regural 
users, at least before BETA is reached. Some developers prefer to 
put changes to SVN only when everything is ready, other developers 
prefer to push changes more often, it might temporarily broke functionality, 
but  it's much more crash-proof strategy.

It's a question to debate if every submit should be a release, or 
if only some special versions should be released, with first option, 
you will get latest release, that may be broken because of we're 
still in alfa-phase, with second option you will get more or less 
working release, but you're definitly going to complain that it's 
not updated too often (even if my estimate of 1-2x week is hit.)

fails for me on any test of mine with  
** Script error: path styl/faced is not valid for none! type

where can I find the style browser for that gui?

TomBon: http://94.145.78.91/files/r3/gui/style-browser.r3

thx andreas

i just try it and it gives me that >> do %style-browser.r3

Script: "R3 GUI Style Browser" Version: $Id: style-browser.r3 1220 
2010-11-26 13
:18:02Z cyphre $ Date: none
** Script error: guie has no value
** Where: catch either either -apply- do
** Near: catch/quit either var [[do/next data var]] [data]

anybody got the same problem ?

xavier - see my previous message and Rebolek's explanation. My take 
is,that it sould be adapted to release, or ppl will find GUI highly 
non-working ...

Thy psychological trick is, that ppl will consider any such visual 
tool being a demo ... the one expecting to work. Prior R3 demo was 
nice app, pity it is not included with the releases anymore ...

The trick in communications is to keep reminding those people that 
this is alpha work in progress and that if they want something that 
works, now, they have to go look somewhere else.

Otherwise, the only option is to shut down completely and not do 
any development work in the open, but only in invisible elitist circles. 
We all know how well that approach has served REBOL in the past.

Prior R3 demo was nice app

, from what I believe, that app served the same purpose as the style-browser. 
Having Carl's R3 GUI being more limited, it could be considered more 
bug free than the current version, thus made a better impression.

well, it did not show single styles. It more showed whole topics, 
so you could see the whole forms with various styles, their setting, 
resetting, etc.  And yes, it was about the impression. I'll wait 
for style-browser fixes - the truth is, that it was never bug free 
:-)

style-browser fixes - the truth is, that it was never bug free

 - the style browser does not have any relevant bugs. the styles have 
 bugs. that's the point of the style browser.

whatever ... this is just playing with words, and I think it does 
not matter, as it is not a big deal (btw - when I found the bug, 
I reported it). My observation though is, that ppl naturally expect 
some visual demo or something like that - being it a former demo, 
or a style-browser - it does not matter. So - hopefully when things 
turn more stable, we could ask Carl to link R3 console demo function 
to launch a style browser?

this is just playing with words, and I think it does not matter

 - sorry, I think you don't understand the importance of the style 
 browser as a *testing* tool rather than as something to show off 
 with.


If we blamed the style browser for the bugs, we'd never finish the 
GUI. I really mean that style browser bugs are irrelevant. Any more 
development on it would be to make testing more thorough. At this 
stage, it's important to build the programs as we want to see them 
working, and if they don't, the underpinnings are to blame and should 
be change to accommodate the needs. That is what's going on now.


We publish the style browser to help users get the quickest possible 
overview of the styles as they are right now, crashing or not. Showing 
off is too early.


It should be possible to have the style browser as part of the demos.

A RETURN keyword poll.


The RETURN keyword is used in groups (Hgroup, Vgroup) to signal the 
end of line/column. Panels, however, neither need nor can use RETURN 
as a keyword. There is a question, whether the RETURN keyword in 
panel specifications should be:

a) silently ignored
b) considered an error

beginners will probably be irritated at b), but b) makes the most 
sense to me right now.

As far as I am concerned, I am slightly in favour of the b), which 
makes the starting score A:B=0:2

b) -- also gives you the option to add a meaningful RETURN for panels 
later on.

b) for the reasons Andreas said.

It may be helpful to put a warning in the style browser GUI

This is not a demo, this is a style browser, just like the label 
says.

:-D

Browser still sounds like a working utility. It could mention that 
it's for testing the styles and they are currently expected not to 
work