World: r3wp

(of REBOL/view that is)

ok, thx Maxim for all your help!

I'm outta here for now.

happy to help,  the people here like helping out new REBOLers, don't 
hesitate to ask however simple you might think the question.

Welcome Jonathan!


The console is your friend, but you're not the first to overwrite 
a system word and have to start a new session. REBOL has a few gotchas. 
With great power and all that. 

>> d: now/weekday
== 3
>> pick system/locale/days d
== "Wednesday"
>> system/locale/days/:d
== "Wednesday"

>> day-name: func [date [date!]] [pick system/locale/days date/weekday]
>> day-name now
== "Wednesday"

hello

umm so im kinda new to rebol, actually it was today when i decided 
to learn this language, and im thinking of making my diplome work 
in it . so i would ask some question if its alowed

ah, welcome! ask away :-)

can i write programs in rebol that is abel to connect to my phone 
via cabel or bluetooth so i can read my sms and stuff like that?

so do they have functions that are abel to connect to phones or stuff 
like that?

That depends if you have access to libraries that already do this. 
REBOL can't do this directly, but it may be possible through a DLL.

(you may want to start with some simpler stuff first)

ye sure thats what i was thinking of, but i donno if its worth to 
learn , if i cant use it for that phone thing

i thought it has some methods

i wanted to do it in java first, but then some one told me about 
this language

it's probably easier for you to do it in java, if you already know 
it.

nop, i dont have much experience in java either, but i was thinking 
hmm phones hey then java why not

REBOL does not currently run _on_ any phones (that I know of) though 
this blog post offers some hope:
    http://www.rebol.com/cgi-bin/blog.r?view=0274


If you want to connect _to_ a phone from a REBOL-supported platform 
(Win, Lin, MAC, etc) then, as Henrik says, the crucial issue is the 
API to access the phone's functions. REBOL can probable connect to 
that API. But without more details, we'd be guessing.

thanks that was helpfull, o its actually possible to do it

probably :D

I'd suggest that if you want to try REBOL, you need to figure out 
the basics first to figure out why we use it. REBOL is not a very 
popular language, but the followers are pretty loyal.

The REBOL2 external library interface (ie how you might connect to 
an API) is described here:
    http://www.rebol.com/docs/library.html

oh thank you a lot, i think there i finde some answers

i think i start tomorrow with the basics, i think i will be abel 
to do this with rebol

Good luck!
Please let us know how things are going.

I will, thank you again for help , by

Just thought I'd wave hello in here.  I've been following the rebol 
project a while and decided to take the plunge.  I have both rebol2 
and 3 downloaded, I assume viewtop is only enable for rebol2 at the 
moment and rebol3 is cli only?

welcome! and yes, correct, r3 doesn't have a desktop and won't get 
one. it will be replaced with ReBrowse, a browser-like launcher environment.

interesting, i'm just wondering whether I should be experimenting 
with r2 or r3.  What do I focus on?  Sorry for this frequently asked 
question.  is there any eta on ReBrowse?

no ETA on rebrowse. it will be quite a while before R3 is done. if 
you want a "complete" experience, you can focus on R2. R3 is the 
cutting edge, where development happens, but it's incomplete.

Ok, I shall explore r2 fully then and keep an eye on r3 development

I guess what I'm trying to avoid is spending a lot of time learning 
something in r2 which is obsolete/redundant or majorly different 
in r3.  I suppose I could try running the various r2 demos and one 
liners under r3 and learn for myself the syntax differences.

It may not matter that much, but for my case that may come from years 
of using R2 and I find it easy to switch between the two. The differences 
are mainly in dialects, ports, graphics, and extensions, while the 
rest of the language is more fine tuned and more functions are available. 
Syntax differences: There are very few basic differences here.

I'd suggest also sticking to r2

R3 has been in development now for 4 years and still there is no 
beta

Yes that makes sense.  It was the words i read that "r3 was a complete 
rewrite of r2" that made me question whether it was worth learning 
all parts of r2

There would be nothing wasted by learning r2

great, r2 it is then.  I've been passively watching the rebol project 
for a while now, years in fact.  I'm now keen to 'at last' throw 
time at it , learn it all and start programming in it

ok, simple r2 problem i'm having.  the cli window  is closing as 
soon as the script ends when i run the simple demos via the viewtop. 
 Any way to force the cli window to remain open - besides adding 
a "press any key" context to end of each script..  I'm using xp at 
the moment I swear the window use to remain open - but maybe I am 
confused with my linux rebol experiences..

right click on the demo and load into the editor to see the source.

Graham, are you you using the xp rebol/view ? try the hellowworld.r 
 script in beginner,  left click the file, the script runs, but the 
cli/output window does not stay open.

there may be a quit command in the script, so the script will close 
the console no matter what.

no there is no quit command.   actually i've run a few scripts which 
have halt at the end, and that keeps the output window open

Thinking about this, it's only natural for any output console window 
to close after script execution.  For running the demos via viewtop 
though, it would be nice to either have the script wait at the end, 
ask for user entry, or maybe have a permanent viewtop console window.

where exactly is this beginner folder?

using rebol view, I am exploring public/library/ scripts/level/beginner

ok, that script needs a HALT at the end.

so does age.r and many others

well, Yeksoon needs to alter them :-)

I think the point there was that you have an open console, and then 
DO those scripts from that console. That has the intended effect.