> > Wow, you've just said that Tapestry, which is a web framework, should drop > the web framework (which is multipage), replace it with Vaadin/GWT (which > are single page) and focus on the IoC part only. I'm sorry, but I think > you're at least very confused about the above opinion
I probably am. But I think tapestry's *major* contribution is into the client part. I highly expect that this is wrong so please correct me if I am. What difference does it make if tapestry is a multi-page framework or a single-page one ? In Tapestry, writing a component is a very trivial thing to do. In > addition, you're using HTML directly, which isn't the case of Vaadin/GWT, > so you can very easily and quickly get some JavaScript > component/widget/whatever from jQuery UI, Scriptaculous or other projects > and turn it into a component when that's not provided by some project like > Tapestry-jQuery or ChennileKit. I totally agree. But I also hope I dive deep enough into tapestry to be able to do such things easily without showstoppers appearing at any point. I am developing a web application, ALL ALONE (small company), along with windows services (Tapestry IoC and Apache Daemon) and some 3rd line support from time to time and it's really hard to have time to go through tapestry code or the docs so I'm mostly just trying to get things done. Tapestry helps a lot but sometimes I just get stuck with trivial (mostly client-side related, components and tml) things that wouldn't take few minutes withing servlets\js. How much effort is needed to get some third-party package like > tapestry-jquery to work in Tapestry? Just add it to the classpath. If use > use some dependency management tool like Maven, Ivy or Gradle, just add the > dependency to the configuration and the tool will do it for you. If not, > download the JAR and configure your project to include it in your > classpath. It couldn't be easier or faster. Obviously I've used the wrong words again, I mean the integration part, like configuration files or whatever. Of course including a jar into my classpath shouldn't be a problem. On Mon, Aug 13, 2012 at 2:43 PM, Thiago H de Paula Figueiredo < thiag...@gmail.com> wrote: > On Sat, 11 Aug 2012 15:30:31 -0300, Muhammad Gelbana <m.gelb...@gmail.com> > wrote: > > I've never used Vaadin but what I can say about it after I visited it's >> website is that it's much more UI component rich when compared to >> tapestry but it has no IoC support. Of course the lack of UI components in >> t5 can be mitigated by using external libraries\frameworks but I'm >> comparing based on the OTB features >> > > From Tapestry side: > * Using HTML, CSS and JavaScript directly. > * Live class reloading > * You can change almost anything in the framework without needing to touch > its source: service override, advice, decoration. > * It's very easy and quick and painless to write new components. In GWT > and Vaadin, creating your own component which uses JavaScript is actually > discouraged: see the bottom of https://developers.google.com/** > web-toolkit/doc/latest/**DevGuideUiCustomWidgets<https://developers.google.com/web-toolkit/doc/latest/DevGuideUiCustomWidgets>. > My argument here is that there's no framework that will provide you 100% of > your component needs, so you'll eventually need to write your own and > you'll hope you have chosen a framework that makes it easy. > * Very high source code quality and test code coverage. > * You can use client-side-focused frameworks like GWT on the top of > Tapestry if you want or need. Someone has already done GWT on Tapestry. > Google it. > > And don't forget that Vaadin is basically GWT plus some server-side stuff. > > > that requires no efforts to import. >> > > How much effort is needed to get some third-party package like > tapestry-jquery to work in Tapestry? Just add it to the classpath. If use > use some dependency management tool like Maven, Ivy or Gradle, just add the > dependency to the configuration and the tool will do it for you. If not, > download the JAR and configure your project to include it in your > classpath. It couldn't be easier or faster. > > > -- > Thiago H. de Paula Figueiredo > > ------------------------------**------------------------------**--------- > To unsubscribe, e-mail: > users-unsubscribe@tapestry.**apache.org<users-unsubscr...@tapestry.apache.org> > For additional commands, e-mail: users-h...@tapestry.apache.org > > -- *Regards,* *Muhammad Gelbana Java Developer*
