|
Posted by David Haynes on 06/20/06 22:19
Chung Leong wrote:
> msch-prv@bluewin.ch wrote:
>> Would such an approach be more efficient that the traditional
>> line-by-line approach wrt. debugging, maintenance, etc. ? (I really
>> dread mixing php and html.). While I like Smarty's templating approach,
>> it seems Smarty still requires linear coding to do code translation.
>
> That approach sounds good in theory but I've found it doesn't work very
> well in practice. User interface tend to require a lot of little
> tweaks, sometimes to work around browser difference (layout quirks,
> etc.), sometimes just be make things look aesthetic pleasant.
> "Shimming" a page, as some might call it. At times it's hard enough to
> get one page to look right, let alone trying to make the same piece of
> HTML work in multiple locations. A lot depends on how tight a design is
> visually. When it's unforgiving, you want to give yourself more
> flexibility.
>
Chung:
I was thinking about this at a finer-grained level than you seem to be
in that I was thinking that msch-prv was thinking of automating the
common HTML elements rather than doing something more complex.
While I agree that some sites required a lot of "shimming", those are
also the sites that fall over with every browser upgrade and/or page resize.
Do you think that, say, wrapping <select>, <img> or the various <input>
tags in functions is really going to lead to big layout issues? It seems
to work well enough in the JSP/JSF space...
-david-
Navigation:
[Reply to this message]
|