Nice! Thanks for sharing!
On Thu, Mar 24, 2022 at 10:56 PM Christopher Dodunski (Tapestry) <
chrisfromtapes...@christopher.net.nz> wrote:
> Hi Ben and Thiago,
>
> Thank you for your well considered suggestions on accommodating anchor
> points in returned pages. I've stored them away for possible
Hi Ben and Thiago,
Thank you for your well considered suggestions on accommodating anchor
points in returned pages. I've stored them away for possible future
use. I wound up solving the original problem in a rather different way,
using a RequireJS module.
Background: My web application has
On Mon, Mar 21, 2022 at 4:24 AM Ben Weidig wrote:
> Hi Chris,
>
Hello, Chris and Ben!
>- Allow an anchor at the end of the String, and set it
>PageNameComponentEventResultProcessor
>
You mean overriding the contribution to the ComponentEventResultProcessor
for the String.class key wit
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."
Hi Chris,
you're right, the returned String is used directly as the page name and
doesn't support any additions.
IMO, there are two options how to implement such a feature:
- Allow an anchor at the end of the String, and set it
PageNameComponentEventResultProcessor
- Use an intermed
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
particul
