These are good points, and HTML5 compatibility will be important. I think we'll see an @HTML5 annotation for pages that converts them to use HTML5 output rules ... but there's more than that, such as training the validators to write HTML5 attributes for validation (fortunately, that is supported in the APIs!).
On Fri, Dec 3, 2010 at 3:47 PM, Katia Aresti <[email protected]> wrote: > Hi, > > This post exists since October, but I would like to send now my feedbak as > the website is now published and this thread is talking about homepage > content. > > > *1 ) Tapestry is ... agile* > > Easy to code,* easy to test,* easy to deploy. Tapestry encourages you to > work in* small increments *with immediate feedback so you are always making > fast, forward progress. *Want to code in Groovy or Scala instead? *No > problem! " > > *> Easy to test, small increments *: this is related with agility > indirectly, but directly with the testability and embraces TDD techniques > we > try to introduce on software development projects. I would rather place > this > into * > Suggestion : ''Tapestry is test focused' or "testable".* I don't know which > could be the best way to express this in English. Will be nice to point to > tapestry covertura results too. > > *> Groovy, Scala* I would rather place this into *"Tapestry is polyglot". > * > IMHO, the agility term is not bad but I think it might be overused and not > really related to the functionalities we are trying to describe on this > part. I fell it as if we said: "Tapestry is cloud computing". Yes, it is > ... we deploy tapestry applications on the cloud if we want to ... > > *2 ) Tapestry is ... scalable* > > After Matt Raible's talk, and Igor's answer, and Matt's matrix updated, I > realized he didn't change his "scalable 0.5" to "1", even if as we say here > : Tapestry is scalable. Well, this is Matt Raible, and honestly before and > while writing this mail I've been hardly trying to understand how and why > he > decides scalability degrees for each web framework. I fell he is not being > coherent on his matrix for this point. If somebody would like to discuss it > fell free to send me an email. > * > Suggestion : 3 ) Tapestry is ... REST ? * > > Tapestry is one of the first java web frameworks that integrates easily > with > REST architectures, despite of being component oriented. I say despite of > because I listen people saying - Matt Raible for example - as if action > oriented fw are more suitable for WWW rather than a component oriented fw. > I > don't think this applies to tapestry. > > Tapestry is able to let us develop 99% stateless and rest applications for > WWW, but very stateful ones if we needed too. I think this point is not > well > enough explained on documentation (correct me if I'm wrong). > I'm suggesting to directly talk about REST Architecture on the front page > too. I consider this point very important to be highlighted now that REST > architecture design paradigms are finally starting to reach enterprise > development too. > > Finally, I would like to say that would be nice to add two more entrys on > the very near future. These two I consider them to be crucial for the > project health and future in order to convince new customers, new > developers > and new comers to join and to use tapestry : > *- Tapestry is ... HTML5 compatible* > - *Tapestry is ... your favourite JavaScript library* > > Katia > > 2010/10/15 Howard Lewis Ship <[email protected]> > > > > Thanks for the comments ... yes a breakdown like that would be nice. > > Tapestry for Project Leaders (3 or so high-level entries) vs. Tapestry > > for Web Developers (the remainder). > > > > On Thu, Oct 14, 2010 at 2:25 PM, Sebastian Hennebrueder > > <[email protected]> wrote: > > > What do you think about a 2-3 short messages to non or less technical > people > > > and then some messages to softwaredevelopers > > > > > > Tapestry is ... a web framework for Java > > > > > > Tapestry provides all features you need to write a complete web > application > > > with or without use of Ajax. Tapestry applications are normally written > in > > > Java, the most popular > > > enterprise applications development language but you may use Groovy and > > > Skala as development language as well. > > > > > > Tapestry is ... highly productive > > > > > > Tapestry embraces convention over configuration, which means little or > none > > > configuration effort. It is based on components which allows heavy > reuse > of > > > elements in other pages. It supports hot class reloading. Just change a > > > class and reload the browser page. > > > > > > Tapestry is ... scalable > > > > > > Tapestry works well for everything from small web applications with > just a > > > couple of pages, to large web applications with hundreds or even > thousand of > > > pages. It scales great on a single server but its runs perfectly on > > > clustered servers or cloud environments. > > > > > > Tapestry more technically > > > > > > Tapestry is ... agile > > > > > > Easy to code, easy to test, easy to deploy. Tapestry encourages you > > > to work in small increments with immediate feedback so you are > > > always making fast, forward progress. It helps you fixing problems > with > > > incredible detailed error messages. Want to code in Groovy or > > > Scala instead? No problem! > > > > > > Tapestry is ... fast > > > > > > Tapestry is pure Java. It doesn't use Java reflection, and is built > > > to cleanly support large numbers of threads. Better yet, it > > > automatically includes standard performance-enhancing strategies for > web > > > application such as GZip content compression, JavaScript aggregation, > and > > > far future > > > expires headers ... all techniques to cut down on the size > > > and number of requests. > > > > > > Tapestry is ... productive > > > > > > Code and templates are lean and mean. LIve class reloading means > > > that the time between seeing an error and providing the fix > > > is seconds, not minutes. Advanced exception reporting gives you all > > > the tools you need to fix your problem: not just > > > a stack trace, but every bit of information you need to know about > > > what Tapestry was doing and why it was doing it. > > > > > > Tapestry is ... scalable > > > > > > Tapestry scales up big on a single server, but also gives you great > > > options for when you need to switch to a cluster. Tapestry makes > > > it easy to store information on the client (as hidden fields or > > > query parameters) or on the server (in the session). > > > > > > Tapestry is..based on components > > > > > > Tapestry is based on components and templates > > > Tapestry applications consist of pages and components. Components > > > are easy to write, and hook together easily ... components > > > can contain other components. Templates are either written with HTML > or > XML > > > and are easy to read and to change by web developers and designers. > Tapestry > > > does > > > all the "dirty plumbing" to connect your components and pages. > > > > > > Tapestry is ... adaptable > > > > > > Tapestry's architecture is open and extensible. You need to integrate > other > > > technologies for your business logic (Spring, EJB), input validation > (Bean > > > validation)? Tapestry provides you with many hooks to integrate your > > > preferred libraries. There are already many integrations for popular > > > technologies. And even better: You don't like how > > > Tapestry does something? There's a clean way to add your own > > > logic, or substitute some of Tapestry's logic with your own. Tapestry > > > modules make it easy to create components and package them > > > for reuse in your current application, or across many applications. > > > > > > Tapestry is ... international > > > > > > Tapestry has built-in support for more than a dozen different > > > languages, and makes it easy for your application to cleanly > > > support multiple localizations. Tapestry automatically tracks the > > > user's preferred locale and makes it easy to access > > > user-localized messages across the entire application. > > > > > > Tapestry is ... dependable > > > > > > Tapestry's roots go back to 2003 as an Apache project, and even > > > earlier as an open-source projects. Thousands of applications > > > run on Tapestry, including high-throughput sites like SeeSaw.com. > > > Tapestry applications have a history of running glitch-free. > > > > > > Tapestry is ... fun > > > > > > Tapestry removes the tedium of developing web applications, leaving > > > just the fun parts. Tapestry keeps you "in the zone", having > > > fun and coding up a storm! Tapestry: code less deliver more! > > > clusters a lone developer working on > > > an application with just a couple of pages, > > > all the way up to large teams and applications with hundreds of > > > pages and custom components. For big teams, Tapestry's > > > pages and components design keeps the efforts of different > > > developers automatically integrated. > > > > > > > > > Best Regards > > > > > > Sebastian > > > > > > > > > > > > > > > I think that 'Tapestry combines > > >>> simple Java classes with straight-forward templates to form > > >>> components and pages ' > > > > > > is hard to understand. > > > > > > > > > > > > Am 12.10.10 22:48, schrieb Christian Gruber: > > >> > > >> +1. If we can have some jazzy JS/CSS magic that makes the "words" > appear > > >> but then shows the additional explanations on hover or some other nice > way, > > >> that'd be slick. But frankly I like the content. > > >> > > >> Christian. > > >> > > >> On Oct 12, 2010, at 4:22 PM, Howard Lewis Ship wrote: > > >> > > >>> Tapestry is ... a web framework for Java > > >>> > > >>> Tapestry applications are written in Java, the most popular > > >>> enterprise applications development language. Tapestry combines > > >>> simple Java classes with straight-forward templates to form > > >>> components and pages and takes care of all the > > >>> "ugly plumbing" of a typical web application. Tapestry embraces > > >>> convention over configuration, which means no > > >>> XML configuration. > > >>> > > >>> Tapestry is ... component based > > >>> > > >>> Tapestry applications consist of pages and components. Components > > >>> are easy to write, and hook together easily ... components > > >>> can contain other components. Tapestry always has an overall map of > > >>> your application, because it knows all the pages > > >>> and all the components within the pages ... this lets Tapestry do > > >>> all the "dirty plumbing" of web application development. > > >>> > > >>> Tapestry is ... scalable > > >>> > > >>> Tapestry works well for everything from a lone developer working on > > >>> an application with just a couple of pages, > > >>> all the way up to large teams and applications with hundreds of > > >>> pages and custom components. For big teams, Tapestry's > > >>> pages and components design keeps the efforts of different > > >>> developers automatically integrated. > > >>> > > >>> > > >>> On Tue, Oct 12, 2010 at 12:16 PM, Christian Gruber > > >>> <[email protected]> wrote: > > >>>> > > >>>> I'm thinking the basic "a web-UI framework for Java" might be useful > for > > >>>> the "stating the obvious" department. > > >>>> > > >>>> But some people coming to the site may not actually get that > context, > if > > >>>> they're journalists or managers looking at platforms. Probably need > to make > > >>>> some sort of really hyper-obvious statement that categorizes its > niche. > > >>>> > > >>>> Christian. > > >>>> > > >>>> On Oct 12, 2010, at 2:58 PM, Howard Lewis Ship wrote: > > >>>> > > >>>>> Actually, I'm not happy with the "dependable" section. That one > needs > > >>>>> some love. > > >>>>> > > >>>>> On Tue, Oct 12, 2010 at 11:52 AM, Joachim Van der Auwera > > >>>>> <[email protected]> wrote: > > >>>>>> > > >>>>>> Great... > > >>>>>> > > >>>>>> On 10/12/2010 08:26 PM, Howard Lewis Ship wrote: > > >>>>>>> > > >>>>>>> For the home page, I kind of see the need for a section "What is > > >>>>>>> Tapestry?" > > >>>>>>> > > >>>>>>> Here's my first pass: > > >>>>>>> > > >>>>>>> What is Tapestry? > > >>>>>>> > > >>>>>>> Tapestry is ... agile > > >>>>>>> > > >>>>>>> Easy to code, easy to test, easy to deploy. Tapestry > encourages > > >>>>>>> you > > >>>>>>> to work in small increments with immediate feedback so you are > > >>>>>>> always making fast, forward progress. Want to code in Groovy > or > > >>>>>>> Scala instead? No problem! > > >>>>>>> > > >>>>>>> Tapestry is ... fast > > >>>>>>> > > >>>>>>> Tapestry is pure Java. It doesn't use Java reflection, and is > built > > >>>>>>> to cleanly support large numbers of threads. Better yet, it > > >>>>>>> automatically includes standard performance-enhancing > strategies > > >>>>>>> such > > >>>>>>> as GZip content compression, JavaScript aggregation, and far > future > > >>>>>>> expires headers ... all techniques to cut down on the size > > >>>>>>> and number of requests. > > >>>>>>> > > >>>>>>> Tapestry is ... productive > > >>>>>>> > > >>>>>>> Code and templates are lean and mean. LIve class reloading > means > > >>>>>>> that the time between seeing an error and providing the fix > > >>>>>>> is seconds, not minutes. Advanced exception reporting gives you > all > > >>>>>>> the tools you need to fix your problem: not just > > >>>>>>> a stack trace, but every bit of information you need to know > about > > >>>>>>> what Tapestry was doing and why it was doing it. > > >>>>>>> > > >>>>>>> Tapestry is ... scalable > > >>>>>>> > > >>>>>>> Tapestry scales up big on a single server, but also gives you > great > > >>>>>>> options for when you need to switch to a cluster. Tapestry makes > > >>>>>>> it easy to store information on the client (as hidden fields or > > >>>>>>> query parameters) or on the server (in the session). > > >>>>>>> > > >>>>>>> Tapestry is ... adaptable > > >>>>>>> > > >>>>>>> Tapestry's architecture is open and extensible. Don't like how > > >>>>>>> Tapestry does something? There's a clean way to add your own > > >>>>>>> logic, or substitute some of Tapestry's logic with your own. > > >>>>>>> Tapestry > > >>>>>>> modules make it easy to create components and package them > > >>>>>>> for reuse in your current application, or across many > applications. > > >>>>>>> > > >>>>>>> Tapestry is ... global > > >>>>>>> > > >>>>>>> Tapestry has built-in support for more than a dozen different > > >>>>>>> languages, and makes it easy for your application to cleanly > > >>>>>>> support multiple localizations. Tapestry automatically tracks > the > > >>>>>>> user's preferred locale and makes it easy to access > > >>>>>>> user-localized messages across the entire application. > > >>>>>>> > > >>>>>>> Tapestry is ... dependable > > >>>>>>> > > >>>>>>> Tapestry's roots go back to 2003 as an Apache project, and even > > >>>>>>> earlier as an open-source projects. Thousands of applications > > >>>>>>> run on Tapestry, including high-throughput sites like > SeeSaw.com. > > >>>>>>> Tapestry applications have a history of running glitch-free. > > >>>>>>> > > >>>>>>> Tapestry is ... fun > > >>>>>>> > > >>>>>>> Tapestry removes the tedium of developing web applications, > leaving > > >>>>>>> just the fun parts. Tapestry keeps you "in the zone", having > > >>>>>>> fun and coding up a storm! Tapestry: code less deliver more! > > >>>>>>> > > >>>>>>> > > >>>>>> > > >>>>>> > > >>>>>> > --------------------------------------------------------------------- > > >>>>>> To unsubscribe, e-mail: [email protected] > > >>>>>> For additional commands, e-mail: [email protected] > > >>>>>> > > >>>>>> > > >>>>> > > >>>>> > > >>>>> > > >>>>> -- > > >>>>> Howard M. Lewis Ship > > >>>>> > > >>>>> Creator of Apache Tapestry > > >>>>> > > >>>>> The source for Tapestry training, mentoring and support. Contact me > to > > >>>>> learn how I can get you up and productive in Tapestry fast! > > >>>>> > > >>>>> (971) 678-5210 > > >>>>> http://howardlewisship.com > > >>>>> > > >>>>> > --------------------------------------------------------------------- > > >>>>> To unsubscribe, e-mail: [email protected] > > >>>>> For additional commands, e-mail: [email protected] > > >>>>> > > >>>> > > >>>> > > >>>> > --------------------------------------------------------------------- > > >>>> To unsubscribe, e-mail: [email protected] > > >>>> For additional commands, e-mail: [email protected] > > >>>> > > >>>> > > >>> > > >>> > > >>> > > >>> -- > > >>> Howard M. Lewis Ship > > >>> > > >>> Creator of Apache Tapestry > > >>> > > >>> The source for Tapestry training, mentoring and support. Contact me > to > > >>> learn how I can get you up and productive in Tapestry fast! > > >>> > > >>> (971) 678-5210 > > >>> http://howardlewisship.com > > >>> > > >>> --------------------------------------------------------------------- > > >>> To unsubscribe, e-mail: [email protected] > > >>> For additional commands, e-mail: [email protected] > > >>> > > >> > > >> > > >> --------------------------------------------------------------------- > > >> To unsubscribe, e-mail: [email protected] > > >> For additional commands, e-mail: [email protected] > > >> > > >> > > > > > > > > > > > > -- > > > Best Regards / Viele Grüße > > > > > > Sebastian Hennebrueder > > > ----- > > > Software Developer and Trainer for Hibernate / Java Persistence > > > http://www.laliluna.de > > > > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [email protected] > > > For additional commands, e-mail: [email protected] > > > > > > > > > > > > > > -- > > Howard M. Lewis Ship > > > > Creator of Apache Tapestry > > > > The source for Tapestry training, mentoring and support. Contact me to > > learn how I can get you up and productive in Tapestry fast! > > > > (971) 678-5210 > > http://howardlewisship.com > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > -- Howard M. Lewis Ship Creator of Apache Tapestry The source for Tapestry training, mentoring and support. Contact me to learn how I can get you up and productive in Tapestry fast! (971) 678-5210 http://howardlewisship.com
