That looks really nice. You'd never put that in a _production_ release though, would you?
Looks perfect for development, but in production I'd prefer my exception views to be pretty generic with a non-technical message, unless the app is for internal staff. So, er, that's what we do. Aside: am I mis-remembering, or did the Yellow Box exception view include a link to the IDE code base class and line in development, you know, a zillion years ago? -- Matt http://logicsquad.net On Mon, Apr 27, 2015, at 12:40 PM, David Holt wrote: > I agree, looks great! > > Sent from my iPad > > On Apr 26, 2015, at 7:34 PM, Paul Hoadley > <pa...@logicsquad.net> wrote: > >> On 27 Apr 2015, at 7:09 am, Hugi Thordarson <h...@karlmenn.is> wrote: >> >>> The standard WO exception page is starting to show its age and I >>> think it’s high time we improve it. I started a new error page today >>> and added the capability to show the code that’s throwing the error >>> (a feature of some of the younger web frameworks that I like) but >>> I’d love to hear ideas about how it can be made better. What does >>> the perfect error page look like? >>> >>> Current work: >>> >>> http://hugi.karlmenn.is/d/error.png >> >> I think that looks fantastic. Out of curiosity, how do you get the >> source code snippet in there? >> >> >> >> >> -- >> Paul Hoadley http://logicsquad.net/
_______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
