tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Geoff Callender <geoff.callender.jumpst...@gmail.com>
Subject Re: Suitability of AjaxResponseRenderer
Date Fri, 24 Jan 2014 07:25:08 GMT
Thanks, Howard.

Rich Hickey is a very bright boy. When he identified "complecting" as a
pervasive problem in this business I thought "hallelujah". He nailed it.


On 24 January 2014 05:44, Howard Lewis Ship <hlship@gmail.com> wrote:

> Got with the change. The MultiZoneUpdate return value is deprecated.  One
> of the things I've learned along the way is that having an API to call into
> (such as AjaxResponseRenderer) is sometimes a lot less complex than a magic
> mapping of return values.
>
> Rich Hickey's "Simple Made Easy" is a wake up call.
>
>
> On Wed, Jan 22, 2014 at 5:45 PM, Geoff Callender <
> geoff.callender.jumpstart@gmail.com> wrote:
>
> > Ville, you've echoed my thoughts exactly. If I don't hear an alternative
> > view in the next 24 hours then I'll go ahead with the change.
> >
> > Geoff
> >
> > On 22/01/2014, at 11:24 PM, Ville Virtanen wrote:
> >
> > > Hi,
> > >
> > > my 2c: use addRenderer. The driving decision for me is to support case,
> > where additional functionality is added later that uses
> > ajaxResponseRenderer.addRenderer(zone). That does not mix well with the
> > return value, and suddenly some part of ajax functionality is not
> working,
> > and the bug manifests only if you happen to hit the code path that uses
> the
> > return value. So, I see no point using the return value myself. (This
> > however was tested with one of the alphas, I don't know if you can mix
> and
> > match these days.)
> > >
> > > Ville Virtanen
> > > Orient Import Oy
> > > +358 45 111 4260
> > >
> > > -----Alkuperäinen viesti-----
> > > Lähettäjä: Geoff Callender [mailto:geoff.callender.jumpstart@gmail.com
> ]
> > > Lähetetty: 22. tammikuuta 2014 7:42
> > > Vastaanottaja: Tapestry development
> > > Aihe: Suitability of AjaxResponseRenderer
> > >
> > > Hey Howard (and anyone else who's qualified to answer),
> > >
> > > Before I mess up JumpStart by changing the examples that return
> > > zone.getBody() to use ajaxResponseRenderer.addRenderer(zone) instead,
> is
> > there any downside to using the latter for single-zone updates?
> > >
> > > The reason I want to do this is to provide simple consistency between
> > single-zone and multi-zone update examples. But is there a downside?
> > >
> > > Regards,
> > >
> > > Geoff
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> > > For additional commands, e-mail: dev-help@tapestry.apache.org
> > >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> > For additional commands, e-mail: dev-help@tapestry.apache.org
> >
> >
>
>
> --
> 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
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message