On Mon, Mar 21, 2022 at 1:34 AM Christopher Dodunski (Tapestry) < chrisfromtapes...@christopher.net.nz> wrote:
> Hi, > Hi! > Quick question: Tapestry is flexible when it comes to return types for > page navigation. "When a string is returned, it is expected to be the > logical name of a page." Although I've not tried it, presumably this > means the likes of "Index#footer" isn't possible for navigating to a > particular place in a page. Is creating a 'Link' object along with > setAnchor() the usual/only approach for achieving this from within a > page's class? > Right now, out of the box, yes, it's the usual and only approach. Of course, you can always create your own return type and corresponding ComponentEventResultProcessor to tell Tapestry how to handle it and have any logic you want. > > Thanks & regards, > > Chris. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > > -- Thiago
