Re: Django Ajax Redux

2005-12-10 Thread David Ascher
On 12/10/05, hugo <[EMAIL PROTECTED]> wrote:  Oh, and please keep in mind that there should be at least a sensiblefallback solution for those who don't want to (or plain and simplecan't) use _javascript_ all the time.I want to read more about the concrete proposal before I dig deep into this thread

Re: Removing the magic

2005-12-06 Thread David Ascher
On 12/6/05, Adrian Holovaty <[EMAIL PROTECTED]> wrote: On 12/6/05, Jeremy Dunck <[EMAIL PROTECTED]> wrote:> As (my) knee-jerk reaction, don't take Aaronsw's criticism so much to heart.  :)>> He's got some points, but his is just one more opinion (and web tool). A bunch of this stuff was discussed b

Re: i18n for JavaScript

2005-11-28 Thread David Ascher
On 11/28/05, hugo <[EMAIL PROTECTED]> wrote: There are several ideas on how to solve this:All of which seem like they would apply beyond Django, no?My first instinct in this sort of case is to find out what others are doing, i.e. Dojo folks, RoR, TG, etc. --david

Re: Making Django easier to get started

2005-11-24 Thread David Ascher
Speaking of searchability, I find that Google searches don't give much insight into the Django website pages. e.g. a search for schema site:djangoproject.orgfails to find any reference to "schema" on the site, but a search from the wiki certainly finds a few hits (23). Is Google being inadvertently

Re: Making Django easier to get started

2005-11-20 Thread David Ascher
On 11/20/05, Simon Willison <[EMAIL PROTECTED]> wrote: I just saw http://code.djangoproject.com/ticket/853 , which advocatessimplifying Django's first-time user experience as much as possible.I think this is an admirable goal, and one that would dramatically improve the number of people using the f

Re: Django and AJAX: Setting aside the conflict

2005-11-18 Thread David Ascher
On 11/18/05, Eugene Lazutkin <[EMAIL PROTECTED]> wrote: I don't care how many layers we are going to have in implementation, I care for the final layer --- actual use of Ajax in templates. RPC is not a final layer for me, because I suspect that majority of user will need end user function

Re: Proposal: models.py by default instead of "models" directory

2005-11-18 Thread David Ascher
On 11/18/05, Jonathan Daugherty <[EMAIL PROTECTED]> wrote: # * Change Django so that it looks for models in a "models" package# (as it currently does) *or* in a file called models.py. Either the# models package or models.py should live directly within the package # pointed-to by INSTALLED_APPS.Do y

Re: Proposal: models.py by default instead of "models" directory

2005-11-18 Thread David Ascher
Overall, anything that doesn't require packages but that accomodates both modules or packages depending on the complexity of the system, and defaults to modules, strikes me as pythonic.I'm pretty new to Django's "app" concept, though, and it seems you're slightly messing with it here, so I'll +0 on

Re: A fix for all that futzing around with paths

2005-11-18 Thread David Ascher
On 11/18/05, Sune Kirkeby <[EMAIL PROTECTED]> wrote: I guess all this just rubs me the wrong way, because it breaksthe Only One Way guideline.And it should thus be challenged, no argument here.It's very possible that the use case it supports (repeatedly switching b/w projects when invoking django-

Re: A fix for all that futzing around with paths

2005-11-18 Thread David Ascher
On 11/18/05, Sune Kirkeby <[EMAIL PROTECTED]> wrote:  I suggest this, because I think it's a rather poor idea; my biggestproblem with it is that it will break under Apache. So suddenlydjango-admin and the handlers do different things, which isbound to cause surprises... That's exactly the kind of f

Re: A fix for all that futzing around with paths

2005-11-18 Thread David Ascher
On 11/17/05, Tim Keating <[EMAIL PROTECTED]> wrote: It's an interesting idea . . . I know why perforce works this way, butI'm curious what problem this addresses. Most of the stuff that livesin the P4CONFIG file is located in /settings.py, as far as I can tell. And I'm not clear how this would solv

Re: [Django] #830: Add AUTHORS file to distribution

2005-11-17 Thread David Ascher
IP discussions are worth having, if often painful.I'm far from an expert (or a lawyer), but as a director of the PSF, I unfortunately have a lot of conversations about this stuff.I worry a bit about the current system "scaling" in the long term, as today's core devs may not stick around for 10 year

Re: Django and AJAX: Setting aside the conflict

2005-11-17 Thread David Ascher
On 11/17/05, Bill de hÓra <[EMAIL PROTECTED]> wrote: Turn it around. Which of the _javascript_ stacks is working now, or iswilling to work, to make it kick ass with Django?I won't speak for him, but I was talking last night to Alex Russell, of Dojo, and he said that he'd tried to talk to the Django

Re: Django and AJAX: Setting aside the conflict

2005-11-16 Thread David Ascher
On 11/16/05, Eugene Lazutkin <[EMAIL PROTECTED]> wrote: > PS: There are some people in Dojo community, who work on form widget,> which supports some validation mechanism. It would be nice to see what> they do.They do have some stuff to validate input. I found this file in their repository:http://do

Re: Django and AJAX: Setting aside the conflict

2005-11-16 Thread David Ascher
On 11/16/05, Robert Wittams <[EMAIL PROTECTED]> wrote: Not to fan the flames, but I think my position has been a bit distinctfrom these:3. There are requirements for the bundled apps to make use of extensiveJS functionality. If we don't bundle an existing toolkit, we will end up inventing a new one