I would suggest moving the properties related to page navigation into a central object, a "model".
The model can be owned by the page or the Visit, and can be reached by all sorts of components, and be passed as a normal, in, parameter (nothing says you can't change properties of an in parameter). This is a very common Tapestry approach; it leverages all the good Tapestry stuff (rich objects, OGNL, real object parameters, etc.). -- [EMAIL PROTECTED] http://tapestry.sf.net > I am in what seems to be a strange situation that could benefit from an > "InOut" direction for parameter bindings.. which I don't think exists... > on the other hand I can't imagine how such a thing would work. > > The situation is that I have a component with a property (in this case > "currentPage") that includes a component for displaying google style > next-prev page navigation at the bottom. As such, the page navigation > component has it's own currentPage property. DirectLinks within the page > nav component change it's local currentPage property but these changes > need to be reflected in the parent component. Likewise, the opposite may > occur where the parent component changes it's currentPage property and > the page nav component must be aware of this. > > Should I implement a custom direction for this? Or is there a better > way? > > Thanks in advance. > > Luke Galea > Software Development > BlueCat <http://www.bluecatnetworks.com/> Networks > 905-762-5225 > > ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Tapestry-developer mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/tapestry-developer
