Textpattern CMS support forum

You are not logged in. Register | Login | Help

#11 2015-06-23 18:38:26

hcgtv
Plugin Author
From: Miami, Florida
Registered: 2005-11-29
Posts: 2,634
Website

Re: Working with Pages and Forms on the backend

Bloke wrote #291893:

Do you think form-name.type.txp is the right approach to keep things alphabetised by name, or is it handier to group them by type.form-name.txp like rah_flat does?

I don’t know, we haven’t decided yet if “Form Type” will become “Theme”.

But I’ll change the plugin to be type.form-name.txp to match the backend display like you suggest.

Offline

#12 2015-06-23 19:01:34

philwareham
Core designer
From: Farnham, Surrey, UK
Registered: 2009-06-11
Posts: 3,096
Website

Re: Working with Pages and Forms on the backend

Probably type.form-name.txp would get my vote, since that groups the forms into their type, then alpha orders them.

Offline

#13 2015-06-23 22:26:17

hcgtv
Plugin Author
From: Miami, Florida
Registered: 2005-11-29
Posts: 2,634
Website

Re: Working with Pages and Forms on the backend

hcg_themes 0.5 output:

themes
└── default-4.5.7
    ├── forms
    │   ├── article.article_listing.txp
    │   ├── article.comments_display.txp
    │   ├── article.default.txp
    │   ├── article.search_results.txp
    │   ├── comment.comment_form.txp
    │   ├── comment.comments.txp
    │   ├── comment.popup_comments.txp
    │   ├── file.files.txp
    │   ├── link.plainlinks.txp
    │   ├── misc.images.txp
    │   └── misc.search_input.txp
    ├── pages
    │   ├── archive.txp
    │   ├── default.txp
    │   └── error_default.txp
    └── styles
        └── default.css

4 directories, 15 files

Type before Form name, still don’t get what type is good for?

As a grouping mechanism for the backend, so you can collapse and expand your forms, that is if you have 50+ forms, I get it, but in the grand scheme of things, it’s confusing for the new user.

Offline

#14 2015-06-23 22:39:43

Bloke
Developer
From: Leeds, UK
Registered: 2006-01-29
Posts: 8,462
Website

Re: Working with Pages and Forms on the backend

hcgtv wrote #291900:

As a grouping mechanism for the backend, so you can collapse and expand your forms, that is if you have 50+ forms, I get it, but in the grand scheme of things, it’s confusing for the new user.

Yeah the types do seem rather arbitrary. I mean, a Section form type? I’ve started using that group for broad-stroke layout code, like head-meta, head-css, head-js, page-header, page-footer and so forth. Anything article-related goes in the Article group (though I’ve never used the Preview thing), reusable gallery code in the Images group, and so forth, with any remaining bits and bobs in Misc.

But without any clear distinction between them, you’re right it might seem confusing to newcomers. Ruud has often campaigned for the removal of Forms entirely since (besides the dubious preview feature) they offer nothing that a Page couldn’t also offer, as long as there was a suitable tag like <txp:output_form /> to render them. There’s some merit in that. The loss of the stupid name would be the most welcome benefit! It’s only the backwards-compatibility card that stands in the way, really.


The smd plugin menagerie — for when you need one more gribble of power from Textpattern. Bleeding-edge code available on GitHub.

Txp Builders – finely-crafted code, design and Txp

Offline

#15 2015-06-23 22:47:28

philwareham
Core designer
From: Farnham, Surrey, UK
Registered: 2009-06-11
Posts: 3,096
Website

Re: Working with Pages and Forms on the backend

I’ve long been against the name ‘Forms’ for these template pieces (favouring partials) but I do think they have a distinction from overall pages templates, so I think they need to stay in some form (sorry for the pun).

I would kill the preview ‘feature’ though, it’s utterly useless and makes things look like they are broke when they are not.

Offline

#16 2015-06-24 00:33:17

jstubbs
Moderator
From: Hong Kong
Registered: 2004-12-13
Posts: 2,393
Website

Re: Working with Pages and Forms on the backend

Partials or snippets gets my vote.

Offline

#17 2015-06-24 06:09:49

bici
Member
From: vancouver
Registered: 2004-02-24
Posts: 1,320
Website

Re: Working with Pages and Forms on the backend

jstubbs wrote #291906:

Partials or snippets gets my vote.

fior me : Snippets or Includes


…. texted postive

Offline

#18 2015-06-24 07:06:14

philwareham
Core designer
From: Farnham, Surrey, UK
Registered: 2009-06-11
Posts: 3,096
Website

Re: Working with Pages and Forms on the backend

Are we changing the name? This was about whether the snippets/forms are needed (which they are, I think). Unless you had another form type of ‘pages’ and lumped everything within a templates section.

It’s probably best to stay with what we have currently though – it’s too ingrained in the system to change easily (tag names would need to change, attribute names too).

Offline

Board footer

Powered by FluxBB