On Mon, 16 Jun 2014 05:17:43 -0300, Nourredine K. <nourredin...@gmail.com>
wrote:
Hi Thiago!
Hi!
Nice feature! Simple but very useful. Thanks you.
:)
Just a thought. What about multiple contributions to the
ComponentReplacer
for the same page/component or mixin ?
They would work in the same way every MappedConfiguration would: use
configuration.override() instead of configuration.add().
In a next improvement, it could be very handy to allow some kind of
ordered configuration.
I thought about it, but then I couldn't find a good scenario in which
there would be more than a replacement for the same page, component or
mixin. If you think of some, please let me know. I imagine this new
feature/service to not be used often. Making it an ordered configuration
would make contributions to it harder with almost no.
Changing it from MappedConfiguration to OrderedConfiguration would be a
backward-compatible change so, if you want to present some compelling
reason to do it, please do it quickly, so we can implement the change
before 5.4 final is released.
--
Thiago H. de Paula Figueiredo
Tapestry, Java and Hibernate consultant and developer
http://machina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org
For additional commands, e-mail: dev-h...@tapestry.apache.org
