Re: Ticket 9483
On Nov 4, 2008, at 15:26, H. de Vries wrote: > From a publishing point of view, I don't know for sure Python's method > is correct. Personally, I don't think so. I'd have to say, if Python's misbehaving, Python should be patched. And also, I'm strictly against making the title filter not behave as str.title does, because let's face it, a lot of template designers are Python programmers. It's also really a corner case, and I wouldn't sacrifice the Python titlecase implementation just for this one corner case (and which legitimate words do use semicolons in the middle of them?) - Ludvig --~--~-~--~~~---~--~~ 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: Dynamic SITE_ID (again)
Hello, > Now I know from reading all of the previous discussions that this > really isn't such an easy implementation, but given the state of > Django today, how much work would really be involved? For that matter, > what design direction would be the preferred one? I'm also interested by this "pony", so if a design decision is made, I can try to write a patch or to improve an existing one. -- Fabien SCHWOB --~--~-~--~~~---~--~~ 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: Ticket 9483
On Nov 7, 3:07 am, Ludvig Ericson <[EMAIL PROTECTED]> wrote: > On Nov 4, 2008, at 15:26, H. de Vries wrote: > > > From a publishing point of view, I don't know for sure Python's method > > is correct. Personally, I don't think so. > > I'd have to say, if Python's misbehaving, Python should be patched. > > And also, I'm strictly against making the title filter not behave as > str.title does, because let's face it, a lot of template designers are > Python programmers. > > It's also really a corner case, and I wouldn't sacrifice the Python > titlecase implementation just for this one corner case (and which > legitimate words do use semicolons in the middle of them?) > > - Ludvig For English (U.S. English at least), it should also not capitalize articles (a, an, the, etc). I don't know the rules for other languages, but I have heard they are different. So given this, if there was an effort to make the title filter better, it might be worthwhile to put it under the localization stuff. --~--~-~--~~~---~--~~ 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: Ticket 9483
On Nov 7, 2008, at 14:46, varikin wrote: > For English (U.S. English at least), it should also not capitalize > articles (a, an, the, etc). I don't know the rules for other > languages, but I have heard they are different. So given this, if > there was an effort to make the title filter better, it might be > worthwhile to put it under the localization stuff. You try making an implementation of the actual English title casing rules, and let me know how that goes. :P str.title is a very simple title casing function, and there's a reason for that. Ludvig Ericson --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
contrib.comments: working example must make a boost.
Hi all, @mtredinnick, @jacob, @wilson, @ubernostrum not sure if any "community boosts" are at all wanted here, but finally django is not for a closed circle of django-gurus and things are for the larger audience, isn't it? :) so, why there is no easy-to-launch example of last contrib.comments code? Look, I've spent about 3 (three) hours in total on 1.searching the example, 2. trying to get stable version somehow working according to wiki, then 3. the "trunk" things running according to wiki.The stable things are too old. The trunk's ones are too young. In the case of contrib.comments as I see it now, I'd definitely stick to trunk. How could one get it somehow usable? -- Examples are needed. A simple rule of mine regarding the community and bounce rate: * 1 person who is leaving after having no success in 3 hours equals to: * 2 more pragmatic persons who stop after 1.5 hours of no success -- and this is equal to: * 4 of even more pragmatic persons who stop after 45 min of no success trying the things they need for their Goal... and? what does it equal? :) * 8 pers and 25 mins ... * 16 pers and 15 mins * 32 pers and 10 mins * 64 pers and 5 min :) * 128 pers looking at WORKING live demo! * 256 pers who never seen even the demo but have been reading in blogs how cool has been the experience about django and its contrib.comments. Sum them all up. Just single me and those hundreds. I don't want really enter the long discussions. I'd like to know how could I help getting such an example running. (Of course, I have some work copy) Kind regards Valery --~--~-~--~~~---~--~~ 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: contrib.comments: working example must make a boost.
Valery wrote: > Hi all, @mtredinnick, @jacob, @wilson, @ubernostrum > > not sure if any "community boosts" are at all wanted here, but finally > django is not for a closed circle of django-gurus and things are for > the larger audience, isn't it? :) so, why there is no easy-to-launch > example of last contrib.comments code? > > Look, I've spent about 3 (three) hours in total on 1.searching the > example, 2. trying to get stable version somehow working according to > wiki, then 3. the "trunk" things running according to wiki.The stable > things are too old. The trunk's ones are too young. In the case of > contrib.comments as I see it now, I'd definitely stick to trunk. How > could one get it somehow usable? -- Examples are needed. > > A simple rule of mine regarding the community and bounce rate: > > * 1 person who is leaving after having no success in 3 hours equals > to: > > * 2 more pragmatic persons who stop after 1.5 hours of no success -- > and this is equal to: > > * 4 of even more pragmatic persons who stop after 45 min of no success > trying the things they need for their Goal... and? what does it > equal? :) > > * 8 pers and 25 mins ... > > * 16 pers and 15 mins > > * 32 pers and 10 mins > > * 64 pers and 5 min :) > > * 128 pers looking at WORKING live demo! > > * 256 pers who never seen even the demo but have been reading in blogs > how cool has been the experience about django and its > contrib.comments. > > Sum them all up. > > Just single me and those hundreds. I don't want really enter the long > discussions. I'd like to know how could I help getting such an example > running. (Of course, I have some work copy) > > With a positive attitude like that I *really* hope you will be at the PyCon sprints next year! As far as Django's concerned I'm pretty much a user not a developer, but they do have a very knowledgeable and helpful community on both sides of the line. regards Steve --~--~-~--~~~---~--~~ 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: contrib.comments: working example must make a boost.
> With a positive attitude like that I *really* hope you will be at the > PyCon sprints next year! Chicago, IL -- uhhh, quite far... :) > As far as Django's concerned I'm pretty much a > user not a developer, but they do have a very knowledgeable and helpful > community on both sides of the line. OK, Steve, consequences? I have a bad looking form after following the trunk's wiki, in my form I can see - entries without any tag at all and this all when those guru's are telling me "tables is a bad thing, just let the content flow!" Ok, I am kinda equipped with a DIV-magic wand and am quite happy to let the content flow, just let me know my contrib.comment- friends are :) Whatever friends, definitely, it is not the biggest prob we are facing :) I wish you a nice evening and a nice weekend coming. Looking forward to hearing from you regards Valery --~--~-~--~~~---~--~~ 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: contrib.comments: working example must make a boost.
Valery wrote: > >> With a positive attitude like that I *really* hope you will be at the >> PyCon sprints next year! > > Chicago, IL -- uhhh, quite far... :) > Maybe so, but it *is* possible to apply for assistance with funding. Not all such requests can succeed, but you could consider applying. Keep your eye on us.pycon.org. > >> As far as Django's concerned I'm pretty much a >> user not a developer, but they do have a very knowledgeable and helpful >> community on both sides of the line. > > OK, Steve, consequences? I have a bad looking form after following the > trunk's wiki, in my form I can see - entries without any > tag at all and this all when those guru's are telling me > "tables is a bad thing, just let the content flow!" > > Ok, I am kinda equipped with a DIV-magic wand and am quite happy to > let the content flow, just let me know my contrib.comment- > friends are :) > I'm no CSS angel, but holdenweb.com now only uses a table layout for the home page. It does make the inner pages much more flexible. My latest attempt (as test.holdenweb.com) currently breaks in IE ... > Whatever friends, definitely, it is not the biggest prob we are > facing :) No, but for well-designed web systems good HTML and CSS is important. > I wish you a nice evening and a nice weekend coming. > > Looking forward to hearing from you > K hope you have a good weekend also. regards Steve -- Steve Holden+1 571 484 6266 +1 800 494 3119 Holden Web LLC http://www.holdenweb.com/ --~--~-~--~~~---~--~~ 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: contrib.comments: working example must make a boost.
On Sat, Nov 8, 2008 at 6:45 AM, Valery <[EMAIL PROTECTED]> wrote: > > Hi all, @mtredinnick, @jacob, @wilson, @ubernostrum > > not sure if any "community boosts" are at all wanted here, but finally > django is not for a closed circle of django-gurus and things are for > the larger audience, isn't it? :) so, why there is no easy-to-launch > example of last contrib.comments code? ... > Just single me and those hundreds. I don't want really enter the long > discussions. I'd like to know how could I help getting such an example > running. (Of course, I have some work copy) How can you help? By doing it. Build it, and they will come. :-) Seriously - you don't have to ask for permission to help out. If you think there is an area where Django needs more/better/different documentation or examples, then dig in and get your hands dirty. There are many ways that you could make this happen: 1) The obvious solution would be to write a new tutorial or example page that could be distributed as part of the core documentation. Write up the docs in ReST format, and submit them as a ticket. It might take a while to get through the editorial process, but then your tutorial would be part of the Django core for ever more. 2) Blog about it. Write an N part series on setting up comments on a site. There are certain blogs (such as James Bennett's B-list) that are well known and oft-referenced sources of unofficial documentation of common tasks. 3) Screencast about it. Screencasts can be a more engaging way to demonstrate something by doing it, live on camera. 4) Set up a demo site, and provide the code for that site. I notice that how-to-use-django-comments.com is available... :-) Good ideas are easy to have - I usually have three or four each time I have a shower. Executing is much harder. Any contribution is welcome, but if you want to see improvement, you have to contribute. I look forward to seeing your contribution :-) 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~--~~~~--~~--~--~---
