Hi,
in my scenario I used something like this:
Code:
<t:gridcol id="g_13" sortreference=".{sortInformation}" text="..." >
<t:pane id="g_14" padding="left:0;right:0;top:0;bottom:0" >
<t:row id="g_15" >
<t:label id="g_16" font=".{font}" text=".{information}" />
<t:label id="g_17" font="weight:bold" text=".{additionalInformation}" />
</t:row>
</t:pane>
</t:gridcol>
The sortreference attribute allows me to define how this multi-cell-column can be sorted.
Unfortunately, searching on this column is not possible.
My workaround now is (thanks to Björn Müllers hints) to go back to something like this:
Code:
<t:gridcol id="g_13" sortreference=".{sortInformation}" text="..." >
<t:label id="g_16" font=".{font}" text="<html>.{information} <b>.{additionalInformation}</b></html>" />
</t:gridcol>
Something like means that the putting together of the String with the html-Tags happens in the code and is exposed via Getter to the JSP.
Now everything works alright, but I still don't like it. It just doesn't look clean to me (I needed to put html tags and String concatenation into the Java code to make this work). Does the definition of the font-attribute even work if the content of the text-attribute is html?
If we had something like searchreference, data and presentation could be separated more clearly if we could let be this html stuff.
If that feature were in CaptainCasa, that would be great.
Thanks,
Björn