'why is there no maxsize parameter whose value is dictated by the database constraints?'
Because templating systems are meant to remove all application/business logic and just focus on the appearance and presentation.

This tends to be most useful as if you do put anything other than a few variables an html in templates designers tend to break it/not understannd it/mash it with a graphical html editor. with html I think there are 2 real life approaches

1. You give them(designers) very basic templates to add their graphics and html to.
2. They give you a design and you plug it in (more work for programmer but less chance of having to fix things)

Generally if you mix code and html it's a lot harder for the designer than if you give them a template.

As for XML and XSLT thats probably the way forward but I ain't tried it yet. In general I don't think designers should be able to see any of the presentation logic or affect any html that the appliocation is dependent on. This is especially dependent on the knowledge of the designer and mainly true if designers don't understand javascript or html forms. Interesting how many diff ways to do this kind of thing seem to emerge.

2006-06-21 Retitled by holli, as per Monastery guidelines
Original title: 'Separation'

In reply to Separation of Presentation and Application/Business Logic by hakkr
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.