On Tue, Aug 11, 2009 at 11:59 PM, Rob Hudson<treborhud...@gmail.com> wrote: > > On Tue, Aug 11, 2009 at 7:01 AM, Russell > Keith-Magee<freakboy3...@gmail.com> 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 pro-active (thanks to Jacob)... > before any new commits from new committers were merged I made sure > they're code was ok to be licensed under BSD and they were listed in > the AUTHORS file. Seeing as the "framework" part hasn't changed a > whole lot in the year or so it's been out, it seems like a worthwhile > consideration to me. And I'd be for it.
Excellent. > Actually, to my knowledge, all the forks are panel specific and are > not changing the core "framework" part of the debug toolbar. This was my largest technical concern - if the community is using the same interface, then there is is isn't a problem standardizing on that interface. >> Thirdly - look & feel. I haven't used DDT for a while, so I don't know >> what the state of the art is here. Last time I used DDT, it worked >> fine, but I felt that it needed a little UI polish, especially in >> providing a way to hide it or preventing the toolbar from obscuring >> meaningful parts of the underlying site. I don't know how time and >> forking has treated this particular aspect of DDT. > > Agreed. UI isn't my strong point and I've always hoped a designer > would be inspired to give it a full treatment. There's also the > jQuery aspect of it. I think this probably leads to a bigger > discussion. I have a local branch that makes some big improvements in > this area already. At this point, Jacob has pretty much indicated that JQuery is going to be Django's toolkit of choice if/when a toolkit is used. However, we aren't going to impose that choice onto the frontend. Some discussion is definitely required to establish exactly where the boundary ends. I'll be sure to take a closer look at your new UI branch. >> Lastly - time. This needs to be done in a timely fashion. If we're >> going to include DDT in Django v1.2, then we're going to need to have >> a consensus position - if not a ready-to-commit patch, then at least >> agreement on what would be in a ready-to-commit patch - in a little >> over a month. It it takes much longer than that to reconcile the >> forks, then we may need to consider this a work-in-progress for v1.3. > > Perhaps some discussion at DjangoCon? :) Certainly. This sounds like a great topic for a sprint. Russ %-) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
