Good people,

I am involved in a project that has adopted Tapestry over Struts as the
MVC.  I am developing the page mockups and handing them off to the
developers.  There are three main "states" or views of the application
containers.  One with a center content region and left and right panels.
The metaphor for closing the panels is a vertical dividing line with an
arrow graphic.  When an arrow is clicked on an open panel, the request to
the server brings back a view with the panel closed, or open, depending on
the state when selected.

Without graphics, it's a bit hard to emulate this in text, but here goes...

Left Panel Open <-- Center Content Region --> Right Panel Open

Action: Click Left Arrow

Result:
--> Center Content Region --> Right Panel Open

Okay, so you probably have the idea by now.  Here is what is being
developed on the back-end:

Each page is being dynamicaly generated as what is being called "The
border".  All the code for this generation is contained within a servlet
class, in effect placing the html in a class that responds to the user
action of opening or closing panels.  The result works very well except
there is one thing bugging me that I hope someone can clear up.  If
Tapestry is indeed a component framework, then are we making a mistake by
creating the largest presentation layer as a dynamic object?  I thought the
way this should play out would be for there to be three html files for
three states of the application.  Based on this design, if a presentation
change is called for, the html is modified, the L&F is approved, (heads
nod, smiles all around) and then the developer finds exactly where I made
that change, and copies and pastes it into his servlet at just the right
spot.  The presentation cannot be viewed in an HTML editor because the
presentation might as well be in a JSP object.  What's wrong whith this
picture?  It it my understanding of Tapestry?

I await your learned reponse...


Curtis Fisher
Contractor


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to