Making the move...
revolutionary.dan at gmail.com
Tue Mar 28 01:14:32 CST 2006
I agree that "merge" is very cool and quite powerful.
Still, I cannot put into a Web page:
Hello, there. The time is <% merge [[the time]] %> (regardless of the
dellimiter being used around the call) as I can with Ruby. The merge
operation would, I think, have to be included in the CGI generating the
entire text string above, right? Or am I really missing something obvious
Again, as I said earlier, this may well be a distinction without a
difference when it comes to accomplishing what I'm pointing out as the main
advantage/feature of an MVC framework for Web development, namely the
(relatively) clean separation between presentation and business logic. I'm
not promoting Ruby, just trying to understand the qualitative difference in
using an embedded scripting language vs. a CGI approach.
On 3/27/06, Richard Gaskin <ambassador at fourthworld.com> wrote:
> Dan Shafer wrote:
> > In any case, what is clearly NOT happening with an SSI is the inclusion
> > Transcript commands or functions directly in the HTML file from
> which the
> > dynamic page is generated. All of the Transcript code is external to the
> > page layout/template. The overly simplistic example I provided earlier
> > using an embedded call to a built-in Ruby function such as Time.now() is
> > key idea here. The call to that function generates NO HTML code, just a
> > value to be substituted into the HTML page when it's generated by the
> > server. Using CGI, you can't mix HTML and operational code *in the HTML
> > template or page*. This means in general that the CGI must generate HTML
> > blocks to be inserted into the HTML page at generation time on the
> Just as Ruby is used to pre-process pages containing statements like
> time.now, you can use Rev as the preprocessor with its merge function to
> do the same thing:
> The time is [[the time]]
> The merge function is very powerful, well worth spending some time with
> if you want to use Rev like Ruby or PHP.
> The key thing to keep in mind when implementing a system like this is
> that Ruby is just a text processing engine. The methods by which it's
> hooked into the server are not unique to that engine, and just about any
> capable text processing engine, such as Rev, can be set up to be used in
> the same way.
> Richard Gaskin
> Managing Editor, revJournal
> Rev tips, tutorials and more: http://www.revJournal.com
> use-revolution mailing list
> use-revolution at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
Dan Shafer, Information Product Consultant and Author
Get my book, "Revolution: Software at the Speed of Thought"
More information about the use-livecode