Porting from Django 0.96 to 1.0 doc improvement
Hello, I had hard time to find that I need to add primary_key=True to my OneToOneFields to make it work as with 0,96. I still don't understand why I need add that for 1.0. Could you please add some lines about this in the doc ? Thanks again for Django 1.0, Olivier. --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~--~~~~--~~--~--~---
Re: Newforms: colon after label
A BIG +1 for me On 29 mar, 16:34, "James Bennett" <[EMAIL PROTECTED]> wrote: > On 3/29/07, Ted <[EMAIL PROTECTED]> wrote: > > > Were I work we have had to do this very thing to support I18N in our > > forms. Something as simple as a ":" is not a given. Maybe I want a > > " :" instead? This could be a form parameter or even a locale setting. > > FWIW I think the ideal would be for the default string representation > of the form to not add any punctuation at all -- adding options to > configure this just feel too ugly, so the proper solution should be > for the form to not do it, and trust to application developers to > present the form in whatever way they want (if that means no > colon/other punctuation, then the default will still be fine; if not, > the templating isn't all that complicated and provides absolute > control of the output). > > -- > "Bureaucrat Conrad, you are technically correct -- the best kind of correct." --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~--~~~~--~~--~--~---
Re: Upcoming Django release, and the future
+1 for me On Mar 1, 5:19 pm, "James Bennett" <[EMAIL PROTECTED]> wrote: > On 3/1/07, David Larlet <[EMAIL PROTECTED]> wrote: > > > What about bug #2282? What's the actual status? A patch is proposed, > > it doesn't suit any case but it's a good start for a part of the > > world. > > It still needs a discussion and decision about how far we want to go > to support (essentially) arbitrary Unicode in slugs. That's come up a > time or two, and there's never been any sort of consensus on a best > practice, so I'd say this probably isn't going to change before 0.96. > > -- > "Bureaucrat Conrad, you are technically correct -- the best kind of correct." --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~--~~~~--~~--~--~---
Re: Graham Dumpleton about mod_python
Malcom, The context of this comment is http://www.djangoproject.com/documentation/modpython/#c2029 What I would like to know is if something has been done or will be to ensure that Django works along with mod_python 3.3. As far as I understand this will allow us to run any taste of Apache in any case (this worker prefork MPM blahblah which is gibberish to me). --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers -~--~~~~--~~--~--~---
Graham Dumpleton about mod_python
Hi folks, Have you read the following from Django Comments, what do you think of it ? Graham Dumpleton August 17, 2006 at 11:59 p.m. You really need to provide an explanation of why the worker MPM cannot be used and the prefork MPM must be used. The reason is that this doesn't make a lot of sense. On a Win32 system, how Apache works is not much different to a worker MPM on a UNIX system with the exception that there is only one Apache child process, whereas on UNIX there can be multiple Apache child processes. In other words, both on Win32 and when worker MPM on UNIX is used there can be multiple concurrent requests being handled in separate threads within the same Apache child process. Thus, if the problem is related to multithreading, if it doesn't work with the worker MPM, it probably shouldn't work on Win32 systems either. The only thing I can think of is that this advice is based on the use of a version of mod_python prior to version 3.2.8. These older versions had a number of issues in relation to multithreaded MPMs which could cause problems. But then, this would have affected both Win32 and UNIX worker MPM. So, please explain. Also, if it is believed that not being able to use worker MPM is related to mod_python, as opposed to Django, you really should communicate with the mod_python folks about it. Keeping up to date with what the mod_python folks are up to would also be a good idea with mod_python 3.3 getting near to be finished. This is because it will have a completely new module importer and there is always a small risk that it may not play well with Django. You may therefore want to ensure you do some testing with the development version in advance of mod_python 3.3 actually being released. --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers -~--~~~~--~~--~--~---
Re: Making URLconfs accept view objects, not just paths to views
+1 We already have to import models to use generic views, then, for the sake of consistency, it seems normal to have to import views as well. Yes, keep objects as objects everywhere is possible. --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers -~--~~~~--~~--~--~---
Re: Django/Dojo integration: take a look and speak up
in fact, since I've rolled back to a 3 days old version I no longer need to do this modification. If it happens again wih a fresher svn update I will let you know. Now I'm convinced that we need Dojo, I will help as much as I can. --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers -~--~~~~--~~--~--~---
Re: Django/Dojo integration: take a look and speak up
in fact, since I've rolled back to a 3 days old version I no longer need to do this modification. If it happens again wih a fresher svn update I will let you know. Now I'm convinced that we need Dojo, I will help as much as I can. --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers -~--~~~~--~~--~--~---
Re: Django/Dojo integration: take a look and speak up
Sorry, I came back to the version MR version I had two days ago and it is better now. But the filter above the left list does not work, JS console says: Erreur : SelectFilter is not defined Fichier source : http://localhost:8000/media/js/dojo/dojo.js Ligne : 187 Erreur : SelectFilter is not defined Fichier source : http://localhost:8000/media/js/dojo/dojo.js Ligne : 186 Note: the fact that I have to rename this is still relevant: ManyToOne by ForeignKey ManyToMany by ManyToManyField Now just a silly question: what is the value added by Dojo ? --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers -~--~~~~--~~--~--~---
Re: Django/Dojo integration: take a look and speak up
What I see is a simple multiselection list, so I suspect that the related Dojo is not loaded. --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers -~--~~~~--~~--~--~---
Re: Django/Dojo integration: take a look and speak up
My copy of MR has been updated yesterday evening.
How do I specify the use of Dojo rich-text editing widget in my model ?
I don't know why M2M does not render properly, here is an excerpt of
the displayed page source:
...
dojo.setModulePrefix('django', '../django');
var admin_media_prefix = '/media/';
dojo.require('django.admin');
...
Operating system:
HP/UX
IBM AIX
IBM OS/390
Sun Solaris
Windows 2000
Windows 2000 sp4
Windows NT
Hold down "Control", or "Command" on a Mac, to select
more than one.
--~--~-~--~~~---~--~~
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 [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-developers
-~--~~~~--~~--~--~---
Re: Django/Dojo integration: take a look and speak up
James, to make it work I had to replace in your views all occurences of: ManyToOne by ForeignKey ManyToMany by ManyToManyField The only problem for me so far is that TextField are no more handled by TinyMCE. Just one reproach: the widget use for ManyToMany was better before Dojo (MultiSelect combolists are ugly). Good work anyway. Olivier. --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers -~--~~~~--~~--~--~---
Re: installperms and/or sqlinitialdata
Yes, what you need is: python manage.py syncdb Olivier. --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers -~--~~~~--~~--~--~---
