You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by Kimmo Eklund <ki...@postikaista.net> on 2003/04/02 17:49:31 UTC

Thanks for ther truly informative error messages!

Hi,

I just want to thank Howard and all the other developers for having
informative error messages. Really. It's yet another thing that makes
Tapestry different from most frameworks; the default error messages go
often beyond just reporting an error by giving hint what should be done
to fix the problem.

I've noticed this when I started using tapestry again for a new project.
My last Tapestry project ended about 5 months ago and that was enough to
forget many details.

As a developer I know that it's hard work to finish details things like
this.

/ekimmo





Re: Thanks for ther truly informative error messages!

Posted by Adam Greene <ag...@nbnet.nb.ca>.
I would also like to thank Howard et al for the great work on Tapestry.  It
is all we use to do projects now and with each successive release we just
keep saying "Wow, that just cut out even more work that we have to do."
With the upcoming release of 2.4, less and less of the heavy lifting needs
to be done by the Web Developer and it leaves us free to be creative and
focus on making good web applications and not simply web applications that
works (and even then not always :-< ).

Again, thanks for making my life easier (I stopped going bald thanks to
Tapestry... Sounds like a shampoo advertisement doesn't it :-)

----- Original Message -----
From: "Howard M. Lewis Ship" <hl...@attbi.com>
To: "'Tapestry users'" <ta...@jakarta.apache.org>
Sent: Wednesday, April 02, 2003 2:04 PM
Subject: RE: Thanks for ther truly informative error messages!


> Thanks for the feedback.  This is one of the design goals of Tapestry:
> support the developer with useful error messages.  Glad to see people
> notice!
>
> --
> Howard M. Lewis Ship
> Creator, Tapestry: Java Web Components
> http://jakarta.apache.org/proposals/tapestry
>
>
>
> > -----Original Message-----
> > From: Kimmo Eklund [mailto:kimmo.eklund@postikaista.net]
> > Sent: Wednesday, April 02, 2003 10:50 AM
> > To: tapestry-user@jakarta.apache.org
> > Subject: Thanks for ther truly informative error messages!
> >
> >
> > Hi,
> >
> > I just want to thank Howard and all the other developers for
> > having informative error messages. Really. It's yet another
> > thing that makes Tapestry different from most frameworks; the
> > default error messages go often beyond just reporting an
> > error by giving hint what should be done to fix the problem.
> >
> > I've noticed this when I started using tapestry again for a
> > new project. My last Tapestry project ended about 5 months
> > ago and that was enough to forget many details.
> >
> > As a developer I know that it's hard work to finish details
> > things like this.
> >
> > /ekimmo
> >
> >
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>
>



RE: Thanks for ther truly informative error messages!

Posted by "Howard M. Lewis Ship" <hl...@attbi.com>.
Thanks for the feedback.  This is one of the design goals of Tapestry:
support the developer with useful error messages.  Glad to see people
notice!

--
Howard M. Lewis Ship
Creator, Tapestry: Java Web Components
http://jakarta.apache.org/proposals/tapestry



> -----Original Message-----
> From: Kimmo Eklund [mailto:kimmo.eklund@postikaista.net] 
> Sent: Wednesday, April 02, 2003 10:50 AM
> To: tapestry-user@jakarta.apache.org
> Subject: Thanks for ther truly informative error messages!
> 
> 
> Hi,
> 
> I just want to thank Howard and all the other developers for 
> having informative error messages. Really. It's yet another 
> thing that makes Tapestry different from most frameworks; the 
> default error messages go often beyond just reporting an 
> error by giving hint what should be done to fix the problem.
> 
> I've noticed this when I started using tapestry again for a 
> new project. My last Tapestry project ended about 5 months 
> ago and that was enough to forget many details.
> 
> As a developer I know that it's hard work to finish details 
> things like this.
> 
> /ekimmo
> 
> 
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>