World: r3wp

once they start the program, they can connect to the source server 
to get updates via REBOL/Services. Delivery by the developer to the 
source server is meant to be just as simple.

Sounds like DevBase.

it's nothing like devbase.(sorry, I said docbase)  it's user centric, 
not developer centric.

in fact I hope I'll be able to use devbase with this.

I will explain more when it's ready.

(which I expect will be a year from now at this pace)

Perhaps they will converge. I have big plans for DevBase.

looking forward to that :-)

but the basic idea is that developers should have an easy way to 
distribute their programs and users should have an easy way to upgrade 
their rebol applications. there are some tricks involved to lock 
it down so only specific users can get specific updates for specific 
programs. it may be tied into a purchasing system as well. that's 
where the on-demand encapping comes in.

it is much more than just providing links to scripts on a webpage.

but it has to start at that, so I want to use cheyenne for that :-)

I just changed the secirity model of DevBase to be more fine-grained. 
It would probably be extensible to cover something like that.

secirity -> security

I wonder now if cheyenne can use REBOL/Services' account system for 
login.

A Cheyenne front end could be very useful. Cheyenne could easily 
use REBOL/Services for login.

Part of the plans for DevBase is to clean the code structure to make 
it more modular, to make different front ends easier.

sounds interesting

Doc, you may want to say system/options/quiet: true


I found this in /var/log/system.log on my Mac, when starting Cheyenne 
using Launchd:

Jan  1 11:01:43 Macintosh com.rebol.cheyenne[60072]: /
Jan  1 11:01:43: --- last message repeated 1 time ---
Jan  1 11:01:43 Macintosh com.rebol.cheyenne[60072]: -
Jan  1 11:01:43: --- last message repeated 1 time ---
Jan  1 11:01:43 Macintosh com.rebol.cheyenne[60072]: \

Jan  1 11:01:44: --- last message repeated 1 time ---
Jan  1 11:01:44 Macintosh com.rebol.cheyenne[60072]: |
Jan  1 11:01:44: --- last message repeated 1 time ---
Jan  1 11:01:44 Macintosh com.rebol.cheyenne[60072]: /
Jan  1 11:01:44: --- last message repeated 1 time ---
Jan  1 11:01:44 Macintosh com.rebol.cheyenne[60072]: -

Jan  1 11:01:44: --- last message repeated 1 time ---
Jan  1 11:01:44 Macintosh com.rebol.cheyenne[60072]: \
Jan  1 11:01:44: --- last message repeated 1 time ---
Jan  1 11:01:44 Macintosh com.rebol.cheyenne[60072]: |
Jan  1 11:01:44: --- last message repeated 1 time ---
Jan  1 11:01:44 Macintosh com.rebol.cheyenne[60072]: /
Jan  1 11:01:44: --- last message repeated 1 time ---

Jan  1 11:01:44 Macintosh com.rebol.cheyenne[60072]: -

Jan  1 11:01:44: --- last message repeated 1 time ---
Jan  1 11:01:44 Macintosh com.rebol.cheyenne[60072]: |

Jan  1 11:01:44: --- last message repeated 1 time ---
Jan  1 11:01:44 Macintosh com.rebol.cheyenne[60072]: /
Jan  1 11:01:45: --- last message repeated 1 time ---
Jan  1 11:01:45 Macintosh com.rebol.cheyenne[60072]: -

Jan  1 11:01:45: --- last message repeated 1 time ---
Jan  1 11:01:45 Macintosh com.rebol.cheyenne[60072]: \
Jan  1 11:01:45: --- last message repeated 1 time ---

Jan  1 11:01:45 Macintosh com.rebol.cheyenne[60072]: |

Jan  1 11:01:45: --- last message repeated 1 time ---
Jan  1 11:01:45 Macintosh com.rebol.cheyenne[60072]: /

:-)

Apparently it's not in the main cheyenne.r file, but during a call 
to a sub system (don't know which yet) that causes this.

I think I found the problem in Uniserve:

In uni-engine.r, replacing:

call join form to-local-file system/options/boot [" -s " cmd]

with:

call join form to-local-file system/options/boot [" -sq " cmd]

quiets it down

Thanks for the fix, it will be part of the next release.

great :-)

Doc, are you considering simple HTML templates for .rsp pages, or 
is that already possible?

Such as converting a block of values to a table:

<% print html-table read %. %>

It's not on my Todo list, I plan to make a higher level framework 
for building web applications, where I don't want to mess anymore 
with HTML or Javascript. Kind of VID dialect that compiles to HTML+CSS+JS.

cool

Just like RoR, RSP can use the following <%= %> instead of <% print 
... %>

Kind of VID dialect that compiles to HTML+CSS+JS.
 Now, that's what I'm talking about!!!

Doc - that would be too wonderful, us HTML challenged programmer 
types would be so very happy with such an option!

hi to Gregg -- thx for the invitation to your world...

oops, probably the wrong place ... plz. excuse the noob

http://www.softinnov.org/is not working?

not here either.

umm,  okay, well maybe this is the right place for a small problem 
I've encountered with  cheyenne / uniserve -- maybe not an issue 
with the server but me being new to rebol -- btw this is on windows 
2000 and happens with both cheyenne and uniserve -- when I go to 
any cgi or rsp page a new rebol console pops up in front of the browser! 
Is there anywhere in the uniserve / cheyenne source where I can disable 
this behavior?

Softinnov.org is back online. There's some bad URL requests using 
not supported HTTP method that sometimes crash Cheyenne. I'm working 
on a fix for this and will publish it asap.

Re DerekR: just look above at Henrik's message, it shows the patch 
to hide the REBOL console when CGI or RSP scripts are processed.

Hi Doc / Nenad -- excellent! (Jeez, there's the answer staring me 
in the face at the top of the window!)

;-)

While you're here -- I noticed that Cheyenne failed to fetch a jpg 
image that had spaces in its src url -- e.g. "red rock river.jpg" 
-- and "red rock river.jpg" didn't help either ...

(uniserve didn't have a problem with this btw)

Could you please fill an issue ticket about that in the bugtracker 
please : http://www.softinnov.org:8000/curecode/project.rsp?id=4

Sure thing Doc!

-- btw wanted to say how delighted I was to find a lightweight, scriptable, 
no-hassle-to-install, x-platform web server -- many thanks!!

I plan to make a new release this week, only bugfixes.

Great! --

Thanks! That's exactly why I've built Cheyenne ;-) I plan to improve 
it much more in features, speed, easy configuration,...

I had a problem with port 80 at first -- this both in uniserve and 
cheyenne -- changed the hardcoded port assignment in httpd.r to 8880 
and it worked fine

Are you on Linux or OSX ?

Can the port # be reassigned from the command line

This is on Windows 2000

use : -p 8880