Agreed. Here's an example of creating a binding heavily based on the prop:
binding.
http://tapestry-stitch.uklance.cloudbees.net/mapbindingdemo
On 21 Mar 2014 13:02, "Thiago H de Paula Figueiredo"
wrote:
> On Fri, 21 Mar 2014 06:22:32 -0300, Guillaume Bodet
> wrote:
>
> Hi all,
>>
>
> Hi!
>
>
On Fri, 21 Mar 2014 06:22:32 -0300, Guillaume Bodet
wrote:
Hi all,
Hi!
Any idea where I should start?
I think you're looking at the wrong part of Tapestry for the solution. I
think the best solution would be to implement a new binding that would be
heavily based on the prop one Tape
uses an
unknown property (i.e. ${foo.bar}, where foo or bar do not exist). I would
like to build a dynamic property conduit to handle this (this could work
either like a universal property provider within a component, or as a
“missing_property” fallback, similar to the “missing_method” method in
ruby
