It's very informative and helpful , esp. for newbie to Django, it's
also looking good. How may I get to try it in my own learning projects?
On Thu, 10 Nov 2005 21:26:36 -0600 Jacob Kaplan-Moss wrote:
>
> Hey folks --
>
> With Wilson's help I've mocked up some nice-looking error pages to
> replace the ugly tracebacks when DEBUG is on. Right now they're
> implemented as a middleware component, but I think they'd be best
> roll
Jacob Kaplan-Moss wrote:
>
>
>> We'll have to think about how to fit the template debugging work I did
>> in new-admin into this as well
>
>
> Ooh, this is nice -- I hadn't seen it before. I'll take a look at your
> code and think about how the two could work together, but to keep SVN
> con
Jacob Kaplan-Moss wrote:
>
> Hey folks --
>
> With Wilson's help I've mocked up some nice-looking error pages to
> replace the ugly tracebacks when DEBUG is on. Right now they're
> implemented as a middleware component, but I think they'd be best
> rolled into the Django core -- good looking
On Nov 11, 2005, at 9:32 AM, Wilson Miner wrote:
My conclusion is that app error pages shouldn't be wrapped in the
admin. I
think that's the right way to go, but I'm open to arguments to the
contrary.
I agree; they need to be as simple as possible to avoid re-raising
exceptions in the err
We'll have to think about how to fit the template debugging work I did
in new-admin into this as well
Ooh, this is nice -- I hadn't seen it before. I'll take a look at
your code and think about how the two could work together, but to
keep SVN conflicts to a minimum I won't actually integ
The arrow next to "Local vars" on the 500 page seems the wrong wayround to me. I think it should point down before you click it to
indicate that doing so will reveal more stuff, and point left whenthe stuff is expanded to indicate that clicking again will roll itall back up.I had it that way to beg
Jacob Kaplan-Moss wrote:
>
> Hey folks --
>
> With Wilson's help I've mocked up some nice-looking error pages to
> replace the ugly tracebacks when DEBUG is on. Right now they're
> implemented as a middleware component, but I think they'd be best
> rolled into the Django core -- good looking
Jacob Kaplan-Moss wrote:
Server error page: http://toys.jacobian.org/django/500.html
This one is fantastic! I hope now I will use those 'raise str(myvar)'
lookups mush less.
On 11 Nov 2005, at 05:08, Adrian Holovaty wrote:
We could include it as a data:url. :-)
I thought about that, but I imagine it would lead to a broken image
in IE.
Unless... we set the data:url as the CSS background of a div. I bet
that would fail gracefully in IE. Fun!
On 11 Nov 2005, at 04:32, pbx wrote:
Lovely. How about adding accesskeys? E.g.:
GET
POST
Cookies
META
Settings
As always with accesskeys, the trouble with these is their potential
to interfere with browser shortcuts. In this case, the "Go" menu in
Firefox on Windows
On 11/10/05, Simon Willison <[EMAIL PROTECTED]> wrote:
> Pretty as it is, it doesn't match the style of djangoproject.com at
> all. I'd like to see a bit more green! Not showing a logo is a good
> idea though as we can't know for sure where the logo is hosted by
> their install, and linking to one
On 11 Nov 2005, at 03:26, Jacob Kaplan-Moss wrote:
With Wilson's help I've mocked up some nice-looking error pages to
replace the ugly tracebacks when DEBUG is on. Right now they're
implemented as a middleware component, but I think they'd be best
rolled into the Django core -- good lookin
Lovely. How about adding accesskeys? E.g.:
GET
POST
Cookies
META
Settings
--
Paul Bissex
http://e-scribe.com/news/
Northampton MA USA 01061-0847
# Server error page: http://toys.jacobian.org/django/500.html
# 404 error page: http://toys.jacobian.org/django/404.html
Yay!
--
Jonathan Daugherty
http://www.parsed.org
2005/11/11, Jacob Kaplan-Moss <[EMAIL PROTECTED]>:
>
> Hey folks --
>
> With Wilson's help I've mocked up some nice-looking error pages to
> replace the ugly tracebacks when DEBUG is on. Right now they're
> implemented as a middleware component, but I think they'd be best
> rolled into the Django
Hey folks --
With Wilson's help I've mocked up some nice-looking error pages to
replace the ugly tracebacks when DEBUG is on. Right now they're
implemented as a middleware component, but I think they'd be best
rolled into the Django core -- good looking, functional error
messages by def
17 matches
Mail list logo
