On 8/28/06, Hugo Palma <[EMAIL PROTECTED]> wrote:
Since Geoff decided to leave the Spindle project i've been thinking about the future of TapIDEA. As many of you know, TapIDEA is built on top of Spindle, which means "No Spindle" -> "No TapIDEA". There are several scenarios that can be put into account in the current situation, and after a long consideration here are my conclusions. Someone else picks up Spindle where Geoff left off: I honestly don't think this is going to happen. AFAIK Spindle was a one man project so no one else has the know how to quickly get into gear with the project. Some might think that that person could be me, and indeed i've become familiar with Spindle internals during the development of TapIDEA. But, there's the free time factor. I just wouldn't be able to find the time to do it. Still, if this scenario were to be become true, TapIDEA would live on.
I looked one day at Spindle source code and I don't know about its latest version but the spindle T3 is wicked. There is some very complex XML parsing code that seems to be used for reporting errors to eclipse. One thing about an IDE plugin is that I would be more than happy with a very basic plugin: - I can really live if the plugin doesn't do a complete check of the app. Even if the component parameters are not checked I'm fine... - What I like the most with spindle is the navigator on the right that shows all the components used in the page - basic html checking (and ognl friendly...) would be good to have. This is where spindle helps us the most. Eclipse web project has a very decent html editor... Maybe if I find spare cycles, I'll look to see how difficult it would be to add some basic tapestry abilities into the html editor. The other point about a plugin is to have an idea about its expectations. What are everyone's expectations on an IDE plugin? -- Henri Dupre Actualis Center
