Re: t:grid coercing value when it shouldn't

2022-01-31 Thread Thiago H. de Paula Figueiredo
On Sat, Jan 29, 2022 at 8:13 PM Jonathan Meijer wrote: > Thank you to both for your replies. > My pleasure to help! > After reading and rereading the documentation, I'm getting a much better > understanding of how (and how not) to use Tapestry. > Tapestry does have some concepts you need to

Re: t:grid coercing value when it shouldn't

2022-01-29 Thread Jonathan Meijer
Thank you to both for your replies. After reading and rereading the documentation, I'm getting a much better understanding of how (and how not) to use Tapestry. I'm trying to integrate with Cayenne without using the outdated integration module, and so far it's going well and I figured out my way

Re: t:grid coercing value when it shouldn't

2022-01-27 Thread Thiago H. de Paula Figueiredo
On Fri, Jan 21, 2022 at 12:56 AM Jonathan Meijer wrote: > Hi, > Hi! > New Tapestry user here, started with a bootstrapped 5.7.3 and > experimenting. > Welcome to Tapestry! We just released 5.8.0, by the way. > Delete > I suggest using EventLink instead of ActionLink. Very similar, but

Re: t:grid coercing value when it shouldn't

2022-01-20 Thread Volker Lamp
Hello Jonathan New Tapestry user here, started with a bootstrapped 5.7.3 and experimenting. > Welcome + enjoy! > What am I doing wrong? There is really no room for error, the Blah class > is defined right there in the same class and the current row object has > absolutely no reason to be

t:grid coercing value when it shouldn't

2022-01-20 Thread Jonathan Meijer
Hi, New Tapestry user here, started with a bootstrapped 5.7.3 and experimenting. I tried to follow the grid example https://tapestry.apache.org/current/apidocs/org/apache/tapestry5/corelib/components/Grid.html quite literally, however I had issues with coercion, so I simplified to try to root