Very true; I started to see which fields should be made more visible and so far I don't see any. I really think this will be used to make it easier for user pages to work together, and some components will be built for extensibility and expose the necessary fields.
On Fri, Dec 23, 2011 at 2:23 PM, Kalle Korhonen <[email protected]> wrote: > On Fri, Dec 23, 2011 at 10:07 AM, Howard Lewis Ship <[email protected]> wrote: >> I have working tests inside Plastic; I'm about to convert a lot of >> component fields from private to protected, which will make extending >> existing Tapestry components a lot easier, as there will be reasonable >> access to parameters defined in base classes. > > The changes in plastic are great, but please carefully consider each > case before changing component fields from private to protected, as > they will become part of the API and thus need to be maintained. A > positive side effect of making it difficult to extend components is > that it has also forced people to think more about composition and to > copy and modify some built-in components rather than extending them. > > Kalle > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > -- Howard M. Lewis Ship Creator of Apache Tapestry The source for Tapestry training, mentoring and support. Contact me to learn how I can get you up and productive in Tapestry fast! (971) 678-5210 http://howardlewisship.com --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
