World: r3wp

to :

path: form to-local-file get-modes req/in/file 'full-path

Doc - currently on vacation with my Vista notebook. That one line 
fixes the problem! Tested under IE 7.0 and FF 2.0! Thanks a lot. 
Now the last thing is to get mySQL into non-installable version :-)

I'm glad to hear that it's finally working on your Vista laptop. 
Why not use SQLite instead of MySQL ?

BTW, there's a MySQL version without installer (in ZIP format for 
Windows), see : http://dev.mysql.com/downloads/mysql/5.1.html

Hi Nenad ! I confirm that the change fixes the problem for php. Thanks 
Doc  ! Well, we have Rebol, Php, Perl, what's about Python, Ruby 
and Java now ? ;-)

Most languages support the CGI interface, they call all be used with 
Cheyenne. I plan a specific support for Java servers (by implementing 
AJP protocol in Cheyenne).

call = can

Cheyenne status update : http://softinnov.org/cheyenne/blog.cgi?view=0012

today ?  "If all goes well, the 1.0 rc1 should be released next Sunday"

Pity you can't use the Rebol plugin to create the administration 
console

It's not yet Sunday here ;-). I thought about using the plugin, but 
the browser/OS supported are too limited.

probably faster to develop though!

There's a error in RSP-API documentation, several RSP examples refer 
to session/alive? instead of session/active?.

It's been a while.  Go Doc Go  :)

Is Cheyenne migrating to R3?

Certainly not before R3 goes beta. All the underlying UniServe part 
will be rewritten from scratch to take advantage of the new port! 
model and multithreading capabilities of R3.

R2 is not yet dead, it will takes time for R3 to mature and become 
as stable as R2 is now.

Btw, work on Cheyenne keeps advancing but slower, due to my lack 
of free time, customers have a higher priority...

When's the next Sunday?  :)

It's a french expression meaning : someday ...(just kidding) ;-). 
I need a couple of days of work on Cheyenne to reach the rc1, but 
I only have an hour or 2 to work on it, here and there, so it's hard 
to schedule a release date...the customer project I'm leading is 
taking almost all my time.

If it's the control panel that needs to be finished, why not just 
release it without it ?

When my kids would ask when something or another was going to happen, 
I'd say "one day".. to them this started to mean 'likely never".

Later when they would ask 'when'? I'd say "one day' ... and they'd 
say disappointingly.. 'not ONE day'

So how much money do we need to raise to buy you enough time to finish 
it?

This is a serious remark - Cheyenne is a killer app and if a lot 
of the rebolers donate someweher between $20-$50 you mighht be able 
to work dedicated on it for some time. The community would get a 
great product....

I would sponsor it too.

Better yet, the source is there.. have at it.

Graham: it's not about the control panel, it's about several features 
that need to be fixed or added to make a stable and consistent 1.0.

Maarten: thanks for the offering, but I'm not sure that the community 
is big enough for such funding. Anyway, funded or not, I'm going 
to work on it and finish it, a lot of our internal projects depend 
on it. It's just a short delay (a few weeks) before going rc1.

Little teasing for rc1 : The win32 binary version of Cheyenne will 
natively (no 3rd party software) support running as service ;-).

Windows rawks.

hmm.  running as a service  ... nice nice nice

just go to cmd.exe Window consoíe and type: net help start :-) So, 
IMO the trick is to use "net start  cheyenne.exe" or something like 
that. Then you use "net stop cheyenne.exe". It should be equivalent 
of linux /etc/rc.d/init.d/service-name start

I'm tried using Firedaemon to run Cheyenne as a windows service but 
noticed aberrant behaviour which I reported above.

Petr, it's not that easy (unfortunately)...

Petr: Cheyenne has to be registered as a service before being able 
to start the Cheyenne service.

Graham;  I just installed Vanilla under Cheyenne.  It's working, 
but the lack of docs is making it a pain to  configure.  I'm not 
sure if setting vanilla.options.metadata  "space-mode" "open" is 
the proper way to go about things or not, but keeping it "closed" 
doesn't seem to allow much.  Until I figure out how to get associate 
status on user accounts, my test head is "open" but closed behind 
the firewall.  But it seems to be working, if not a little rough 
around the edges now I'm getting used to MediaWiki.


I think I might brave a kick at turning on PHP with Cheyenne, and 
then see if copies of MediaWiki and phpBB will run.  If so, I might 
start building up a homesite for user.r right here in peoplecards.ca 
land, but not if it means a conversion to Apache to make a wiki and 
a forum work.


Anyone going to tell me not to bother trying MediaWiki or phpBB because 
it won't work?

the problem I had with mediawiki is the amount of spam I had to remove

Good to know vanilla runs under Cheyenne .. it should be a lot faster 
running that way instead of under Apache.

Oh, figured out how to Admin vanilla.  Then went to remove the sticky 
on register-master and now I'm getting an endless redirect loop. 
 Rebol with trace/net on is reporting  /vanilla.cgi to //vanilla.cgi 
to ///vanilla.cgi ad infinitum.  Before trying it with the .9.16 
testhead (I still run .9.13 for production) I'm going to jump into 
playing with PHP5 and .9.16.


MediaWiki and phpBB apt install for Debian both include Apache.  
Rassafrassa...making me work...pulling in everything by hand...rassafrassa 
 :)

it should be a lot faster running that way instead of under Apache. 
Why?

Do you think Apachi is bloated software or  somthing...Just curious 
abbout your opinion

because vanilla runs Rebol code

gottcha!

Nope.  Just a Cheyenne fan.  The patchy server is just fine.  But 
Cheyenne is REBOL  :)

so Apache invokes the rebol interpreter each time .. whereas with 
Cheyenne the interpreter is always resident

Oops, injecting comments into other people's chats....  my bad.

I'm using Hayes Deki as a wiki now.

comes with a REST api

REST?