Just to clarify, SPI definitely stands for Service Provider Interface. Read Howard's blog post on the subject: http://tapestryjava.blogspot.com/2012/10/zeroing-in-on-tapestry-54.html
+1 for the @ClientEvent proposal On Sat, Oct 27, 2012 at 2:54 PM, trsvax <[email protected]> wrote: > > - Service Provider Interface? > > - Script Programming Interface? > > - Single Page Interface? > > It does seem a definition would be nice. I would say #1 also because I > think > the API spills over into the Java side. For example the current javascript > deals with initializing the client side of components and there are Java > interfaces into that. I'd prefer a switch to the data attribute style > initialization and I don't think that would require any Java side support > and very little client side support. > > I would like to see Java interfaces for client events. Perhaps > > @ClientEvent(event="pageload") > Object onPageLoad() { > } > > I think the Javascript part should be moved to it's own module and you pick > the one you want. The ones that I'm interested in are > > 1. Prototype which works likes (is) the current one > 2. jQuery > > The other tricky part not currently mentioned is what does the HTML > generated by the components look like? If there is a switch to Bootstrap > the > HTML needs to change. Also what happens to things like Calendar and and > even > the other form components. Bootstrap/jQuery have their own mechanism for > handling validation. Will Tapestry use the "native" one or roll it's own? I > would hope the "native" one. > > In summary I think the client side support should be a separate module. I > can see the need for more than one just like JPA/Hibernate/roll your own. > > Given that is there a third provided client module and if so what is it? > > > > > -- > View this message in context: > http://tapestry.1045711.n5.nabble.com/Abstract-layer-or-jquery-all-the-way-tp5717250p5717339.html > Sent from the Tapestry - Dev mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
