|  |   | | One of Smartys primary design goals is to facilitate the separation of application code from presentation. Typically, the application code contains the business logic of your application, written and maintained in PHP code. This code is maintained by programmers. The presentation is the way your content is presented to the end user, which is written and maintained in template files. The templates are maintained by template designers.
 At its most basic function, the application code collects content, assigns it to the template engine and displays it. The content might be something like the headline, tagline, author and body of a newspaper article. The application code has no concern how this content will be presented in the template. The template designer is responsible for the presentation. They edit the template files, adding markup and bringing it to completion. This typically involves things like HTML tags, cascading style sheets and other tools provided by the template engine.
This paradigm serves several purposes:
*) Designers can't break application code. They can mess with the templates all they want, but the code stays intact. The code will be tighter, more secure and easier to maintain.
*) Errors in the templates are confined to the Smartys error handling routines, making them as simple and intuitive as possible for the designer.
*) With presentation on its own layer, designers can modify or completely redesign it from scratch, all without intervention from the programmer.
*) Programmers aren't messing with templates. They can go about maintaining the application code, changing the way content is acquired, making new business rules, etc. without disturbing the presentation layer.
*) Templates are a close representation of what the final output will be, which is an intuitive approach. Designers don't care how the content got to the template. If you have extraneous data in the template such as an SQL statement, this opens the risk of breaking application code by accidental deletion or alteration by the designer.
*) You are not opening your server to the execution of arbitrary PHP code. Smarty has many security features built in so designers won't breach security, whether intentional or accidental. They can only do what they are confined to in the templates.
|
 | | COCAiN. CO. engine gives customer an unique tool to realize it's expectations. It's developed as most as possible to be easy in expansion. All text files are kept in one directory. This gives user very easy way to edit all page texts.
Besides multi-language implementation gives.
· opportunity to reach more people
· in future, develop site to international status.
It's easy to mantain and easy to expand on new languages. |
 | | COCAiN. CO. delivers a framework with modular contruction. It gives very easy to expand code. In our shop you can buy extensions to our engine like new libraries, modules (ex. download module etc.). It's brilliant opportunity. Ask yourself. Who gives so much options as we? |
 | | Due to maximization of perfomance our source code is compressed as most as it can be. It's done in the final web generation process, when site is requested (not in code). It lowers bandwich, provides faster page load for user and reduces server load which cuts page generation time. If you want to check this solution, simply view this page source by clicking 2nd mouse button and selecting 'view source' (or pressing Ctrl+U in some web browsers). |
 | | We provide to all of our website products friendly URLs (like: http://site.com/contact), cause we think that they're very important part of each site. Main adventages of short and user-friendly links are (about usability):
· easy to communicate and remember: current or potential customers can easily remember the address for personal use or distributing via word of mouth, e-mail, and so forth.
· short enough to be pasted: this is a facet of communication - the address should be short enough to be pasted in an e-mail without wrapping. The addr. is often mangled when/if it wraps, leaving the user to reconstruct it.
· easy to guess: users should be able to discern an address (within reason) by what they are trying to do. A good example is the news section of the Google site; you can get to it by adding news to the Google address like this www.google.com/news. Along the same line, the book section of Amazon.com is easy to access with the address www.amazon.com/books.
· presentable: the URLs should be short and legible enough to appear in company brochures and so forth.
· easy to type: the address should be easy on the fingers when typing into the address area of a browser via a conventional keyboard or mobile device. The length of the address will be a major issue with mobile users who often work with limited input devices.
Resources.
* http://www.sitepoint.com/article/search-engine-friendly-urls/ [1]
* http://www.alistapart.com/articles/succeed [2]
* http://www.seoconsultants.com/articles/1000/urls.asp [3]. |
|
|
