> On 2018-20-12, at 05:16 AM, Christopher Dodunski
> wrote:
>
> Should simplification, then, be one of the declared objectives going forward?
I would appreciate this as one goal of the future roadmap.
Rafael
-
To
Hi all,
"A designer knows he has achieved perfection not when there is nothing
left to add, but when there is nothing left to take away." - Antoine de
Saint-Exupéry.
Winsome words from a once French aviator. Perfecting Tapestry is unlikely
to be a simple matter of just culling code. Still, it
It would be great to see a fresh vision and roadmap for Tapestry going
forward. Tapestry has many strengths, but has a relatively steep
learning curve and does not do enough to help new developers get off the
ground. We have been using Tapestry for a very long time and still find
it
> On 2018-19-12, at 07:32 PM, Carlos Montero Canabal
> wrote:
>
> 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...
That’s great
> On 2018-19-12, at 07:01 PM, Thiago H. de Paula Figueiredo
> wrote:
>
> What issue, exactly? Exact HTML output? If yes, this is something that
> probably can be either fixed in Tapestry itself or customized implementing
> a MarkupRenderer.
Yes, this basically boils down to Tapestry not
Hello,
I kind of agree with Rafael. I would really like to see tapestry core having no
css or JS framework dependencies at all, server side only validation etc…
And a pluggable architecture where you can add bootstrap compatibility os JS
frameworks or form client side validation etc…
The
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
On Wed, Dec 19, 2018 at 2:03 PM Rafael Bugajewski
wrote:
> 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
> On 2018-19-12, at 01:23 PM, Thiago H. de Paula Figueiredo
> 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).
>
> On 2018-19-12, at 02:26 PM, Chris Poulsen wrote:
>
> Perhaps it is possible to find a lightweight,/focused library with a
> compatible license today, that tapestry could rely on, instead of
> attempting to implement this on its own.
I pretty much like this idea in practice. What I mean
Hi
Nice work on moving tapestry forward! It looks like the JDK updates may
just land, before we can't postpone updating our stuff anymore *fingers
crossed* ;)
There are still something fishy in the property access / generics support
implementation, I reported it some years back either on the
On Wed, Dec 19, 2018 at 8:41 AM Rafael Bugajewski
wrote:
> Congratulations! Thanks to the core team for your continuous work and the
> effort you put into maintaining Tapestry.
>
Thanks!
> I think the whole industry goes the way of trying to simplify things (just
> take a look at the most
Great news and great work Tapestry Team!
El mié., 19 dic. 2018 a las 0:15, Thiago H. de Paula Figueiredo (<
thiag...@gmail.com>) escribió:
> You're welcome!
>
> Tapestry 5.5, supporting Java 11, will be released in the next couple
> months at most.
>
> On Tue, Dec 18, 2018 at 5:54 PM Cezary
Congratulations! Thanks to the core team for your continuous work and the
effort you put into maintaining Tapestry.
I think the whole industry goes the way of trying to simplify things (just take
a look at the most recent programming languages & frameworks). If we’re talking
about modernizing
Good team effort! It's encouraging to see Tapestry progressing in step
with associated technologies: Java 12 is due out in March, and Hibernate
currently at version 5.3.3.
Tapestry 5 was a leap forward from 4. Where does the community see
Tapestry 6 at on the Java web landscape? A free and
15 matches
Mail list logo
