just pushing this here for dave to see, I forget that when emails are
addressed to me and the list, reply sends to the user and do not hit "L" to
reply to the list.
@dave: This is the idea we came up with.
On Wednesday, February 23, 2011 05:29:55 am you wrote:
> Maybe you could write a filter "urlsafe" to use into templates so that
> variable does not contains javascript.
> And you could create a command that scan templates and raise an alert every
> variable inside an href attribute that is not "urlsafe".
>
Already has one, this is not the real goal.
> But I believe that a tool is used to work, not to do the work for me. And
> Django is a tool.
> It's like the java paradox, java is a language that hidden a lot of
> problems, and try to resolve them without the programmers. Result: you
> cannot trust a java programmer, because often he doesn't know what the code
> really does.
>
> For this reason, I see that this kind of problems are better if you leave
> resolve by developers. The better solution is to document better the
> problem.
>
I agree here.
> I think it is out of the scope of djangodevtools.
> In other words, djangodevtools not is a library to development, but is a
> library to help the development process itself.
>
Think of this more of a pylint type tool that helps developers by issuing
warnings when scanned over the code/template, not changing code for the
developer. In this mindset, I can see it being perfect for djangodevtools.
It still leaves the decision to change it or accept it up to the developers
and won't hurt running code.
As pointed out in the previous thread, a lot of developers. Especially new
developers who think you can just put together some html, some database code
and come up with a website that's on par with a professionally built one. Also
at times when it's late in the day, experienced developers are not above
making simple mistakes. This would help both situations.
Mike.
Hey, I had to let awk be better at *something*... :-)
-- Larry Wall in <1991nov7.200504.25...@netlabs.com>1
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en.
