I tried to steer clear of calling this a documentation "issue" in my post because I while this seems like a documentation problem I don't think more documentation is the answer because an Interface is really tied to the compiler and documentation is not. So it really does two things documentation cannot not do.
1. Provides a compiler enforced API to Taptestry. 2. Allows an IDE to perform code completion. But at the same time it does provide quick access to the documentation via IDE code completion. -- View this message in context: http://tapestry.1045711.n5.nabble.com/Would-it-be-possible-or-desirable-to-add-a-TapestryCoreServices-Interface-for-5-3-beta-tp4730424p4730728.html Sent from the Tapestry - Dev mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
