Re: The "Presentation" Layer

["Aaron Bartell" <aaronbartell@xxxxxxxxx>]

> I guess my point is that there's a natural tendency to blend everything
together.  Even though you try not to.  And I may not be able to pinpoint a
specific example, but I suspect there are a number of major vendors and
players in the UI widget market that have combined UI layout with data
validation and formatting, and mapping with data stores, into one component.

And maybe to jump on their side, it can *sometimes* be right if it proves to
create quick application development that is also easy to maintain
longterm.  The contrast to separation of concerns is leaky abstraction which
isn't bad all the time (http://en.wikipedia.org/wiki/Leaky_abstraction).
For example, I have a lot of my DAO's (Data Access Objects) make their way
to the View layer even though a purist might say you should never allow an
object based on a table to make it's way to the View.

Anyhoo, so many terms, so little time to read about them :-)  BTW, these are
terms I HAD to take an interest in because of JSF's flaws (of which I have
commented on here in the forums a number of times).

Aaron Bartell
http://mowyourlawn.com