Hi Thiago,
I didn't want to argue with you, just wanted to explain my opinion (and
understand yours). I can accept the decision to stay with private
methods althought I do not agree with you reasons ^^
I'll continue to discuss smaller changes (in behaviour) here.
Kind regards,
Michael.
Tapestry internal service implementations and all services (unless
stated otherwise, as Autocomplete) were written with the assumption
that they won't be subclasses. They're not part of the public API and
shouldn't be used directly. Period.
Why don't you post here what changes of behavior you want to be done
in Tapestry sources and, if we all agree, have it done in the source
code itself instead of asking us for something too broad as changing
methods and fields visibilities?
--
Mit freundlichen Grüßen / Kind regards
Michael Wyraz
evermind GmbH
Schorlemmerstraße 1
04155 Leipzig
Tel.: +49 (0)341-25 39 66 - 0
Fax: +49 (0)341-25 39 66 - 1
Funk: +49 (0)177-73 00 00 3
E-Mail: michael.wy...@evermind.de
HRB: 21586
Amtsgericht Leipzig
Geschäftsführer:
Christoph Klemm
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org
For additional commands, e-mail: dev-h...@tapestry.apache.org
