From: paul vudmaska <paul_vudmaska@...>
Date: 2004-02-04T05:17:17+09:00
Subject: Re: Ruby Web Application Framework Roundup


--- Kirk Haines <khaines@enigo.com> wrote:
> On Wed, 4 Feb 2004, paul vudmaska wrote:
> 
> > Seperation of duties(developers from designers) is
> > beneficial to all. My observation is that as
> scripting
> > languages become more intuitive/approachable it
> > *might* be helpful to turn their power over to
> > designers - if it can be done without jeapordizing
> the
> > integrity of the supporting system. Only with
> access
> > to variables that are pushed  to the file for
> example.
> 
> The seperation is beneficial even when the developer
> and the designer are 
> the same person, IMHO.  It helps keep the codebase
> more organized, it's 
> harder to mess something up that one didn't intend
> to change.  Also, 
> syntax highlighting works better when HTML isn't
> mixed with Ruby.

I sure do agree.

> What you are talking about with access to variables
> that are pushed to the 
> file -- what do you mean?  Can you give me some sort
> of psuedocode example 
> to illustrate what you are thinking of?

I'll try. Just as Amrita has a data property that is
'pushed' to it. 
  data = {
     :title => "a title",
     :body => "this body"
  }
  tmpl.expand(STDOUT, data)

but instead of...
  <html>
     <body>
        <h1 id=title>title will be inserted here</h1>
        <p id=body>body text will be inserted here</p>
     </body>
  </html>

something like...
  <html>
     <body>
        <h1><%=data['title']%></h1>
        <p><%=data['body']%></p>
         ...just testing what i get for data
           <%
                 data.each do |d|
                    puts d
                 end

           %>
     </body>
  </html>

So, leave the heavy lifting to the developer but let
the designer play too.

:P



__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free web site building tool. Try it!
http://webhosting.yahoo.com/ps/sb/