"- project wizard that downloads all dependencies and create a ready to run project with a module builder, a configured web.xml and a Home page. - page creation wizard."
Can you say maven archetype? :-) On 1/29/07, Hugo Palma <[EMAIL PROTECTED]> wrote:
Actually, in this case less is more. T5 does need much less IDE support then T4, but what this means is that as an IDE plugin developer i can spend my time thinking of more ways i can improve the life of every Tapestry developer instead of figuring out all the quirks and rules for path resolutions and stuff like that. At this point, i've already got: - project wizard that downloads all dependencies and create a ready to run project with a module builder, a configured web.xml and a Home page. - page creation wizard. - syntax highlighting in component templates. - a visual palette that show all services in you module builder in a tree and let's you inject them in a component. And it extracts the documentation from the service class and shows it in a nice manner. Still a lot to be done and lot's of cool ideas in my mind. The really good news is that implementing this has been much much easier compared with supporting T4. Howard Lewis Ship wrote: > That's good news that you're working on support for T5 ... what kind > of support do you expect? I really think T5 will need much less > support than T4. > > Keep me posted on any issues you see w.r.t. to supporting of tooling. > > On 1/29/07, Hugo Palma <[EMAIL PROTECTED]> wrote: >> Here's what i know about Spindle for T4. Geoff split Spindle in two >> libraries, an IDE agnostic one that could be used by any plugin for any >> IDEA and the Eclipse plugin itself. I started using the IDE agnostic >> part in TapIDEA. I'd say that Geoff left about 80% of the work done. As >> far as the Eclipse plugin is concerned, i think it's in a much earlier >> stage of development, but i'm not really sure about this as i never >> looked at code. >> >> AFAIK, the Splindle project is dead until someone comes along and picks >> it up where Geoff left off. >> >> I don't want to steal the thread to TapIDEA, but just as a side note, >> i'm implementing TapIDEA for T5 and dropped TapIdea for T4 as i feel >> that by the time i got it right T5 would probably be out and running. >> And by the way, TapIDEA for T5 is coming out great :o) >> >> So, if anyone decides to pick up on Spindle, i'll gladly share my >> knowledge on the IDE agnostic library. In the meantime, i'll be focusing >> on TapIDEA. >> >> >> Dan Adams wrote: >> > So I'm one of those guys who in general thinks you shouldn't need >> > special IDE tools to work on your stuff (ala JSF) but at the same time >> > it would be really could if I could select a block of text in a >> template >> > and do "Extract component" or "Extract block". I know that development >> > on Spindle has stopped so I question is >> > >> > - would these kind of eclipse-refactoring-esque features be right for >> > spindle or a whole new plugin? >> > - what's the status of where spindle left off? >> > >> > >> >> > >
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
