Textpattern CMS support forum
You are not logged in. Register | Login | Help
- Topics: Active | Unanswered
Re: Style(s) tab
Yep. “Forms” needs a new name too.
That’s been mentioned a bunch before – don’t remember seeing a final conclusion.
I guess that one is more complicated since it’s a tag attribute. I say change the name and deprecate “forms” as an attribute for another few releases (that’ll give everyone a couple years to make the change) – wink.
Offline
#14 2008-11-13 03:14:22
- masa
- Member
- From: Asturias, Spain
- Registered: 2005-11-25
- Posts: 1,091
Re: Style(s) tab
renobird wrote:
Yep. “Forms” needs a new name too.
This one’s difficult though.
I’ve seen suggestions to rename it to Snippets or Includes , but I think that is very misleading. To me Snippet means a bit of static code/content, but forms are much more.
In fact I’m quite happy with the term Form , since it implies that it can pull in other content and “whip it into shape” anyway you want.
Offline
Re: Style(s) tab
“Templates” for pages and I think “includes” would be an appropriate replacement for forms. If you were creating a static site you would use “php include” wouldn’t you?
Stuart
In a Time of Universal Deceit
Telling the Truth is Revolutionary.
Offline
#16 2008-11-13 15:48:07
- net-carver
- Archived Plugin Author
- Registered: 2006-03-08
- Posts: 1,648
Re: Style(s) tab
Other candidate names that are relatively free of existing txp/plugin bias might include…
- fragments
- units
- pieces
- blocks
- patterns
- bits-n-bobs
- whatnots
- whimwams
- thingy-me-jigs
:)
Despite good reasoning to want to change the name from ‘forms’ to something not-to-be-confused with HTML forms, it seems to me that the term ‘form’ is tightly bound to the tag attributes and would require a lot of changes to the taghandlers code; in turn requiring rework on sites that received the new name-bearing version of txp — unless that was also automated as part of any such update.
— Steve
Offline
Re: Style(s) tab
OK. So “forms” proves to be a tough change – how about the others?
Devs?
Offline
Re: Style(s) tab
maniqui wrote:
For “Forms”, the spanish translation (“Formularios”) is totally misleading, because “formulario” means form but in the sense of a web form (ie. a contact form).
You allways can become a translater. As for me, I sometimes ask opinions of russian txp community – how to translate such string. It’s rather difficult to select such translation, that will not have any double-meanings
Providing help in hacking ATM! Come to courses and don’t forget to bring us notebook and hammer! What for notebook? What a kind of hacker you are without notebok?
Offline
Re: Style(s) tab
Els wrote:
…after all it is CSS, isn’t it?
This was my feeling on it too and thus why I threw that out there. Nothing gives clearer indication where to find the CSS than a tab that reads CSS. On the other hand, while it makes pretty good sense in the admin-side interface, I can see where this might introduce documentation headaches.
Par contre, I think “Templates” is a more questionable replacement for Pages, especially for people coming to Txp from other CMS systems that use the term “template” to mean a predefined look (as in skin design), which is not the same thing here conceptually. If you think about it, “template” means a lot of things; it’s not as cut and dry as CSS, for example, and thus opens up more potential for confusion. I would leave Pages alone, personally.
Last edited by Destry (2008-11-14 11:33:20)
Offline
#20 2008-11-14 13:19:27
- els
- Moderator
- From: The Netherlands
- Registered: 2004-06-06
- Posts: 7,458
Re: Style(s) tab
Actually I don’t mind at all if the tab names stay as they are now. But it would be great if there were a possibility to name the tabs in preferences, something like the way you can name the custom fields now. Especially for clients’ sites, depending on the client’s needs and/or abilities you could create tab names that show unambiguously what they are meant for. I can imagine that sometimes ‘sections’ would make much more sense if it were named ‘pages’, or ‘pages’ would do better as ‘code’. You could even name tabs like ‘Code (STAY OUT!)’ ;)
Offline
Re: Style(s) tab
Els, that was an unexpected added bonus from MLP- you can rename everything, so I changed a few things to more newbie-user friendly names.
~~~~~~~~~~~~~| monolinea.com | pixilate.com | istockphoto.com/kemie |~~~~~~~~~~~~~
Offline
Re: Style(s) tab
Els wrote:
But it would be great if there were a possibility to name the tabs in preferences.
Not a bad idea for core use. That would seem to solve the hairy “form” issue too. Leave all the code alone and just let a person start using the semantics on the surface that makes sense to them or their clients. Actually, better chalk that up to interesting. There would have to be some kind of baseline for docs at least, and that could run afoul if you have clients looking at their customized admin-side and comparing that with TextBook docs, for example.
(Or, just add the “s” to the styles tab and I’ll be happy. :) )
Last edited by Destry (2008-11-14 14:05:35)
Offline
#23 2008-11-14 14:14:14
- els
- Moderator
- From: The Netherlands
- Registered: 2004-06-06
- Posts: 7,458
Re: Style(s) tab
kemie wrote:
Els, that was an unexpected added bonus from MLP- you can rename everything, so I changed a few things to more newbie-user friendly names.
Kemie, yes I know, and if you don’t have MLP it can also be changed in the txp_lang table directly, but in both situations your changes will be gone with every Txp or language update… the l10n strings are kept when updating Txp, but not the Txp core strings.
Last edited by els (2008-11-14 14:17:50)
Offline
#24 2008-11-14 14:16:48
- els
- Moderator
- From: The Netherlands
- Registered: 2004-06-06
- Posts: 7,458
Re: Style(s) tab
Destry wrote:
and that could run afoul if you have clients looking at their customized admin-side and comparing that with TextBook docs, for example.
You are right, I had not thought of that. But most clients (mine at least) don’t look at TextBook docs ;)
Offline