Howard wrote:
> My vision is to divide what is today the "component" into two pieces, > which (for the moment) I call the "peer" and the "resources". > The peer is a user supplied class, as today, but not needing to extend > from a Tapestry base class. > The component is a fixed implementation, private to Tapestry. Great stuff Howard, Get the public API right and you can decouple the framework from applications enough to make user upgrades straightforward even for quite significant internal changes. I hope you're planning to design the API in a "clean room" to be the best fit users' requirements then change the framework to fit the API. One of the most attractive features of Tapestry is component reuse, but this can sometimes be undermined (a bit, not a lot) by tight coupling with the framework, and by the fact that Tapestry constrains the way in which we can use inheritance and polymorphism in the bits we (users) write. Many of the most useful examples of java technologies are based around wholly abstract API's, with some boilerplate thrown in, IMHO it would be a big step forward for Tapestry to adopt this pattern too. Are you going to post your initial ideas about the basic entities, event model and component interfaces for us to give you feedback on? d. *************************************************************************** The information in this e-mail is confidential and for use by the addressee(s) only. If you are not the intended recipient (or responsible for delivery of the message to the intended recipient) please notify us immediately on 0141 306 2050 and delete the message from your computer. You may not copy or forward it or use or disclose its contents to any other person. As Internet communications are capable of data corruption Student Loans Company Limited does not accept any responsibility for changes made to this message after it was sent. For this reason it may be inappropriate to rely on advice or opinions contained in an e-mail without obtaining written confirmation of it. Neither Student Loans Company Limited or the sender accepts any liability or responsibility for viruses as it is your responsibility to scan attachments (if any). Opinions and views expressed in this e-mail are those of the sender and may not reflect the opinions and views of The Student Loans Company Limit ed. This footnote also confirms that this email message has been swept for the presence of computer viruses. ************************************************************************** --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
