Skip to content

Conversation

@aaugustin
Copy link
Contributor

No description provided.

@aaugustin
Copy link
Contributor Author

@jezdez @robhudson Are you OK with this?

jQuery accounts for more than two thirds of the size of the debug_toolbar package, and the world doesn't need yet another bundled copy ;-)

jezdez added a commit that referenced this pull request Nov 23, 2013
@jezdez jezdez merged commit 7d24008 into django-commons:master Nov 23, 2013
@robhudson
Copy link
Contributor

I probably would have voted a -0 on this. I don't think the hassle of setting this up before you might go on a trip (or expect it to be there but it's not and you have no internet) outweighs the extra size to bundle it. But I wouldn't block it you guys think it's the way to go.

@aaugustin
Copy link
Contributor Author

Sure, it's difficult to quantify the advantages and drawbacks of this change.

It's quite uncommon and challenging to do serious development work totally offline if you haven't prepared for it, for instance by ensuring you have the docs for your frameworks available offline.

If you're missing jQuery, the toolbar won't appear. You may not even notice it — it's hard to notice that something isn't there! And if you understand that the toolbar doesn't load, and you really need it, you can probably find a copy of jQuery lying around on your laptop and inject it in the page...

@aaugustin
Copy link
Contributor Author

(As a side note, this change will make it easier for Linux distros to package the debug toolbar, if they ever want too. They frown upon bundled libraries.)

ryneeverett pushed a commit to ryneeverett/django-debug-toolbar that referenced this pull request Oct 2, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants