On Tue, 2008-10-28 at 15:52 -0700, IMTheNachoMan wrote:
> I have a thought for improvement. Currently the template files use
> a .html extension for template files.
That's not correct. Template files can have any extension you like.
Django deliberately does not use the file extension to mean anything.
> While this system works I think
> it could be improved.
>
> Having a file as .html implies it is an HTML file. The template files
> are not complete HTML therefore not valid HTML files, in my opinion.
>
> Like from an IDE or editors perspective. If an IDE/editor opens
> a .html file it has no way of knowing it is a template verses a true
> HTML file.
An editor that uses file extensions as the sole means to determine the
file type has a bug. There are many file types that incorporate data
from multiple formats and tools have to be able to handle that. It's
really a solved problem. Django's templates are just one example: they
will often include both Django template directives and HTML code (and
also Javascript and CSS code, which are common in files with .html
extensions).
> A user can quickly look at the contents and know. An editor
> could look at all the code and look for certain words like {% blah %}
> but that's in-efficient.
Claims of inefficiency are invariably subjective. Yes, it's more work
than zero, but that's also just a strawman. The point is whether the
amount of work required is noticeable or wasteful. And in the case of
filetype detection, the answer is "no". It's the normal way to do file
type detection: look at the first X number of bytes (X can be small, but
can be as large as the whole file, since files aren't really that big
and computers are very fast). Your OS does this all the time and you
never notice.
A very good way to detect Django template files for example is to check
for "{% block %}" or "{% extends %}". I know of a couple of different
editors that use that. Often combining it with their normal detection
for HTML or Javascript so that they can use both groups of syntax
highlighting and code completion at once.
If don't want to use .html as the extension for you predominantly
HTML-including tempaltes, you don't have to. The same as you don't need
to use .txt for your text-based templates and so on. Django leaves it
entirely up to you. But please let's not wheel out the old "editors only
use file extensions" red-herring. Tool writers (at least outside of
Microsoft) have known for years that that is both unreliable and
insecure.
Best wishes,
Malcolm
--~--~---------~--~----~------------~-------~--~----~
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 [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---
