Re: Enhanced auth.User

2011-03-22 Thread crodjer
On Wednesday, March 23, 2011 5:10:36 AM UTC+5:30, Russell Keith-Magee wrote:
>
> On Wed, Mar 23, 2011 at 4:32 AM, Rohan Jain  wrote:
> > These are some auth settings and models I propose to account for the
> > generally
> > raised questions for auth.User flexibility.
>
> Two quick points:
>
> Firstly -- the fact that you've given some biographical detail at the
> bottom, and that this biographical detail says your a student,
> suggests that this is a GSoC proposal? Is this the case? If so --
> that's a pretty big detail to omit. Django-developers is a general
> list for discussing the development of Django; if you're proposing a
> GSoC project, you need say so.
>
This was not a gsoc proposal, I added my biographical details as 
an introduction as this was one of my first post on the group. The 
changes I suggested have been on my mind for some time, so I thought
of posting it. Auth user model modifications, Dynamic site ID are some 
discussions which have been highly requested and discussed. So I am 
aware that one cannot just write a few modifications and fix it for all.  

> Secondly -- This is a reason that this project is listed as a high
> complexity project on the GSoC wiki page. It's deceptively difficult,
> and there's *lots* of prior art. A proposal that starts with
> introducing 3 new settings, and finishes with the phrase "create a
> datamigration script" is essentially a non-starter for reasons that
> are well documented historically.
>
> If you're interested in this project, I *strongly* suggest that you
> spend a couple of days familiarizing yourself with the historical
> discussions about the idea. There was a lengthy discussion around last
> year's GSoC; a student was proposing work on this project, but
> ultimately backed out because of the complexities involved. At the
> very least, it should give an indication of what will and won't be
> accepted.
>
> Yours,
> Russ Magee %-)
>
>

-- 
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.



Form media, expose raw urls to templates

2011-06-28 Thread crodjer
The form media widget should also allow an access to the direct javascript
urls (Instead of just rendering it directly) so that it can be used with 
javascript
loaders (I perticularly use headjs <http://headjs.com/> which supports 
parallel loading of javascripts.
But for using it I always have to write custom form methods as accessing 
private
variables (._js) is reastricted. 

I finally set about and added few lines to the form media widget. The patch:
https://github.com/crodjer/django/commit/8fa41950bcfe1396862a17dc5e138af35075005a

I think that django should allow an access to the media (at least js) as the 
html
rendring required is not always the way the form does.

If there is a simpler way to achieve this, please suggest.

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/django-developers/-/2Pck_o-u7o0J.
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.