Textpattern CMS support forum

You are not logged in. Register | Login | Help

#11 2017-04-25 06:18:09

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

Re: Rebrand contact form plugin

Ok, I’ve come round to the idea of <txp:contact /> so +1 from me.

Offline

#12 2017-04-25 06:18:36

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

Re: Rebrand contact form plugin

If txp:contact is too simplistic, how about txp:connect.

Offline

#13 2017-04-25 09:22:25

jakob
Admin
From: Germany
Registered: 2005-01-20
Posts: 3,553
Website

Re: Rebrand contact form plugin

gomedia wrote #305465:

+1 for txp:contact – maintains some familiarity with the past, less typing, and also we don’t then have code like <txp:html_form_text html_form="xx" />.

True, both are good points.

One more idea, though: how about txp:input?


TXP Builders – finely-crafted code, design and txp

Offline

#14 2017-04-25 10:45:57

Destry
Moderator
From: Haut-Rhin
Registered: 2004-08-04
Posts: 4,233
Website

Re: Rebrand contact form plugin

You’re welcome.

– Mr. Unfriendly1

–––

1 Sometimes you have to rattle a tree.


The text persuades, the *notes prove。

Offline

#15 2017-04-25 12:36:58

maverick
Member
From: Southeastern Michigan, USA
Registered: 2005-01-14
Posts: 960
Website

Re: Rebrand contact form plugin

re: the name

txp:contact is okay. Not a fan of html_form for reasons already stated by others. txp:input would seem broader. Or perhaps txp:event (not in terms of calendar event, but in terms of some input or other item is triggering an action on the front side type event). Though that isn’t necessarily any better than txp:contact or txp:input. Just an alternative for the sake of brainstorming if txp:form is out.

Offline

#16 2017-04-25 13:12:22

NicolasGraph
Plugin Author
From: France
Registered: 2008-07-24
Posts: 860
Website

Re: Rebrand contact form plugin

Hi,
input is for me the most generic word after form, but honestly I would prefer form, even if it may be confusing with Txp forms. form is just how it is called and how people would search for it. Txp forms should maybe not be named forms. I know that it won’t change but is it a reason to spread alternative tag names?
Furthermore, we are talking about a new plugin name isn’t it, not a core tag?

Last edited by NicolasGraph (2017-04-25 13:13:49)


Nicolas
Follow me on Twitter and GitHub!
Multiple edits are usually to correct my frenglish…

Offline

#17 2017-04-25 13:23:48

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

Re: Rebrand contact form plugin

form isn’t going to fly, sorry, unless it’s prefixed with a plugin author prefix like <txp:pub_form /> or was <txp:contact_form />. Otherwise you’d get something like <txp:form form="my_form" /> which looks confusing to me.

Offline

#18 2017-04-25 13:35:06

NicolasGraph
Plugin Author
From: France
Registered: 2008-07-24
Posts: 860
Website

Re: Rebrand contact form plugin

philwareham wrote #305477:

[…] unless it’s prefixed with a plugin author prefix […]

Wouldn’t it be?

Last edited by NicolasGraph (2017-04-25 13:41:34)


Nicolas
Follow me on Twitter and GitHub!
Multiple edits are usually to correct my frenglish…

Offline

#19 2017-04-25 13:36:42

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

Re: Rebrand contact form plugin

NicolasGraph wrote #305478:

Wouldn’t it be?

I guess so.

Offline

#20 2017-04-25 13:48:39

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

Re: Rebrand contact form plugin

Wooooooah, hold up everyone!

It’s a plugin, it still needs a prefix. All this talk of making it a core plugin/module is somewhat premature, imo. Bottom line, the plugin adds a slew of tags for creating different types of input control. I don’t want to add this plugin to core, because we already have waaay too many tags.

txp:contact is a noble idea, but what of the 10-15 other tags? txp:contact_text, txp:contact_email, txp:contact_textarea, txp:contact_radio, …it gets daft.

This is really just about the plugin getting a more useful title, with suitable prefix. One day I’d like to expand core’s email ability now everything’s in a lovely central class so maybe at that point we can revisit the plugin and integrate it more tightly with the core’s mail system.


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

Board footer

Powered by FluxBB