The following statement is not completely true as it relates to me:
"However after one month's worth of experience with Tapestry, my understanding of Tapestry's inner workings cannot hope to match that of Howard and Geoff." Spindle is a tool that manipulates the XML files used by Tapestry. The XML files are clearly specified by Howard. The trick with Spindle is not knowing how all the internals of Tapestry work, but rather how to implement wizards and editors in Eclipse. I must admit that I have gained a good (not omnipotent) understanding of Tapestry by using it, rather than by building Spindle. If I were admit that I have a better understanding of something, its the Eclipse Platform and its plugin architecture rather than Tapestry itself. That's not a bad thing, I would love to learn more about Tapestry, especially how it is an excellent platform for building RAD tools. I expect that I will learn more as I work on our company's product (uses Tapestry). That said, I know nothing about building plugins for other IDEs. This is not a great revelation, I knew nothing about Eclipse when I started Spindle. But it was a lot of work to get going, work that my employer graciously paid for as they saw the value. Spindle is pretty much maintained in my spare time now, so there's little time left over for me to work on another plugin. As for the subscriber issue, too bad its not possible to track the lurkers. Geoff Geoffrey Longman Intelligent Works Inc. ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Tapestry-developer mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/tapestry-developer
