Finally, an approach to bring Spindle up to 2.4

Been spending some time on parsing and that's still valid stuff, but...

I have been avoiding the funky new way developers can place things in
Tapestry 2.4, bad me.

So, I have decided to approach this bottom up. What'll happen is that a new
Eclipse builder for Tapestry Projects
will be created. Won't be too useful in its initial form as that'll be the
testbed for finding all the locations for pages, templates and
then parsing the found stuff into a form Spindle can use.

The step after that will be somewhat more useful. A new plugin that'll form
the base for the New Spindle.
This plugin, which I might call SpindleBuilder, will be useful on its own as
a Tapestry project validator (sound familliar MB?).

Use case:

1. create a Java project, put whatever you like in it.
2. Add the Tapestry project flavour to the Java project. This will add the
builder.
If the project is an application and not a library, the tapestry project
flavour will require that the user designate a folder as the approot, and
one as the context root. ( a wizard or something).

3.Create, edit, tapestry artifacts. The builder plugin will incrementally
validate the Tapestry stuff and ignore the rest.

SpindleBuilder won't have any editors or such, as those will be provided by
the new Spindle.

New Spindle will build on this by adding better wizards, the editors and
such.

Geoffrey Longman
Intelligent Works Inc.




---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]