On Wed, 22 Jun 2016 11:58:23 -0300, Lherm Nicolas wrote:
In my app.tml I put an that refers to
my app.java to :
void onSetupRender() {
environment.push(EnumCorgamo.class, corgamo);
}
but it still doesn't works
That's because the corgamo variable is null
In my app.tml I put an that refers to my
app.java to :
void onSetupRender() {
environment.push(EnumCorgamo.class, corgamo);
}
but it still doesn't works [☹]
De : Lherm Nicolas
Envoyé : mercredi 22 juin 2016 16:04:09
À : Tapestry users
Objet : RE:
Hi,
EnumCorgamo is the context of the execution, an enumeration with some Strings,
and methods thats returns codes (strings)
Yes, it was Tapestry 5.2.6 [?]
De : Thiago H de Paula Figueiredo
Envoy? : lundi 20 juin 2016 19:45:28
? :
You should checkout the tapestry source (Grid, GridRows and friends) to see
how the output is generated.
--
Chris
On Wed, Jun 22, 2016 at 12:50 PM, g kuczera wrote:
> Thanks for the idea, Chris. I was going to make the table with styled divs
> and t:Loop, but much better
Thanks for the idea, Chris. I was going to make the table with styled divs
and t:Loop, but much better option is to create it with the regular table
syntax, but having two rows - just like you mentioned - inside the t:Loop.
So you saved me a lot of time.
PS: I already have it tested, so the rest
So:
For each row.
The grid is not meant to handle something like that.
You can roll your own component(s) to render what you need (using loop
etc.) or add an extra cell as a regular grid cell and then use a mixin to
manipulate the html of the grid to introduce a new row containing
Sorry, the image was not embedded correctly. Here is the link:
http://i.imgur.com/OlnNVBn.png
(two headers before, three headers after).
Now I am examining if it's possible to move the third component down
(below the other two) via css styling.
2016-06-22 8:13 GMT+02:00 Chris Poulsen
Your post seems incomplete, so it is not clear to me, what you are trying
to do.
--
Chris
On Wed, Jun 22, 2016 at 8:05 AM, g kuczera wrote:
> Currently I got a request to add another visible column to the table (grid
> component), but the request was for it to be placed
Currently I got a request to add another visible column to the table (grid
component), but the request was for it to be placed below the rest. What do
you think the best approach would be in this case? I see three of them:
- add the mentioned column in the *include* parameter and after