On 17 Dez., 04:23, Malcolm Tredinnick <malc...@pointy-stick.com>
wrote:
> So the problem that you are now mentioning is that you registered the
> name first and decided to ask check if there might be a problem only
> afterwards. I'm really not trying to be a hard-ass here, but that's not
> a motivating factor. The solution is still simple. You just don't upload
> anything. You pick a better, different name and use that. You tell the
> CPAN guys you made a mistake in registering the original name. What
> happens if somebody makes a typo in the name of their package, for
> example? There must be plenty of cases of accidental registration.
I probably will have to do that then :(
Still I would prefer it to be called Django::Template and stay very
close to the Django specification.
In my view Djangos templates are pretty much a defined file format and
the Django::Template module provides an interface for those files.
That's why I think it is a fitting name.
Like for example YAML files, which has a lot of parsers. And in every
language I want to use it, I just google for YAML and language name
and there I go. Given the choice between YAML::Syck or
Data::File::Structured I go for the YAML::Syck module first and might
have overlooked the other one. And all search engines I know treat the
title as special. http://search.cpan.org/search?m=all&q=YAML is not
showing Activator::Registry first but behind all the other module with
YAML in the title.
>As I said, I don't really have any power of decision here.
Ok if someone with that power tells me no, I won't do it.
This is really a matter of opinion, some say that people who provide
an interface to their files are are infringing their copyright and
others think that having the ability to access those files in other
languages might strengthen their format and benefit their users and
maybe even themselves.
I personaly don't like that with switching a framework, or being
forced to switch by an employer, you have to learn a new programming
language, a new template language and maybe a new database. This takes
a lot of time and effort. If you could use the old templates in the
new language you might have some less work to do. Just as a general
concept. There are like a gazillion template languages out there, and
I like Djangos the best, but I have to work in Perl for my current
project (because I spent like a year of code in perl in it)
--~--~---------~--~----~------------~-------~--~----~
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
django-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/django-developers?hl=en
-~----------~----~----~----~------~----~------~--~---
