While http://tapestry.apache.org/service-status.html is useful for debugging I don't think it's a good idea to use it as the list of services because there are internal ones as well as public ones listed and that's where the trouble starts.
I do agree about having lots of code completions but what are you going to do? And why does java.awt.List keep showing up even though I've never picked it on purpose. But worst of all why are there 15 loggers and sl4j is always at the bottom. Coding is hard I think I'll go to lunch :) Interesting discussion. I'm not sure how well it would work either but I don't really see any downside. Perhaps I'll make one and put it on GitHub. -- 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-tp4730424p4731782.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]
