On Mon, 09 Mar 2015 20:45:30 -0300, Daniel Jue wrote:
Hi,
Hi!
There were a couple ways I thought of doing this but they all seemed to
fight Tapestry's static structure paradigm.
Let's see. :)
The first way would be to let the customer completely define the search
results page and tml, a
Perhaps you could use display blocks like the beaneditor/grid etc. does.
--
Chris
On Tue, Mar 10, 2015 at 12:45 AM, Daniel Jue wrote:
> Hi, I have a reusable war overlay project where the omnipresent search bar
> component is in a layout and search results page is defined in a core
> library (
Hi, I have a reusable war overlay project where the omnipresent search bar
component is in a layout and search results page is defined in a core
library (These are hooked together via @InjectPage in the search bar
component so i can set the page's parameters and then send the user there)
The searc
