World: r3wp

I agree, starting with polygons and graphics is great for instant 
visual feedback at the beginning.

i'd say the most important rebol native is INSERT. (even print is 
insert system/ports/output under the hood)

ah! "insert". I would not have thought so. Will remember that while 
picking native words...

Denis : You should maybe contact Gerard Cote on the mailing list. 
I believe he has been using Rebol in teaching introductory programming 
for a while now. He might have interesting pointers.


Also I would be curious to know if you have ever considered using 
Scheme for your courses. There are great ressources such as PLT Scheme 
and their book "How to design Programs" or "Simply Scheme" by Harvey 
and Wright. I think the content could be adapted to a curiculum based 
on Rebol

A few ideas were collected here as well 3 years ago http://www.compkarori.com/vanilla/display/Rebol+School

tks for the link Graham. And there is a mention of Gerard Cote in 
there too, Jean-François.

Actually, I'm not trying to figure out how to introduce programming 
concepts, or computer science in general. I already have a lot of 
stuff on that since I have been teaching this for 20 years now. And 
I'm not looking tor a "better" language to teach, even though I have 
given a look to Scheme.

What I want to develop is a "better" approach to learning Rebol, 
for non-programmers mostly. I'm really focusing on Rebol, and not 
what should be learned before, nor what could be a better option.

The "Rebol Essentials" is a good start. But I think I can break the 
approach down to still simpler steps. The difficulty I face is not 
having the broad, overall picture for Rebol. I am very conscious 
this limits my ability to make the best choices for the moment.

Here is what I figure would be a good starting point, at the present 
level of my knowledge:

First concepts: values, words (at a basic level), blocks (later on 
: functions)

First natives: print, arithmetic operations, the simplest control 
structures (conditional, for loop, while loop)

Then reading data somewhere and some simple parsing techniques: find 
a string, extract from one point to a second and saving the data.

I have the feeling that would be a very good starting point. I'm 
a little hazy on what is offered for parsing in Rebol at the moment. 
I'll look into that next. I think that once you have read a file 
into memory, it is in block form and you can use natives like "first", 
"next", "find" and so on on it. If so, then I would be going that 
way for sure.

read file --> string
load file --> block

Strings and blocks are both series, so first, next find etc work 
on both, but when you load you get a block and the units are values. 
When you read, you have a string and the units are characters.

When you load, the file has to be LOADable by rebol, which means 
everything in it must be parseable into rebol values.

When you read, the file can be absolutely anything. I usually have 
to read web pages and parse a string, for instance.

How about that old way of starting with a text-adventure? Write a 
framework and let the learner add some special item?

actually denis, for introducing looping I'd use foreach before while. 
 while is rather hard to grasp in the begining, cause its easy to 
bugger up the end conditions and end up in infinites loops.

for example, in parsing a sentence, foreach could make you very easily 
traverse the whole string like so:
foreach letter sentence [print letter]

also remember that find, does not copy the series, it returns the 
serie at a different index.

to extract substrings without use of 'PARSE you can do:
substring: copy/part find sentence "debut" find sentence "fin"

in the above, the string "fin" is not included, since find returns 
the start of the match by default... to include it, just add the 
/tail refinement.

substring: copy/part find sentence "debut" find/tail sentence "fin"

this can allow you to explain optional arguments later on in funcs. 
  also as an easy exercise, you can ask them to return the substring 
without "debut" or "fin"... (simply switch the /tail to the first 
find)

Anton, Maxim: noted. Hum... will have to test what happens if I use 
"début" with the accent. In VC++ console mode, the output doesn't 
use the same character table as the editor. Didn't think of checking 
this yet, but the classe will be held in French so I should check, 
although this is not vital.

Volker: good idea. "old way"? I've never seen this approach used 
before (and I'm not young). But I think it would be very motivating 
project for these students. I'll use this suggestion.

I've talked to one of my colleagues about Rebol and he's checked 
into it. He's interested also. So it is becoming more probable we 
will switch to Rebol to introduce basic programming concepts as well 
as to empower them with a programming tool to build very small applications 
to complement the scientific software at their disposal.

My colleagues suggest that we use the View GUI. He feels that it 
is simple enough to code a graphic interface with this. I admit I 
have not looked into View much. My preconception is that adding the 
graphical layer complicates things too much (like Windows/C++). Maybe 
I'm wrong as Rebol is concerned?

you are wrong :-)

well, just kidding ... it depends .... easy things are easily don 
... if you will insist on OS behavior compatibility, there might 
be some work included - but for scientific kind of stuff, it is pretty 
good imo. I do remember how relatively easily I got my results with 
Matlab ..

you may look into RebGUI project - consumes less memory (mostly non-issue 
on PC), provides more styles, resizing, more proper behavior to styles, 
try to go thru demo AND look into tour.r source - you will see how 
nicely readable the gui part is - you don't need to go into internals 
too much ...

RebGUI, something new to me. In fact, we probabably just need an 
interface to enter data and start some process and show the results. 
Maybe draw a graph with the results - that would be great. Will look 
into it. Tks.

You may want to take a look at Matt  Licholai's quick plot dialect 
for your students to use to plot results. The details are at http://www.rebol.org/cgi-bin/cgiwrap/rebol/ml-display-thread.r?m=rmlQBZK

Scroll down the thread to find the location of the source.


There is an updated version of his ez-plot example in the script 
library at http://www.rebol.org/cgi-bin/cgiwrap/rebol/view-script.r?script=ez-plot.r

Maybe you can use Rebol and  try to implement a curriculum similar 
to HtDP.  

The Structure and Interpretation of the Computer Science Curriculum 
http://www.cs.brown.edu/~sk/Publications/Papers/Published/fffk-htdp-vs-sicp-journal/

My preconception is that adding the graphical layer complicates things 
too much 

 -- A valid concern in many environments, but VID is great, and simple, 
 for simple things.


view layout [button "Show help" [alert "Sorry, I can't help you"]]


No need to manage the event loop, no redraw handlers (until you need 
to get into them of course), just put an action block after a face 
style and it binds to it automatically.

.

.

.

Did that "online school" that was talked about ever get tested? How 
did it work out?

I never heard anymore about it.

Could not find a free tool that allowed al the features we wanted.

The best we found was TeamSpeak for Voice.

It needs Chat (writte), Talk (Spoken), Video, and several Whiteboards, 
and a way to view somoeone's computer screen.

We use TeamSpeak all the time.

Tell me what is out there, and I will get this started.

Google Desktop has a plugin that makes GTalk able to make a chatroom, 
and another that allows you to share part of your screen with someone 
on your buddy list.  I don't know how well they work, thouhg

though*, as I never found anyone else to test it with*

Reichart, can you list the ones that you tried, but failed your criteria?

Can you tell me specifically what I have to learn (master) in Rebol 
(mainly instructions) to code these projects:

Project 1: Read a web page given a URL, find some data in the page, 
append it to a file on disk. Read the given disk file et show the 
data on screen.