--- Hugo Palma <[EMAIL PROTECTED]> wrote:
> Those simple features you mention are not so difficult to implement and i > could easily provide those in TapIDEA without Spindle. Still, when i think > of Tapestry ÎDE support i think of something much more complete and feature > rich like what Spindle for T3 provides. It was and is TapIDEA's goal to > provide such functionality to IntelliJ users. > Don't let the best be the enemy of the good. What I mean by that is if someone just starts creating a new Tapestry plugin that just does a few simple things with clearly written code (comments!). It makes it possible for others to add their own desired features. I, for one, would like to learn a little bit about how eclipse plugins work by helping out. But I don't have the time to learn the plugin architecture, rewrite spindle *and* do my main work. I would also suggest that someone more knowledgeable post what areas of Tapestry are *least* likely to change in T5 and what areas Howard plans on sucking into the main code base. For example, my earlier question about ognl's use in T5. Clearly there is no need for the plugin to help with ognl expressions as ognl use is going to be deprecated. Another example is specification xml file parsing. I don't use the XML files at all now that I have the annotation mechanism. Once we know what areas are going to last into T5, then we can chose a small set of plugin features that are likely to be useful in both T4.1 and T5 -Pat --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
