World: r3wp

Just to be clear, I'm lamenting the time Doc needs to waste.  


For example, I moved my WebCAm from one USB port on my PC to another 
on the same PC.  This apparently made Windows think it needed to 
reload the entire installer for the drivers..............................something 
like 50 megs, plus about 15 minutes.  WTF!?!


Earlier today I wanted to VNC into an office.  2 hours, and several 
IT people, and it was 5 seconds per frame update.  WTF!?!

I'm tired of working out simple problems over and over again…

er, end <rant>

you are actually very right :-)

Rant on...rant on  Intelligent bitching is one small way of getting 
through to people.  :)
 
Oh yeah, Cheyenne group...Go Doc Go

Pekr: are you using a php.ini file ? If you're using one, just remove 
it and retry the test.

there was not php.ini, just _php.ini - I moved it out, still the 
same ... currently on vacation with my notebook with Vista. Tried 
relative path, absolute path, no path - manually starting php-cgi 
- b 9999, still not luck ....

Does anyone else have the same issue than Pekr running PHP scripts 
with Cheyenne on Windows ?

I got a message from another user having the same symptoms, so now 
at least, I know that it's not your PC fault ;-). Still, I can't 
reproduce it on my development box....

so release 1.0 is to be delayed until php support is fixed??

I guess it should not. Currently, what takes me time is the web control 
panel that I'm adding to Cheyenne and the UI part (HTML) really takes 
a lot of time. Once it's ready, I'll release the 1.0 rc1.

web control panel??

is that to replace a console application?

BTW, EJSCharts are now out of beta .. I found it really easy to add 
line charts to my portal http://www.ejschart.com/

the free version only allows one or two graphs per chart

The web control panel purpose is to provide an embedded UI for managing 
Cheyenne configuration. Once done, you shouldn't need to edit the 
httpd.cfg file anymore.

I plan also to allow remote administration through reb|web-services, 
but after the v1.

Pekr: ok I've reproduced the problem, it seems to occur on XP-SP2 
but not on XP-SP1... Should be fixed soon.

Anyone got a wiki working with Cheyenne ?  Vanilla or derivative?

Doc - right, XP SP2 on my home PC, but it is related also to Vista 
(my work notebook)

Ok, the issue with PHP interfacing can be solved by specifying a 
full path for 'root-dir in config file (it's not related to Windows 
version). I'll fix that for the next release so that relative path 
could be used too.

If you don't want to mess with the httpd.cfg file, it's a one-line 
fix, just change the following line in %mods/mod-fastcgi.r :

path: form to-local-file req/in/file

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.