World: r3wp

This who process could be controlled by a VID dialect that creates 
the object that then generates the page

Yep

My web framework works along those lines, but it doesn't use objects 
in that place

I'd imagine it could be quite the killer app .. a dialect that generates 
a web page for you switching between YUI, jQuery or whatever JS framework

That's more in the direction of Weblocks

Where's your framework?

On my disk :-)

Ahh.. Maxware

The html dialects I've seen before don't address the issues of JS 
frameworks ...

Might make an interesting project ...

Not really; it's running a number of sites, including the Syllable 
sites. It has also performed the final distribution build of the 
last Syllable Server release. But it's not published

I've in the process of rewriting a site I built 3 years ago in YUI 
and it is so tedious and repetitive.

Ideal target for dialecting

So, does your dialect build QM sites ?

I'm not using an HTML dialect; at least not as a requirement. The 
dialects I have are text, not REBOL

So I'm doubtful people even here would understand my design decisions 
even if I would publish it

For example, I did the Try REBOL site with it on top of QM, but I'm 
working on replacing QM fully

with ...?

My framework. They're both MVC-style

Endo: I will need a rebol code obfuscator for making one of cheyenne 
webapps also run locally. I don't know how encryptor would work since 
local app would have to decrypt it to run it so others can see that 
and decrypt it also in same way.

but I haven't yet started coding it.

5-Aug-2010/20:58:17-7:00 : make object! [
    code: 200
    type: 'syntax
    id: 'invalid
    arg1: "tuple"
    arg2: "247hvs.cloud-ehr.net"
    arg3: none
    near: "(line 171) 247hvs.cloud-ehr.net  ["
    where: none
]

when using this for a webapp

@janko: I use Zend Encoder to encode my PHP scripts before give them 
to my customers, so they cannot see/change my scripts. Zend Optimizer 
is a free tool which installed on IIS or Apache, it simply reads 
the encoded php files decode them and execute. It really difficult 
to crack it, not impossible ofcourse but it gives enough security 
to protect sources.

I thought that it can be easily adopted in Cheyenne to read & execute 
encoded RSP files.

I've been thinking of how to separate code from display and have 
come up with the following ideas http://rebol.wik.is/Cheyenne/Page_Title/HTML_dialect


Basically the idea is to create all the html, js, css beforehand, 
and then emit in a template.  When the parser runs through the layout 
block, it builds all the CSS and JS links.  Once it reaches the body, 
it recursively parses the div tags building and closing them.  In 
the same way html, head and body tags are built and closed.

Hopefully this will result in more maintainable code .. as the whole 
page is now Rebol.  And like classical programming, we "define" all 
our variables first .. and then use them later on.

Has anyone done anything similar already?

yes, I wrote the HTML dialect to do a similar thing, though not with 
direct mapping of HTML tags to REBOL words.

I get the idea that your dialect is much more low level ...

actually it's more high level. you get loops and mapping of blocks 
and objects to tables, etc.

are you still using it?

yes, it's used on my website.

and I use it also on the R2 and R3 pages for GUI images, that I serve 
locally, as you have seen.

Have you got any examples for the pages on your sites?

I can see if I can pull a few out. The reason the HTML dialect is 
not published yet, is because the docs contain examples about redirecting, 
and coincidentally, redirects to an empty page. :-)

perhaps I can remove those parts for now...

http://www.hmkdesign.dk/rebol/html-dialect/docs/0.0.7/html-dialect.html

yes, you can use that for now.

I think I might develop my idea a little to see if I can get anywhere 
with it.

Note the docs describe version 005 to 007, whie I have 008 here.

I think what I am suggesting is a MVC approach, and so clearly the 
template at the bottom is my View, and the code at the top is the 
Model and Controller.  I imagine that it would be quite simple to 
change the View with this approach

So, in this page you could have a selection of Views ready to render 
depending on user input.

I've posted an outline of the parse rule on the same page http://rebol.wik.is/Cheyenne/Page_Title/HTML_dialect

Any parse experts care to comment ...

Rule is now working ... recurses thru the div blocks

sample template and actual ouput http://rebol.wik.is/Cheyenne/Page_Title/HTML_dialect_demo

This uses the Yahoo YUI grid t1 example

http://developer.yahoo.com/yui/examples/grids/grids-t1.html

A html dialect that builds tables and such would be used outside 
of the template.. which only does a simple substitution

Endo: I think it's possible to encap the Cheyenne server including 
RSP files, but it would require some hacking the code.

Wasn't Doc planning a virtual file system for that?

It's possible.