Re: 1.2 Proposal: django debug toolbar in contrib

On Aug 18, 12:35 am, Dave Jeffery wrote: > (Sticking my nose in where it isn't wanted...) The toolbar looks really > great but it feels a bit over-designed and too heavy for a functional > interface which will sit atop of existing websites. I'm especially referring > to the

Re: 1.2 Proposal: django debug toolbar in contrib

On Mon, Aug 17, 2009 at 2:28 PM, Jacob Kaplan-Moss wrote: > > The reasoning was that we wanted the error pages to be somewhat > framework-agnostic; > we didn't want to impose our branding onto parts of *your* site. I'd > say a similar ethos should be expressed in the debug

Re: 1.2 Proposal: django debug toolbar in contrib

On Aug 17, 4:28 pm, Jacob Kaplan-Moss wrote: > I'd say a similar ethos should be expressed in the debug toolbar branding. > If you wanted to be extra special, some UI similarity between the > error pages and the debug toolbar would probably be a good idea. Fair 'nuff. I'll

Re: 1.2 Proposal: django debug toolbar in contrib

Oh, forgot to include the screencast: http://s3.pixane.com.s3.amazonaws.com/ddt-ui-refresh.mov -I --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to

Re: 1.2 Proposal: django debug toolbar in contrib

I've been working on prettyfication of the DDT. Github: http://github.com/idangazit/django-debug-toolbar/tree/idan-ui-rf. It's a reasonably complete reskinning of the existing DDT. There are still a couple of outstanding issues but the redesign is largely finished. I didn't use the admin color

Re: 1.2 Proposal: django debug toolbar in contrib

On Thu, Aug 13, 2009 at 5:00 AM, Rob Hudson wrote: > > I'm not sure if this is the place but here are some other issues or > questions I have if this were to happen... This is as good a place as any. > * The jQuery question is a big one.  I've taken strides to make the >

Re: 1.2 Proposal: django debug toolbar in contrib

Oh, and thats most likely my branch you're referring to Martin. I implemented a lot of the panels, and went so far as adding crazy monkey patching in some of them to catch some information I wanted. http://github.com/dcramer/django-debug-toolbar/tree/master On Aug 11, 11:38 am, Martin Maney

Re: 1.2 Proposal: django debug toolbar in contrib

I think it's mostly only my fork (and it's forks) that vary much from trunk. I never got around to changing the framework to come in line with the master branch I think because it didn't support everything that was needed. Not sure if it does now however. On Aug 12, 4:00 pm, Rob Hudson

Re: 1.2 Proposal: django debug toolbar in contrib

I'm not sure if this is the place but here are some other issues or questions I have if this were to happen... * The jQuery question is a big one. I've taken strides to make the debug toolbar interoperate with other popular JS frameworks (mootools and prototype, namely). But if jQuery were

Re: 1.2 Proposal: django debug toolbar in contrib

On Tue, Aug 11, 2009 at 11:59 PM, Rob Hudson wrote: > > On Tue, Aug 11, 2009 at 7:01 AM, Russell > Keith-Magee wrote: >> Firstly, there is the simple issue of ownership and copyright. >> Obviously, those that have written DDT components that are to

Re: 1.2 Proposal: django debug toolbar in contrib

I thought one of the more recent patches to DDT made it run Jquery in compatability mode, which should resolve these clashes, probably isn't on all branches though. mat On Tue, Aug 11, 2009 at 6:09 PM, Ulrich Petri wrote: > > > Am 11.08.2009 um 16:50 schrieb Alex Gaynor: > > > >

Re: 1.2 Proposal: django debug toolbar in contrib

Am 11.08.2009 um 16:50 schrieb Alex Gaynor: > > This is still true IMO, but there's another issue here. DDT uses > jQuery, and AFAIK the official position is still that we aren't > choosing a JS lib (although clearly Zain's work is rapidly moving us > to the point where a decision has to be

Re: 1.2 Proposal: django debug toolbar in contrib

On Tue, Aug 11, 2009 at 09:50:35AM -0500, Alex Gaynor wrote: > Right now django-debug-toolbar has a pretty stable panel interface and > I actually can't recall it changing since release. A possibly more > interesting issue is that some of the debug information it get's is > somewhat of a hack,

Re: 1.2 Proposal: django debug toolbar in contrib

On Tue, Aug 11, 2009 at 7:01 AM, Russell Keith-Magee wrote: > Firstly, there is the simple issue of ownership and copyright. > Obviously, those that have written DDT components that are to be > included need to be onboard with this idea. On this point I've strived to be

Re: 1.2 Proposal: django debug toolbar in contrib

On Tue, Aug 11, 2009 at 9:01 AM, Russell Keith-Magee wrote: > > On Tue, Aug 11, 2009 at 8:32 PM, Mat Clayton wrote: >> Hey all, >> >> For us of the most useful developments in the django community recently has >> been the django debug toolbar. >> >>

Re: 1.2 Proposal: django debug toolbar in contrib

On Tue, Aug 11, 2009 at 8:32 PM, Mat Clayton wrote: > Hey all, > > For us of the most useful developments in the django community recently has > been the django debug toolbar. > > http://github.com/robhudson/django-debug-toolbar/tree/master/debug_toolbar > > This seems to be

1.2 Proposal: django debug toolbar in contrib

Hey all, For us of the most useful developments in the django community recently has been the django debug toolbar. http://github.com/robhudson/django-debug-toolbar/tree/master/debug_toolbar This seems to be branching and growing very rapidly on github, however lots of branches are appearing