> From: Nicola Ken Barozzi [mailto:[EMAIL PROTECTED]]
> :-/ Me too. > This reuse-but-not-quite situation *sucks* *big* *time*. > > Let's make reuse a reality. A word of warning. Avalon facilitates the machinery to make reuse really easy. However, in order to truly support reuse, the design philosophies of the two projects have to be aligned. For instance, SourceResolver, DataSourceComponent, and some of the other Excalibur components are generic enough because they have been used in more than one project. Because of that they have a sufficient abstraction that makes them compatible with a number of projects. Some components are simply too application specific to re-use. That's ok. You have to evolve your component definitions by incorporating how they work into at least three projects to find an abstraction that works 90% of the time. You are doing *really* well if you achieve 70% reuse. The problem that corporations and many other projects realize is that reuse costs a lot of time and resources to get it done. For that reason some things are doomed to be repeated. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
