So:
<tr>
<td/><td/>
</tr>
<tr>
<td colspan="2"/>
</tr>
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 <gkucz...@gmail.com> 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 <td> component down
> (below the other two) via css styling.
>
> 2016-06-22 8:13 GMT+02:00 Chris Poulsen <mailingl...@nesluop.dk>:
>
> > 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 <gkucz...@gmail.com> 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?)
> > >
> > > <t:grid t:id="casesGrid" id="casesGrid" class="regular clear"
> > > source="casesDataSource" include="id, topic, date" row="currentCase"
> > > pagerPosition="none">
> > >
> > > - I tried putting the regular <p> inside the <t:grid> with
> > > currentCase.date value, but without having it in the include
> > parameter, but
> > > the grid ignores that and do not render the date value
> > >
> > > <p:idCell>${currentCase.id}</p:idCell>
> > >
> > > <p:topicCell>${currentCase.topic}</p:topicCell>
> > >
> > > <p>${currentCase.date}</p>
> > >
> > > - 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:
> > >
> > >
> > >
> > >
> >
>
