Switch naming scheme to *.html instead of *.txp

[textpattern]

Switch naming scheme to *.html instead of *.txp

[philwareham]

But @gocom states .txp as one of the possible file extensions. There may be a good reason for using .html (syntax highlighting), however I use the Coda Textpattern mode which recognises .txp extensions and provides better highlighting for that. I'll let Jukka make the final decision on this.

[petecooper]

Personally, it makes no difference to me either way - I'm also a Coda jockey, but without the Textpattern plugin. The basis for this is that I'm making a new theme and I've looked at the source for textpattern-default-theme, which refers (quite rightly) to *.txp files. I recalled @gocom's comments about *.html from the linked thread, and was curious about the disparity. Please don't take this issue as me rabble rousing or being That Guy, Phil - I'm just attempting to unify some stuff and -- perhaps unrealistically -- kickstart a somewhat stagnant 3rd party front-end theme development effort.

[philwareham]

All comments and discussions are good even if they don't eventually become commits, so don't be shy in raising issues. I don't know if *.html is better than *.txp - I can see arguments for both cases (more people will be using IDEs that recognise *.html rather than amount of users with Coda and Textpattern Mode, for example).

[petecooper]

In the same vein, forms aren't necessarily HTML; some are, some aren't - put a Textpattern tag in and it's no longer HTML, right? Thinking out loud (and rhetorically, too), that can be ignored.

[philwareham]

Off topic - the Textpattern bits for Coda can be found here: https://github.com/philwareham/Textpattern-for-Panic-Coda

The mode works fairly OK - I fudged it together from someone else's initial work without really knowing much about how it functions. Code auto-completion doesn't work though for Textpattern tags.

[philwareham]

Yeah, as soon as Textpattern tags are used it's not strictly HTML - and Textpattern forms could just be a Textpattern tag and nothing else, in theory (although that's a bit wasteful).

[gocom]

The txp extension is fine. Most editors allow mapping file extensions anyways (unless your editor is absolute garbage), and using distinct one allows the editor to give specific syntax support and autocompletion for Textpattern templates.

In the same vein, forms aren't necessarily HTML; some are, some aren't - put a Textpattern tag in and it's no longer HTML, right? Thinking out loud (and rhetorically, too), that can be ignored.

Template files are just data. The extension tells the system consuming the data what it should use it as, an not necessarily what it actually contains, or what the included templating or programming language generates.

[mauricevancooten]

Works fine for Sublime Textedit 2. I found the .txp extensions self explanatory, for the syntax rendering I set the files to HTML, works!