Re: How to customize the grid to show three s in two rows?

[g kuczera]

I ended up using the loop in this way:



${message:title-label}
${message:content-label}




${currentObject.title}
${currentObject.content}


${currentObject.date}





${noObjectsMessage}


  




With the css styles based on the elements' types. Thanks guys for the help.

PS: In this case, especially the  tag was very useful - helped
me to use the hover style over the two rows at the same time.




2016-06-24 18:03 GMT+02:00 Norman Franke :

> It’s not meant to, but can. I add a new column for the special row via
> t:add=“special” or whatever. Then define that column in the grid:
>
> 
> 
> Some Content Here
> 
>
> I usually use CSS to hide that column, since you’ll end up with an empty
> column on the end. You can make it a real column, if desired, by just
> adding content after the first line. However, that confuses sorting since
> you have two columns inside of one.
>
> I typically use this for a description or long textual content. I usually
> wrap that in a  with CSS of white-space: nowrap; overflow: hidden; so
> it just truncates after the first line,
>
> -Norman
>
> > On Jun 22, 2016, at 3:50 AM, Chris Poulsen 
> wrote:
> >
> > 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 the
> cell.
> > The latter being the most "hackish solution" of the two, IMO.
> >
> > --
> > Chris
> >
> > On Wed, Jun 22, 2016 at 8:22 AM, g kuczera  wrote:
> >
> >> 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 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
>    rendering the page move it below the others (is that even possible?)
> 
>    source="casesDataSource" include="id, topic, date" row="currentCase"
>  pagerPosition="none">
> 
>    - I tried putting the regular  inside the  with
>    currentCase.date value, but without having it in the include
> >>> parameter, but
>    the grid ignores that and do not render the date value
> 
>  ${currentCase.id}
> 
>  ${currentCase.topic}
> 
>  ${currentCase.date}
> 
>    - the last one would be using the loop component, and put the values
>    inside divs, which can be easily moved around - it would mean for me
>    changing the casesDataSource (extended GridDataSource) to something
>    different, because the loop source cannot be feed with it
> 
>  What do you think is possible in this case?
> 
>  Here is the concept art:
> 
> 
>  ​
> 
> >>>
> >>
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
> For additional commands, e-mail: users-h...@tapestry.apache.org
>
>

Re: How to customize the grid to show three s in two rows?

[Norman Franke]

It’s not meant to, but can. I add a new column for the special row via 
t:add=“special” or whatever. Then define that column in the grid:



Some Content Here


I usually use CSS to hide that column, since you’ll end up with an empty column 
on the end. You can make it a real column, if desired, by just adding content 
after the first line. However, that confuses sorting since you have two columns 
inside of one.

I typically use this for a description or long textual content. I usually wrap 
that in a  with CSS of white-space: nowrap; overflow: hidden; so it just 
truncates after the first line,

-Norman

> On Jun 22, 2016, at 3:50 AM, Chris Poulsen  wrote:
> 
> 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 the cell.
> The latter being the most "hackish solution" of the two, IMO.
> 
> -- 
> Chris
> 
> On Wed, Jun 22, 2016 at 8:22 AM, g kuczera  wrote:
> 
>> 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 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
   rendering the page move it below the others (is that even possible?)
 
 >>> source="casesDataSource" include="id, topic, date" row="currentCase"
 pagerPosition="none">
 
   - I tried putting the regular  inside the  with
   currentCase.date value, but without having it in the include
>>> parameter, but
   the grid ignores that and do not render the date value
 
 ${currentCase.id}
 
 ${currentCase.topic}
 
 ${currentCase.date}
 
   - the last one would be using the loop component, and put the values
   inside divs, which can be easily moved around - it would mean for me
   changing the casesDataSource (extended GridDataSource) to something
   different, because the loop source cannot be feed with it
 
 What do you think is possible in this case?
 
 Here is the concept art:
 
 
 ​
 
>>> 
>> 


-
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org

Re: How to customize the grid to show three s in two rows?

[Chris Poulsen]

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 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 is just trying to recover the
> styles, which disappeared after replacing the t:Grid with t:Loop (it looks
> that tapestry automatically adds, after generating the html from t:Grid,
> the classes with the names of the columns eg. Some kind
> of topic).
>
> 2016-06-22 9:50 GMT+02:00 Chris Poulsen :
>
> > 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 the
> cell.
> > The latter being the most "hackish solution" of the two, IMO.
> >
> > --
> > Chris
> >
> > On Wed, Jun 22, 2016 at 8:22 AM, g kuczera  wrote:
> >
> > > 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 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
> > > > >rendering the page move it below the others (is that even
> > possible?)
> > > > >
> > > > >  > > > > source="casesDataSource" include="id, topic, date"
> row="currentCase"
> > > > > pagerPosition="none">
> > > > >
> > > > >- I tried putting the regular  inside the  with
> > > > >currentCase.date value, but without having it in the include
> > > > parameter, but
> > > > >the grid ignores that and do not render the date value
> > > > >
> > > > > ${currentCase.id}
> > > > >
> > > > > ${currentCase.topic}
> > > > >
> > > > > ${currentCase.date}
> > > > >
> > > > >- the last one would be using the loop component, and put the
> > values
> > > > >inside divs, which can be easily moved around - it would mean
> for
> > me
> > > > >changing the casesDataSource (extended GridDataSource) to
> > something
> > > > >different, because the loop source cannot be feed with it
> > > > >
> > > > > What do you think is possible in this case?
> > > > >
> > > > > Here is the concept art:
> > > > >
> > > > >
> > > > > ​
> > > > >
> > > >
> > >
> >
>

Re: How to customize the grid to show three s in two rows?

[g kuczera]

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 is just trying to recover the
styles, which disappeared after replacing the t:Grid with t:Loop (it looks
that tapestry automatically adds, after generating the html from t:Grid,
the classes with the names of the columns eg. Some kind
of topic).

2016-06-22 9:50 GMT+02:00 Chris Poulsen :

> 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 the cell.
> The latter being the most "hackish solution" of the two, IMO.
>
> --
> Chris
>
> On Wed, Jun 22, 2016 at 8:22 AM, g kuczera  wrote:
>
> > 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 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
> > > >rendering the page move it below the others (is that even
> possible?)
> > > >
> > > >  > > > source="casesDataSource" include="id, topic, date" row="currentCase"
> > > > pagerPosition="none">
> > > >
> > > >- I tried putting the regular  inside the  with
> > > >currentCase.date value, but without having it in the include
> > > parameter, but
> > > >the grid ignores that and do not render the date value
> > > >
> > > > ${currentCase.id}
> > > >
> > > > ${currentCase.topic}
> > > >
> > > > ${currentCase.date}
> > > >
> > > >- the last one would be using the loop component, and put the
> values
> > > >inside divs, which can be easily moved around - it would mean for
> me
> > > >changing the casesDataSource (extended GridDataSource) to
> something
> > > >different, because the loop source cannot be feed with it
> > > >
> > > > What do you think is possible in this case?
> > > >
> > > > Here is the concept art:
> > > >
> > > >
> > > > ​
> > > >
> > >
> >
>

Re: How to customize the grid to show three s in two rows?

[Chris Poulsen]

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 the cell.
The latter being the most "hackish solution" of the two, IMO.

-- 
Chris

On Wed, Jun 22, 2016 at 8:22 AM, g kuczera  wrote:

> 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 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
> > >rendering the page move it below the others (is that even possible?)
> > >
> > >  > > source="casesDataSource" include="id, topic, date" row="currentCase"
> > > pagerPosition="none">
> > >
> > >- I tried putting the regular  inside the  with
> > >currentCase.date value, but without having it in the include
> > parameter, but
> > >the grid ignores that and do not render the date value
> > >
> > > ${currentCase.id}
> > >
> > > ${currentCase.topic}
> > >
> > > ${currentCase.date}
> > >
> > >- the last one would be using the loop component, and put the values
> > >inside divs, which can be easily moved around - it would mean for me
> > >changing the casesDataSource (extended GridDataSource) to something
> > >different, because the loop source cannot be feed with it
> > >
> > > What do you think is possible in this case?
> > >
> > > Here is the concept art:
> > >
> > >
> > > ​
> > >
> >
>

Re: How to customize the grid to show three s in two rows?

[g kuczera]

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 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
> >rendering the page move it below the others (is that even possible?)
> >
> >  > source="casesDataSource" include="id, topic, date" row="currentCase"
> > pagerPosition="none">
> >
> >- I tried putting the regular  inside the  with
> >currentCase.date value, but without having it in the include
> parameter, but
> >the grid ignores that and do not render the date value
> >
> > ${currentCase.id}
> >
> > ${currentCase.topic}
> >
> > ${currentCase.date}
> >
> >- the last one would be using the loop component, and put the values
> >inside divs, which can be easily moved around - it would mean for me
> >changing the casesDataSource (extended GridDataSource) to something
> >different, because the loop source cannot be feed with it
> >
> > What do you think is possible in this case?
> >
> > Here is the concept art:
> >
> >
> > ​
> >
>

Re: How to customize the grid to show three s in two rows?

[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 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
>rendering the page move it below the others (is that even possible?)
>
>  source="casesDataSource" include="id, topic, date" row="currentCase"
> pagerPosition="none">
>
>- I tried putting the regular  inside the  with
>currentCase.date value, but without having it in the include parameter, but
>the grid ignores that and do not render the date value
>
> ${currentCase.id}
>
> ${currentCase.topic}
>
> ${currentCase.date}
>
>- the last one would be using the loop component, and put the values
>inside divs, which can be easily moved around - it would mean for me
>changing the casesDataSource (extended GridDataSource) to something
>different, because the loop source cannot be feed with it
>
> What do you think is possible in this case?
>
> Here is the concept art:
>
>
> ​
>

How to customize the grid to show three s in two rows?

[g kuczera]

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
   rendering the page move it below the others (is that even possible?)



   - I tried putting the regular  inside the  with
   currentCase.date value, but without having it in the include parameter, but
   the grid ignores that and do not render the date value

${currentCase.id}

${currentCase.topic}

${currentCase.date}

   - the last one would be using the loop component, and put the values
   inside divs, which can be easily moved around - it would mean for me
   changing the casesDataSource (extended GridDataSource) to something
   different, because the loop source cannot be feed with it

What do you think is possible in this case?

Here is the concept art:


​