I'm serving AMP pages with Tapestry ( https://elcocinerocasero.com/amp/receta/tortilla-de-patata ). I hope to upload an example to http://tapestry5.dev-util.com/ this weekend with the workaround to do it... But yes, AMP and XHTML aren´t good friends...
El mié., 19 dic. 2018 a las 17:03, Rafael Bugajewski (< raf...@juicycocktail.com>) escribió: > > On 2018-19-12, at 01:23 PM, Thiago H. de Paula Figueiredo < > thiag...@gmail.com> wrote: > > > > Well, some stuff is indeed not simple, and I'd say the form support is > the > > part which could use some new components to make at least the simpler > > scenarios simpler to implement (for example, when there are no loops). > > Which other areas do you think could or should be simplified? > > The one thing that comes straight up from my head is the current > complexity / pipeline necessary for generating output. A couple of months > ago I wanted to generate valid AMP pages within Tapestry. After one day of > research and a non-working proof of concept, I decided to use the Play > framework for this small customer and it worked right away. Tapestry does > some processing (necessary for other parts of the framework, AFAIK) that > makes it hard to generate valid AMP pages. I would really love to use > Tapestry here, and I don’t think it’s out of scope for the framework. > > Best, > Rafael > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > >
