World: r3wp

I'm planning a Cheyenne bugfix release tomorrow, if you've found 
some new bugs to fix, please report them in Cheyenne's bugtracker 
or post them here. Thanks.

Go Doc Go!   Not a bug note or anything, but I'm becoming very intrigued 
by the potential of emedded Cheyenne.  Go Doc Go!  ;)

Did you played with the %embed-demo.r sample ?

Yep; and some.  I have visions of suger plums dancing in my head. 
  REBOL Website bundles.  Transient home PC whiteboarding.   Kick 
Cheyenne and dance with a browser, have your friends attach to the 
ip and then, after the fact close up shop.   Zero-conf temporary 
web hosting, and the apps are pure REBOL scripts.   Sweetness abounds. 
 I  think up new applications just about everytime I think about 
Cheyenne now.   I was busy when you announced .9.16 so I didn't think 
deeply enough about it (I woohoo'ed, but thaty was it)  It struck 
me like lightning the other day.  I broke with tradition and dropped 
a note to Carl, I was so excited.   GO DOC GO!   :)

Cheyenne release v0.9.18 beta. Download at http://softinnov.org/tmp/cheyenne-r0918.zip

This is a bugfix only release, it fix many bugs, especially the one 
introduced in the previous release causing an exit from the main 
event loop. See details in %changelog.txt.

go Doc, go! :-)

As this group might be followed by our French friends, I have one 
off-topic request ... if here is anyone from Paris area, I would 
like him to msg me privately. Our Company is opening subsidiary in 
Paris area, and I need to find local partner, who would eventually 
take care of some local IT related duties :-)

Binaries for latest Cheyenne release available here : http://softinnov.org/cheyenne/blog.cgi?view=0017

Doc - think you need to check the Cheyenne blog rss setup, when I 
subscribed and followed a link it went 404 and pointed to the following.


http://softinnov.org/article/0017.html

rather than -


http://softinnov.org/cheyenne/blog.cgi?view=0017

FYI, Rod.

Thanks, Rod, I'll fix that asap.

RSS links fixed.

Looks good Doc, thanks.

running on great Cheyenne http://wrapr.org/

Very nice Will.  Highlighting that REBOL can do media ... proof in 
the pudding.

That's great !

Thanks 8)

but that is mostly ajax, and load is put on the flickr api.. now 
for something that really use Cheyenne rsp power, check this http://beta.arounder.com/amsterdam/city_tour/van_gogh_museum_01.html
click on the "read" tab, there is a little number in gray, that is 
page generation time, then reload the same page and check again, 
it use a uniserve/service memcache, also conside that it's on a multilanguage 
framework 8)

Btw, just as teaser, Cheyenne will soon have its own dedicated website 
with documentation and a roadmap for all planned features in future 
versions..among them, there's a new server-side framework providing 
100% separation between HTML and processing code. Petr, you gonna 
love it ;-)

will we have much of a rewrite of existing apps?

Built in LNS server support?

RSP framework will stay and will be improved. The new framework "X" 
will be an addition, so you will always have the choice to use whatever 
framework suits best your needs : CGI, RSP, "X", QM, or FastCGI engines 
(like PHP).

dockimbel, I'm using RSP for the forum and it's working great so 
far. no problems.

LNS or something similar, definitely. I would like something "lighter" 
if possible, than RT's LNS focused on speed and security.

with RSP, would there be an option to only run .rsp files and not 
.r? if I want to serve .rsp pages and allow downloading of .r scripts?

i.e. when the user asks for .r files, not when another .rsp page 
wants to include them

Sure, It's just a matter of configuration in %httpd.cfg file.

Just remove .r from this line : bind-extern CGI to [.cgi .r], and 
.r file will be served as static files.

thanks

What is the advantage of  "x" framework? What kind of stuff does 
it enable us to do?

The main feature has been already exposed above : clean and complete 
separation between HTML and REBOL code.

I would also like to add AJAX and DB abstraction layer, but I didn't 
yet decided what approach would fit the best with REBOL. It needs 
a lot of experimenting first.

My desire is to integrate the best features found around in other 
web frameworks, but in the most efficient way (simple, fast and lightweight).

clean and complete separation between HTML and REBOL code
 

So you are not mixing rebol code with html in one file? (like in 
RSP)

But your building web pages using rebol code alone? Is the server 
acting like a serverside "plug-In"?
Sorry if I sound completley novice.

hmmm... I'm building a dialect that builds HTML code, in a sense, 
weeding out the need for HTML code inside the rebol code. is that 
what "x" does?

Henrik, I like that idea.

Is that what Magic! does somewhat. I know in the docs there seem 
to be widgets.

magic is not there imo

Doc - sounds cool!

Henrik - what he meant was to use some other means of tagging imo. 
Simply no combination of REBOL and html code. That aproach ala PHP 
is total crap

Pekr, "not there". You mean just not powerful or useful enough?

I've tried to get it up and running (Magic!) but have never got it 
to work. Apachi always gives me a hard time. Since its CGI based 
I tried with Cheyenne but again unsuccessful.

The new framework will still use HTML for UI but without mixing it 
with REBOL code.

Doc, if you have specific complaints about LNS, please chime in - 
I am looking over the code now.

HTML templates will be static files and some advanced widgets (like 
those AJAX-based) may be generated dynamically.

Are you going towards a asp.net style special tags model for the 
dynamic widgets?

Brian, nothing specific, it just looked "too big" last time I've 
checked the source code which was a year ago. I should have a look 
in Devbase for the latest version of LNS.

Nope, no custom tags, just plain HTML/xHTML.

I put in some minor fixes yesterday, but I haven't yet had the chance 
to really look it over properly. Any advice would be appreciated, 
especially related to speed, size and security.

I didn't decided yet, but I may use <span> tag for extending the 
set of HTML standard widgets.

(Sorry, my internet connection died in the middle of the conversation.)