I don't share gismo's view that we need a unique extension. I'm happy
with html extensions for my html files but it seems silly to require
one extension for all templates! What about other types such as emails
or dynamic css files? We shouldn't be forced to use a single file
extension for all temp
On 3/20/06, James Bennett <[EMAIL PROTECTED]> wrote:
>
> On 3/19/06, limodou <[EMAIL PROTECTED]> wrote:
> > But there is no editor can deal with django template, so .html maybe
> > the most suitable file extension.
>
> TextMate has a bundle for Django templates.
>
If you say that and I think NewEd
On 3/19/06, limodou <[EMAIL PROTECTED]> wrote:
> But there is no editor can deal with django template, so .html maybe
> the most suitable file extension.
TextMate has a bundle for Django templates.
--
"May the forces of evil become confused on the way to your house."
-- George Carlin
--~--~--
On 3/20/06, gismo <[EMAIL PROTECTED]> wrote:
>
> >But there is no editor can deal with django template, so .html maybe
> >the most suitable file extension.
> I meant this exactly. People can write an extension but how. especially
> for unix world, people use emacs, and vi , and adding a new extens
>But there is no editor can deal with django template, so .html maybe
>the most suitable file extension.
I meant this exactly. People can write an extension but how. especially
for unix world, people use emacs, and vi , and adding a new extension
is very common. Take this there is extensions for r
On 3/20/06, gismo <[EMAIL PROTECTED]> wrote:
>
> I know I can change the extension. But there is a lot of editors,
> people write some extension for them, and only way to handle file type
> is the extensions. Everytime template act like html but you have some
> codes inside of it and when you use
On 3/19/06, gismo <[EMAIL PROTECTED]> wrote:
> I know I can change the extension. But there is a lot of editors,
> people write some extension for them, and only way to handle file type
> is the extensions.
On some operating systems, that's true, but not all.
> Everytime template act like html b
I know I can change the extension. But there is a lot of editors,
people write some extension for them, and only way to handle file type
is the extensions. Everytime template act like html but you have some
codes inside of it and when you use editors you need some special
approach to special file
On 3/20/06, gismo <[EMAIL PROTECTED]> wrote:
>
> you picked .html as extension for template, but it is not a good idea.
> Because it is confusing for editors, when you edit files with .html
> extension, editors think it is an html file and your environment
> setting up as an html enviroment. When
you picked .html as extension for template, but it is not a good idea.
Because it is confusing for editors, when you edit files with .html
extension, editors think it is an html file and your environment
setting up as an html enviroment. When people write extensions for
editors (like emacs or vi)
1+ for smarter cache
On 12/2/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
> > > So, are you interested in PHP realization with main idea explained?
> > Yes
>
> Ok, hope it will be interesting:
>
> In my CMS there is (there was?) such an abstraction: node. Node - it's
> everything - it's a n
On 3/18/06, James Bennett <[EMAIL PROTECTED]> wrote:
> 1. The new example of usage for a generic view is counterintuitive;
> now we pass a QuerySet instead of the app_label/module_name, which is
> fine, but the example on the wiki is:
>
> from myproject.blog.models import Entry
> info_dict = {'que
12 matches
Mail list logo
