#2614: Pick a default extension for Django templates
-----------------------------+----------------------------------------------
Reporter: Allan Odgaard | Owner: adrian
Status: closed | Component: Template system
Version: | Resolution: wontfix
Keywords: | Stage: Design decision needed
Has_patch: 0 | Needs_docs: 0
Needs_tests: 0 | Needs_better_patch: 0
-----------------------------+----------------------------------------------
Comment (by lukeplant):
The problem with your double extension idea is that many editors may not
be so easily configurable as TextMate. In that case, you have HTML
templates and plain text templates etc all with the same extension i.e.
.django, instead of the normal extension, .html/.txt/.js. So now, neither
my editor nor my operating system know what to do with these files,
whereas before they would have opened them correctly as HTML, plain text
and javascript files respectively, which is what I wanted (I don't happen
to use a Django mode when editing any of these templates).
I actually don't want my operating system to give me special icons for
these templates -- I want them to display the icon for the underlying file
type. Also, when I am browsing files, my operating system displays
previews automatically, and using my convention it gets the previews for
HTML correct without any configuration -- see
http://files.lukeplant.fastmail.fm/public/konq_html_preview.png -- and I
like this very much.
So, for me, .django.html etc. would work much better (although just .html
works fine, and .django is just more stuff to type). However, there is a
case for .html.django, especially if you have just one editor for Django
templates, or one Django mode in your editor.
The point I'm making is that what works for '''you''' doesn't necessarily
work for '''me''', and in fact may make my life harder -- the convention
you have picked does not degrade gracefully in my case. (Sorry if that
sounded confrontational -- by 'you' and 'me' I mean 'one person' and
'someone else'). Rather than get mixed up in the politics of all this,
Django is just extension neutral. Authors are free to pick conventions
that suit them and their tools. If you receive files from someone else,
you have to live with their conventions (just like living with tabs vs
spaces in code files), or use tools which will minimise the pain.
--
Ticket URL: <http://code.djangoproject.com/ticket/2614#comment:16>
Django Code <http://code.djangoproject.com/>
The web framework for perfectionists with deadlines
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
