some old criticisms of T5

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

some old criticisms of T5

Qbyte Consulting
https://friendlybit.com/html/tapestry-5-and-how-not-to-treat-html/

I'm wondering how users would respond to the above. I haven't found these
issues a big problem myself, but some of these behaviours are problematic,
for example someone mentioned the white-space issue recently.

John
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: some old criticisms of T5

Bob Harner
That's a very old article (2009 -- I don't think many users care about
IE6 redering quirks anymore), but Howard's comments there seem to do a
pretty good job of explaining where the author is either mistaken or
misunderstands the constraints and trade-offs involved. A lot of the
other commenters do likewise. I don't know if there is much more to
add, is there?

On Mon, Sep 19, 2016 at 11:13 AM, Qbyte Consulting
<[hidden email]> wrote:
> https://friendlybit.com/html/tapestry-5-and-how-not-to-treat-html/
>
> I'm wondering how users would respond to the above. I haven't found these
> issues a big problem myself, but some of these behaviours are problematic,
> for example someone mentioned the white-space issue recently.
>
> John

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: some old criticisms of T5

Qbyte Consulting
No, HLS replies were spot on. The only irritation I have found with T5 is
some of the default styling that gets added to handle form errors and these
can be overriden with your own css - can be mucky, but works.

On Mon, Sep 19, 2016 at 5:23 PM, Bob Harner <[hidden email]> wrote:

> That's a very old article (2009 -- I don't think many users care about
> IE6 redering quirks anymore), but Howard's comments there seem to do a
> pretty good job of explaining where the author is either mistaken or
> misunderstands the constraints and trade-offs involved. A lot of the
> other commenters do likewise. I don't know if there is much more to
> add, is there?
>
> On Mon, Sep 19, 2016 at 11:13 AM, Qbyte Consulting
> <[hidden email]> wrote:
> > https://friendlybit.com/html/tapestry-5-and-how-not-to-treat-html/
> >
> > I'm wondering how users would respond to the above. I haven't found these
> > issues a big problem myself, but some of these behaviours are
> problematic,
> > for example someone mentioned the white-space issue recently.
> >
> > John
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: some old criticisms of T5

Cezary Biernacki
In my experience Tapestry generates better HTML than many (most?) of other
frameworks. Lets take for example the whitespace issue. In most cases
whitespace in templates are artefacts of indentation used to improve
readability of templates during development. As the result when blindly
preserved, whitespace in generated HTML is just ton of unnecessary garbage.
E.g. it is not uncommon to see several empty lines at the start of
generated HTML from JSP-powered frameworks. Tapestry approach is much more
efficient.

Regarding, using a complain about problems with using Tapestry-generated
page as responses to AJAX calls, I believe that Tapestry offers better
solution with custom document builder dedicated for AJAX and returning a
custom structure. While just returning HTML snippets  for AJAX can work for
simple applications, it becomes maintainability nightmare for more complex
once: how to ensure that necessary CSS-es, JavaScripts are included but not
duplicated (and when pages are generated from multiple reusable components
that do not know about each other), how to insert the response into
multiple parts of the page, how to avoid DOM id conflicts, how to handle
errors in a friendly way. All of this is provided by Tapestry from the
start.

Another complain was problems with XHTML, thankfully it almost died.

Best regards,
Cezary


On Mon, Sep 19, 2016 at 6:36 PM, Qbyte Consulting <[hidden email]
> wrote:

> No, HLS replies were spot on. The only irritation I have found with T5 is
> some of the default styling that gets added to handle form errors and these
> can be overriden with your own css - can be mucky, but works.
>
> On Mon, Sep 19, 2016 at 5:23 PM, Bob Harner <[hidden email]> wrote:
>
> > That's a very old article (2009 -- I don't think many users care about
> > IE6 redering quirks anymore), but Howard's comments there seem to do a
> > pretty good job of explaining where the author is either mistaken or
> > misunderstands the constraints and trade-offs involved. A lot of the
> > other commenters do likewise. I don't know if there is much more to
> > add, is there?
> >
> > On Mon, Sep 19, 2016 at 11:13 AM, Qbyte Consulting
> > <[hidden email]> wrote:
> > > https://friendlybit.com/html/tapestry-5-and-how-not-to-treat-html/
> > >
> > > I'm wondering how users would respond to the above. I haven't found
> these
> > > issues a big problem myself, but some of these behaviours are
> > problematic,
> > > for example someone mentioned the white-space issue recently.
> > >
> > > John
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [hidden email]
> > For additional commands, e-mail: [hidden email]
> >
> >
>
Loading...