I think for the admin fonts, we put those in a separate css file: fonts.css, so you could easily disable them by replacing that file with a blank file. We could probably do the same thing with a responsive.css file.
(Though if we do give the option to switch, do we now need to support and test every change for both cases? or maybe from now on we only touch responsive.css?) Collin On Mon, Jan 9, 2017 at 8:26 AM, Marc Tamlyn <marc.tam...@gmail.com> wrote: > I'd suggest including this with a mechanism (on the admin site?) to > disable it for a while if that causes problems for existing custom setups? > > Marc > > On 9 January 2017 at 11:59, Adam Johnson <m...@adamj.eu> wrote: > >> - perhaps supplying an empty CSS file with the same name overrides the >>> file provided by the admin? (I’m not sure) >> >> >> It does, as long as the app it's in is before django.contrib.admin in >> INSTALLED_APPS, django-grappelli >> <https://django-grappelli.readthedocs.io/en/latest/> uses this mechanism >> to extend/replace the admin's javascript and styles. >> >> I'm totally +1 for the responsive CSS too, thanks for your work on >> django-flat-theme! >> >> On 9 January 2017 at 11:50, Aymeric Augustin < >> aymeric.augus...@polytechnique.org> wrote: >> >>> Hello Elky, >>> >>> I’d love to see this responsive design merged in Django. I’m using the >>> admin from my phone quite often and the lack of a responsive design makes >>> that painful. >>> >>> The admin gets very few CSS changes. I don’t think we should refrain >>> from adding a useful responsive design out of fear that it will be hard to >>> maintain. >>> >>> An opt-out mechanisms for third-party apps that don’t want the >>> responsive styles will a nice touch (but not absolutely necessary in my >>> opinion). I don’t think a setting is appropriate. I’d rather use the >>> template or static file overriding mechanisms, for example: >>> - perhaps supplying an empty CSS file with the same name overrides the >>> file provided by the admin? (I’m not sure) >>> - alternatively responsive styles could apply only within >>> body.responsive; the admin’s template would have a <body >>> class=“responsive”>; third party apps could override that template and >>> remove the class >>> >>> Thanks for you work on the admin’s style, >>> >>> -- >>> Aymeric. >>> >>> On 9 Jan 2017, at 11:59, elky <mansell...@gmail.com> wrote: >>> >>> Hi guys, >>> >>> Few months ago I released *django-flat-responsive* >>> <https://github.com/elky/django-flat-responsive> app - a simple >>> extension for admin that makes interface mobile and tablet friendly. I >>> tested it on few complex projects using major mobile browsers and it works >>> good. Now I'm going to make pull request to Django repo but before I want >>> to ask community -- is it necessary to have responsive admin? >>> >>> My thoughts: >>> >>> Pros: >>> - It's modern >>> - Few times I really needed to make some edits inside admin through my >>> mobile (it was painful), so I think some people want admin to be responsive >>> >>> Cons: >>> - New admin features should be always tested on mobile devices (or on >>> different screen sizes at least). It also uses CSS3 flexbox so developers >>> shoul learn how it works >>> - 3rd party apps should care about responsive layout. It's not so easy >>> for some apps like Django Admin Tools or some CMS based on admin >>> >>> As fas as django-flat-responsive just adds one CSS file to static >>> folder, what if to have an option in *settings.py* that enables >>> responsive admin? >>> >>> I would glad to hear your thoughts >>> >>> Thank you >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Django developers (Contributions to Django itself)" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to django-developers+unsubscr...@googlegroups.com. >>> To post to this group, send email to django-developers@googlegroups.com. >>> Visit this group at https://groups.google.com/group/django-developers. >>> To view this discussion on the web visit https://groups.google.com/d/ms >>> gid/django-developers/dd915c1d-d8a8-4f91-a223-268e17044cd1%4 >>> 0googlegroups.com >>> <https://groups.google.com/d/msgid/django-developers/dd915c1d-d8a8-4f91-a223-268e17044cd1%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> For more options, visit https://groups.google.com/d/optout. >>> >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Django developers (Contributions to Django itself)" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to django-developers+unsubscr...@googlegroups.com. >>> To post to this group, send email to django-developers@googlegroups.com. >>> Visit this group at https://groups.google.com/group/django-developers. >>> To view this discussion on the web visit https://groups.google.com/d/ms >>> gid/django-developers/5A95FC83-B1DD-408C-94B7-9A4E81A6F1D3%4 >>> 0polytechnique.org >>> <https://groups.google.com/d/msgid/django-developers/5A95FC83-B1DD-408C-94B7-9A4E81A6F1D3%40polytechnique.org?utm_medium=email&utm_source=footer> >>> . >>> >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> >> >> -- >> Adam >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Django developers (Contributions to Django itself)" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to django-developers+unsubscr...@googlegroups.com. >> To post to this group, send email to django-developers@googlegroups.com. >> Visit this group at https://groups.google.com/group/django-developers. >> To view this discussion on the web visit https://groups.google.com/d/ms >> gid/django-developers/CAMyDDM3c%2B6PzGFOm63sVL0g63mMtchHRPFQ >> syb39rN%3D3ND8%2BHA%40mail.gmail.com >> <https://groups.google.com/d/msgid/django-developers/CAMyDDM3c%2B6PzGFOm63sVL0g63mMtchHRPFQsyb39rN%3D3ND8%2BHA%40mail.gmail.com?utm_medium=email&utm_source=footer> >> . >> >> For more options, visit https://groups.google.com/d/optout. >> > > -- > You received this message because you are subscribed to the Google Groups > "Django developers (Contributions to Django itself)" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to django-developers+unsubscr...@googlegroups.com. > To post to this group, send email to django-developers@googlegroups.com. > Visit this group at https://groups.google.com/group/django-developers. > To view this discussion on the web visit https://groups.google.com/d/ > msgid/django-developers/CAMwjO1EuQMdHXH5ODYoUaG22ALXAi > mnaoYfUyW128%2BxnrFuHYw%40mail.gmail.com > <https://groups.google.com/d/msgid/django-developers/CAMwjO1EuQMdHXH5ODYoUaG22ALXAimnaoYfUyW128%2BxnrFuHYw%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAFO84S5kW-QNU68q05%3DuEfo4tTEonwaKkZJVUDH4RL7jJbY%3Dgg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
