Re: django admin: open popups as modals instead of windows

> > On Feb 25, 2015, at 09:07, Russell Keith-Magee > wrote: > > I have an operating system with a graphical user interface. The developers of > that operating system spent an immense amount of time developing it, > polishing it, making it behave in predictable ways, getting keyboard > access

Re: django admin: open popups as modals instead of windows

On Tue, Feb 24, 2015 at 11:59 PM, Riccardo Magliocchetti < riccardo.magliocche...@gmail.com> wrote: > Il 24/02/2015 16:18, Florian Apolloner ha scritto: > >> On Tuesday, February 24, 2015 at 3:23:23 PM UTC+1, riccardo.magliocchetti >> wrote: >> >> I'm no UI/UX expert but modals are more or les

Re: status of 1.8 release blockers

Zero blockers as of this writing. If we survive the next 12 hours with no new ones, I'll release the beta around then (famous last words). On Monday, February 23, 2015 at 7:29:09 PM UTC-5, Tim Graham wrote: > > Previous two issues have been fixed, and now we have two new issues: > > #24391

Re: RE Composite fields-/ Multi Primary / Foreign keys

Hi Aron, Short version - if you're eager to look into this, we're eager to have composite keys in Django - it's probably one of the last features I can think of that was discussed for the 1.0 release but we bumped so that "we can add it for 1.1". (ahem. :-) Yes, there have been a lot of changes

Re: django admin: open popups as modals instead of windows

Il 24/02/2015 20:12, Marc Tamlyn ha scritto: I would suggest that a good modal implementation for these should still support "open in new tab/window" properly, with control/command click not detected by the overriding JavaScript. It may be possible to do this and keep the popup functionality pass

Re: django admin: open popups as modals instead of windows

I would suggest that a good modal implementation for these should still support "open in new tab/window" properly, with control/command click not detected by the overriding JavaScript. It may be possible to do this and keep the popup functionality passing the new id back to the parent window. >Fro

Re: django admin: open popups as modals instead of windows

On Tuesday, February 24, 2015 at 4:18:36 PM UTC+1, Florian Apolloner wrote: > > > > On Tuesday, February 24, 2015 at 3:23:23 PM UTC+1, riccardo.magliocchetti > wrote: >> >> I'm no UI/UX expert but modals are more or less the standard today, >> windows looks like a relic from the 2000s. >> > >

Re: django admin: open popups as modals instead of windows

Il 24/02/2015 16:18, Florian Apolloner ha scritto: On Tuesday, February 24, 2015 at 3:23:23 PM UTC+1, riccardo.magliocchetti wrote: I'm no UI/UX expert but modals are more or less the standard today, windows looks like a relic from the 2000s. That argument is based on what? I'd personal

Re: Support for DATABASES['default'] = {}

The question I'm asking myself right now: what is a "default" database in a multi database setup where "default" does not make sense at all? I can easily think of a case where I have multiple other databases used by other services where Django provides a dashboard. I don't see any of those data

Re: django admin: open popups as modals instead of windows

On Tuesday, February 24, 2015 at 3:23:23 PM UTC+1, riccardo.magliocchetti wrote: > > I'm no UI/UX expert but modals are more or less the standard today, > windows looks like a relic from the 2000s. > That argument is based on what? I'd personally argue that windows are superior cause I can e

django admin: open popups as modals instead of windows

Hello, I've opened a ticket [1] to implement the popups in the admin as modal instead of windows. I'm no UI/UX expert but modals are more or less the standard today, windows looks like a relic from the 2000s. Am also interested in decoupling the js from the admin to make possible for downstrea

Re: Support for DATABASES['default'] = {}

I can't see why it is sensible to support an invalid database configuration as the default. If you explicitly want the default to be a dummy, you should configure that IMO. On 24 February 2015 at 14:04, Marten Kenbeek wrote: > Which one? :P This was more intended as a question than as a proposal

Re: Support for DATABASES['default'] = {}

Which one? :P This was more intended as a question than as a proposal. I personally prefer a documentation change and strict checking of `default` if and only if the database configuration is not empty. django.db.connection relies on the default connection, and third-party apps which (intention

Re: Support for DATABASES['default'] = {}

In that case your proposal sounds perfectly reasonable. On 24 February 2015 at 13:47, Marten Kenbeek wrote: > In fact, DATABASES={} is a valid configuration and merely sets 'default' > as a dummy backend. An exception is only explicitly raised if you supply a > non-empty setting that does not in

Re: Support for DATABASES['default'] = {}

In fact, DATABASES={} is a valid configuration and merely sets 'default' as a dummy backend. An exception is only explicitly raised if you supply a non-empty setting that does not include `default`. On Tuesday, February 24, 2015 at 2:43:51 PM UTC+1, Marc Tamlyn wrote: > > It would seem more sen

Re: Support for DATABASES['default'] = {}

It would seem more sensible to me to try to support DATABASES={}. There's no reason why a Django site should have to run a database - a microservice using redis or something similar is perfectly reasonable and you could want to use Django for other reasons (e.g. shared templates). Marc On 24 Febr

Support for DATABASES['default'] = {}

With recent bug reports (#24332 , #24298 and now #24394 ) all caused by setting `DATABASES['default'] = {}`, this makes me wonder if it should be supported at

Re: Interested in GSoC idea "Replace Form Media Class"

Hi Varun, Thanks for your interest. If you want feedback, you'll need to describe your ideas in more detail. Tim On Monday, February 23, 2015 at 10:31:34 PM UTC-5, Varun Sharma wrote: > > Hi everyone, > > I've been pondering over the django codebase and GSoC ideas for some time > now. I find t