官术网_书友最值得收藏!

Will a Tag Solve My Problem?

As in the previous recipe, you know that we have three different possibilities for extending CMS Made Simple and solving a problem: User-Defined Tag, Tags, and Modules. Deciding which of these is the best approach, however, requires additional knowledge about the strengths and weaknesses of each technique.

This recipe will help you examine your problem and consider whether creating a Tag is the most appropriate solution.

How to do it...

The criteria for deciding to use a Tag to extend CMS Made Simple are quite similar to the criteria for a User-Defined Tag.

To figure this out, consult the following list, and determine if each item applies to the problem you are trying to solve. Feel free to write down a list of your answers (yes/no).

  1. Can your problem be solved with Smarty logic in your page template?
  2. Are you trying to solve a problem that requires multiple actions? An example of multiple actions would be both displaying a form and processing its results.
  3. Will you need to support localization and internationalization to solve your problem? For example, if your code will be displaying messages, will the messages need to be translated into multiple languages?
  4. Will your solution require an Administration panel?
  5. Do you need to create new database tables or set up new preferences to solve your problem?

If you answered "no" to all of the above questions, either a Tag or a User-Defined Tag would be a viable approach. To decide whether a Tag would be better than a UDT, consider the following questions:

  1. Will you want to share this solution with other people so they can install it into their own CMS Made Simple sites, or will you want to reuse this code yourself on other sites?
  2. Do you want your code to display help text in the Admin area, so site administrators understand what parameters are available and what the code does?
  3. Will your solution serve as a Smarty modifier? A Smarty modifier is a function that reformats a variable for display, for example, {$variable|uppercase} where the modifier ("uppercase") serves to transform the variable ("$variable").

If you answer "yes" to any of these three questions, you should write a Tag instead of a User-Defined Tag.

How it works...

A Tag is a way to connect a Smarty tag to some PHP code. The PHP code can do anything. Like in the case of User-Defined Tags, there are very few things that cannot be done in CMS Made Simple using Tags.

Because Tags are so versatile, the best way to determine if they are the ideal approach is by disqualification. We ask questions about the few things for which Tags are not ideal, to see if any of those things match our requirements. If none of them match, then the problem could be solved by either a Tag or a User-Defined Tag. To make the decision between those two approaches, we consider a few other criteria that will steer us in the right direction.

Let's consider the disqualifying questions again and examine why they would encourage us to use a different approach. The first five questions are the same as they were for User-Defined Tags.

Now, let's consider the three things that differentiate a Tag from a User-Defined Tag:

See also

  • Will a User-Defined Tag Solve My Problem recipe?
  • Will a Module Solve My Problem recipe?
  • Create a "Hello World" Tag recipe
主站蜘蛛池模板: 都江堰市| 塔河县| 新乐市| 简阳市| 中山市| 漳浦县| 浦城县| 北川| 湖南省| 开原市| 福贡县| 无锡市| 昌宁县| 北票市| 漳平市| 定南县| 宜宾市| 甘德县| 弥勒县| 泽普县| 文化| 瓦房店市| 隆昌县| 轮台县| 盐池县| 阿勒泰市| 枣强县| 顺平县| 时尚| 皮山县| 定西市| 新晃| 舟曲县| 义马市| 柘荣县| 博野县| 民勤县| 蒙自县| 贞丰县| 汝阳县| 交口县|