This is not a practical solution for the majority of web projects.

I don't know about majorities, but I do know about applications. bOP doesn't preclude using another templating mechanism. One solution we have used is to let the graphics folks generate their pages however they like. Once they get a design they like, we have them tag programmatically controlled elements, such as, "Login" or "Logout" or nav bars. We also have relied on style sheets to control thematic elements within the app.

I think it is important to address the issue of what controls the application. Most templating languages ignore this. Starting with the UI from a design perspective is fine. That's how we start most projects, and we build dummy models that load fake data. This allows us to prototype the workflow easily, and then we can fill in the business logic without changing the UI. BUT, what we don't do is let the UI guide the control flow. Our applications are task-centric, not page-centric (like JSP and many other toolkits). The advantage is that we can share business and presentation logic in interesting ways. You see an example of this in the petshop.bivio.biz where we reuse the logic for creating/editing accounts.

BTW, visit www.paintedsnapshot.com for an example of a graphics rich site that uses bOP. The artist and programmer were one in the same. The application was developed in a couple of weeks.

In reply to Re: Re: the trend of the presentation layer driving application logic by robnagler
in thread the trend of the presentation layer driving application logic by princepawn

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.