Re: Django Admin New Look

On Sun, Aug 16, 2015, at 16:00, elky wrote: > Hi guys, > > I made double work for vector icons - now we have Font and SVG icons. > Let's choose what to use. > > *Quoting my comment[1] from SVG discussion here:* > >> Well, only week ago I was 100% happy with font icons. But after >> Collin's comme

Re: Django Admin New Look

Does 'title' attribute help in terms of accessibility? On Friday, 21 August 2015 14:44:02 UTC+5, Hugo Osvaldo Barrera wrote: > > > I see not mention of this later on this thread so I have to ask: > Do we have an equivalent of an `alt` if using fonts? If not, how would > this be usable by, for

Re: The hypothetical models.MultiField: is there a rationale to avoid it ? Or could it make it into future releases ?

I've been thinking how we could move forward with composite fields without requiring too much changes in one go (large changes tend to never happen). It seems the first step forward would be to introduce a composite field with the following properties: class Foo(models.Model): x = models.In

Re: Django Admin New Look

On Fri, Aug 21, 2015, at 08:06, elky wrote: > Does 'title' attribute help in terms of accessibility? `title` adds a tooltip, so no, not really. -- Hugo Osvaldo Barrera -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django i

Re: future of QuerySet.extra()?

Actually I spoke too soon, I excitedly misunderstood what *RawSQL* does/doesn't do. Unfortunately it requires access to a column, which is not what I need. I'm inserting WHERE conditions like */*specialcomment*/1* - the special comment is translated into query rewriting, leaving *1* in the *WHER

Adding Optional Better Unicode Handling for `slugify`

Hi. This came up on Crispy Forms : In [*1*]: from django.utils.text import slugify In [*2*]: s = u'επιτέλους' In [*3*]: slugify(s) Out[*3*]: u'' It isn't great. It's been discussed before and closed as Won't Fix

Re: Adding Optional Better Unicode Handling for `slugify`

Does https://github.com/django/django/commit/f8cc464452f495fce2a3d6f7494396c8f798a1e6#diff-f614fc7a7dbb2882be1692a448abd21fR413 work for you? :-) On Friday, August 21, 2015 at 10:29:03 AM UTC-4, Carlton wrote: > > Hi. > > This came up on Crispy Forms >

Re: Allow custom "BoundFields" on forms and make BoundField public API

While reviewing the proposed documentation for BoundField, I noticed the methods BoundField.as_textarea() and as_text() [1] introduced at the start of new forms [2]. According to the comment, their purpose is as "shortcuts for changing the output widget type". These methods aren't documented, an

Re: Allow custom "BoundFields" on forms and make BoundField public API

I replied to your comment on pr 5123 on github [1] but it seems to be buried under "Show outdated diff" so here it is again: I agree that as_text() and as_textarea() are not needed so I will remove them from the docs. There is a use case for as_widget() though. In one of my projects I have a temp

Improving MSSQL and Azure SQL support on Django

Hi Django Committers, My name is Meet Bhagdev, I work in the Database Systems engineering team at Microsoft in Seattle, WA. My focus is the APIs used to connect to and use Azure SQL Database and SQL Server (MSSQL). Example APIs are ODBC, JDBC, ADO.NET, etc. We’d love for Django users t

Re: Adding Optional Better Unicode Handling for `slugify`

Why sir, I think it might. :-) Thanks. On Friday, 21 August 2015 16:37:02 UTC+2, Tim Graham wrote: > > Does > https://github.com/django/django/commit/f8cc464452f495fce2a3d6f7494396c8f798a1e6#diff-f614fc7a7dbb2882be1692a448abd21fR413 > > work for you? :-) > > On Friday, August 21, 2015 at 10:2