Re: Choosing a JS framework to go together with Django
Am Dienstag, den 04.09.2012, 17:37 +0100 schrieb Tom Evans: > On Tue, Sep 4, 2012 at 4:48 PM, Paul Menzel <pm.deb...@googlemail.com> wrote: > > Am Dienstag, den 04.09.2012, 12:08 -0300 schrieb Rafael E. Ferrero: > >> Sorry paul... my bad... "without any problem" i mean. > >> > >> extract of index.html: > >> > >> >> "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd;> > >> http://www.w3.org/1999/xhtml;> > >> > >> > >> ... > >> do you see something wrong there, maybe a mistake?? > > > > Strange. Loading it now worked without problems. Sorry for the noise, > > although I think you should add two more »"« after html and before > > utf-8. > > No, you really shouldn't: > > http://www.w3.org/TR/1999/REC-html401-19991224/charset.html#spec-char-encoding Right. Thanks, I should have checked before suggesting something. I will shut up now and keep wondering why Midori did not display it correctly the first time I viewed the page. Thanks, Paul signature.asc Description: This is a digitally signed message part
Re: Choosing a JS framework to go together with Django
Am Dienstag, den 04.09.2012, 12:08 -0300 schrieb Rafael E. Ferrero: > Sorry paul... my bad... "without any problem" i mean. > > extract of index.html: > > "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd;> > http://www.w3.org/1999/xhtml;> > > > ... > do you see something wrong there, maybe a mistake?? Strange. Loading it now worked without problems. Sorry for the noise, although I think you should add two more »"« after html and before utf-8. Thanks, Paul signature.asc Description: This is a digitally signed message part
Re: Choosing a JS framework to go together with Django
Dear Rafael, Am Dienstag, den 04.09.2012, 11:55 -0300 schrieb Rafael E. Ferrero: > men, i use Jquery on www.expoferiasg.com.ar and works quite well.. > with any problem. s,with,without,? Additionally your site does not tell my browser what character set it is using and therefore all special signs are not displayed correctly in a browser using UTF-8 by default. And last but not least, though not so important on this list, plain text messages are preferred on mailing lists [1]. ;-) Thanks, Paul [1] http://en.opensuse.org/openSUSE:Mailing_list_netiquette signature.asc Description: This is a digitally signed message part
Re: Getting into professional django development
Am Mittwoch, den 19.10.2011, 07:54 +0530 schrieb kenneth gonsalves: > On Tue, 2011-10-18 at 16:47 +0200, Paul Menzel wrote: > > > > > 1.3 belongs to the stone age - since you are learning, it would be a > > > > > good idea to work with the current svn trunk, updating every week or > > > > > so. > > > > > -- > > > > > > > > s/1.2/1.3/ > > > > > With all due respect to Mr. Gonsalves, I do not care to work with the > > > Django trunk unless I'm just playing around with something. My goal > > > is always to produce a production quality application. Even the more > > > stable than average Django trunk cannot provide the consistency needed > > > to deliver an app to a customer. Plus, I don't need the extra work of > > > basing my code on a moving target. When trunk becomes v1.4, I will > > > convert my applications and upgrade. > > > > Please read the message you are referring to again. Kenneth corrected > > the post [2] (although the `sed`-command should be `s/1.3/1.2/`. »The > > latest official version is 1.3.1.« [1], so Kenneth suggested to use > > the current stable release. > > not right - I meant to say that 1.2 belongs to the stone age. I thought that is what I wrote. Maybe I need to improve my English. > I think the sed command is correct. The to be replaced term goes first. $ echo "1.3" | sed s/1.2/1.3/ 1.3 $ echo "1.2" | sed s/1.2/1.3/ 1.3 I hope I did not misunderstood something this time. Thanks, Paul signature.asc Description: This is a digitally signed message part
Re: Getting into professional django development
Am Dienstag, den 18.10.2011, 16:00 +0100 schrieb Tom Evans: > On Tue, Oct 18, 2011 at 3:47 PM, Paul Menzel <pm.deb...@googlemail.com> wrote: > > Dear Dan, > > > > > > [Reordering the message so that it is easier to see the connection.] > > > > Am Dienstag, den 18.10.2011, 06:46 -0700 schrieb Dan Gentry: > > > >> On Oct 18, 3:10 am, kenneth gonsalves <law...@thenilgiris.com> wrote: > >> > On Tue, 2011-10-18 at 12:36 +0530, kenneth gonsalves wrote: > >> > > On Mon, 2011-10-17 at 23:45 -0700, Kevin wrote: > >> > > > Currently I have been focusing on the following: > >> > > >> > > > * Django 1.2 > >> > > >> > > 1.3 belongs to the stone age - since you are learning, it would be a > >> > > good idea to work with the current svn trunk, updating every week or > >> > > so. > >> > > -- > >> > > >> > s/1.2/1.3/ > > > >> With all due respect to Mr. Gonsalves, I do not care to work with the > >> Django trunk unless I'm just playing around with something. My goal > >> is always to produce a production quality application. Even the more > >> stable than average Django trunk cannot provide the consistency needed > >> to deliver an app to a customer. Plus, I don't need the extra work of > >> basing my code on a moving target. When trunk becomes v1.4, I will > >> convert my applications and upgrade. > > > > Please read the message you are referring to again. Kenneth corrected > > the post [2] (although the `sed`-command should be `s/1.3/1.2/`. »The > > latest official version is 1.3.1.« [1], so Kenneth suggested to use the > > current stable release. > > > > I can't stand incorrect pedantry - this is my curse. > > Kenneth actually said that "1.3 is ancient, you should be using > trunk", which he corrected to "1.2 is ancient, you should be using > trunk". His advice, regardless of which version you look at, is to use > trunk - not the latest stable release. You are right. I am sorry. […] Thanks, Paul signature.asc Description: This is a digitally signed message part
Re: Getting into professional django development
Dear Dan, [Reordering the message so that it is easier to see the connection.] Am Dienstag, den 18.10.2011, 06:46 -0700 schrieb Dan Gentry: > On Oct 18, 3:10 am, kenneth gonsalveswrote: > > On Tue, 2011-10-18 at 12:36 +0530, kenneth gonsalves wrote: > > > On Mon, 2011-10-17 at 23:45 -0700, Kevin wrote: > > > > Currently I have been focusing on the following: > > > > > > * Django 1.2 > > > > > 1.3 belongs to the stone age - since you are learning, it would be a > > > good idea to work with the current svn trunk, updating every week or > > > so. > > > -- > > > > s/1.2/1.3/ > With all due respect to Mr. Gonsalves, I do not care to work with the > Django trunk unless I'm just playing around with something. My goal > is always to produce a production quality application. Even the more > stable than average Django trunk cannot provide the consistency needed > to deliver an app to a customer. Plus, I don't need the extra work of > basing my code on a moving target. When trunk becomes v1.4, I will > convert my applications and upgrade. Please read the message you are referring to again. Kenneth corrected the post [2] (although the `sed`-command should be `s/1.3/1.2/`. »The latest official version is 1.3.1.« [1], so Kenneth suggested to use the current stable release. > I know - I'm a dinosaur. That has nothing to do with this. Thanks, Paul [1] https://www.djangoproject.com/download/ [2] http://en.opensuse.org/openSUSE:Mailing_list_netiquette signature.asc Description: This is a digitally signed message part
Re: forum and blog for developers
Am Sonntag, den 22.05.2011, 08:17 +0800 schrieb Russell Keith-Magee: > On Sunday, May 22, 2011, feiwrote: > > I have been using Django for a while. The documentation for the Django > > official web page is great, plus the free online django book. There > > are enough documentations to get started using Django. However, I feel > > there is a missing blog for Django developers. > > Django has a blog - it's linked from the homepage. > > http://djangoproject.com/weblog > > However, it's only used for large project announcements (releases, > conferences, and so on). I guess there are already Django developers with blogs and Django related posts. Just aggregate those into a planet (blog aggregation) planet.djangoproject.com like a lot of projects, for example Debian [1], Gentoo [2] or Fedora [3] have. […] Thanks, Paul [1] http://planet.debian.org/ [2] http://planet.gentoo.org/ [3] http://planet.fedoraproject.org/ signature.asc Description: This is a digitally signed message part
Re: Cherokee for home developing
Dear Rob, Am Freitag, den 29.10.2010, 02:45 -0700 schrieb Robbington: […] > Actually I mentioned Uwsgi, > > Perhaps if you are going to state potential bugs with software you > could be so kind as to add the specifics in your posts and not just > ambiguous statements such as "Do not use the uwsgi wizard: it's > currently broken" we are not all as dedicated to the Cherokee mailing > list as your good self. I had a quick look, here is a small excerpt: > > "If you manually set the uWSGI source you will have no problem but the > wizard make wrong assumptions" > > Now I appreciate, as I am sure my fellow Django-ers are, that you > brought this issue to light, but you could have saved some trouble as > I mentioned before. I agree. Pasting links to the archives is always beneficial for the readers of the messages. > I cant help but feel your tone to be slightly obnoxious, maybe that's > just me, but these forums are to share experience and assist those who > are new or have a problem. You would do well to acknowledge that. I did not find Max’s style obnoxious, he stated the matter very outright(?)/brisk. (I prefer interleaved style when replying though [1].) Thank you for all your input. […] Thanks, Paul [1] https://secure.wikimedia.org/wikipedia/en/wiki/Posting_style#Placement_of_replies signature.asc Description: This is a digitally signed message part
Re: Django editor for Debian
Dear Nicolae, Am Dienstag, den 15.12.2009, 23:58 -0800 schrieb NMarcu: >Can you tell me a good Django editor for Debian? Something more > pretty then default text editor. Something to can edit templates also. what did you end up with? Thanks, Paul signature.asc Description: Dies ist ein digital signierter Nachrichtenteil
Re: New to Django, can't get it running on the web through http://127.0.0.1:8000/
Am Dienstag, den 08.12.2009, 08:54 -0800 schrieb Jenn Hughes: > I'm not sure what you mean by box. »box« in this case means computer or system. Thanks, Paul signature.asc Description: Dies ist ein digital signierter Nachrichtenteil
Re: I want to cancel the subscription for django-users group
Am Dienstag, den 17.11.2009, 10:17 +0100 schrieb "Gosálvez Prados, Diana": > Quiero darme de baja la suscripción al grupo google django-users > > I want to cancel the subscription for django-users group > -- > You received this message because you are subscribed to the Google Groups > "Django users" group. > To post to this group, send email to django-us...@googlegroups.com. > To unsubscribe from this group, send email to > django-users+unsubscr...@googlegroups.com. ^^ Hope that helps. signature.asc Description: Dies ist ein digital signierter Nachrichtenteil
Re: domains vs sub-domains
Am Montag, den 09.11.2009, 21:38 -0800 schrieb Chris: > I've recently been in discussion about which is better to have. > > http://media.example.com OR > http://example.com/media/ > > 1) The first method, I've been told, allows you to make more requests. > IE for example can only make like 4 requests at a given time on a > given domain. but, if you use sub-domains, you can make additional > requests (4 additional in the example of IE). I am not sure, but I think if you use SSL this could lead to problems because some files are loaded from a different server. […] signature.asc Description: Dies ist ein digital signierter Nachrichtenteil
Re: Fixtures for django.contrib.sites.Site
Am Mittwoch, den 01.04.2009, 17:49 -0400 schrieb Adam Nelson: > How do I do a fixture for the Site model? I've tried all sorts of > different model names > > > [ > { > "model": "sites.site", > "pk": 1, > "fields": { > "domain": "example.com", > "name": "Example" > } > }, > ] > > > And I get this error: > ... > File > "/Library/Python/2.5/site-packages/django/utils/simplejson/decoder.py", line > 221, in JSONArray > raise ValueError(errmsg("Expecting object", s, end)) > ValueError: Expecting object: line 10 column 1 (char 124) > > > Any ideas for the correct model name? I've tried every possibility I > can think of. Is the last colon }, correct? If that does not help, use dump the data of the database and see how the syntax is. Thanks, Paul signature.asc Description: Dies ist ein digital signierter Nachrichtenteil