Zend Framework 1.7.0 is now available

New Zend Framework released with many new components and features.

Zend Framework 1.7.0 is now available from the Zend Framework download site:

http://framework.zend.com/download/latest

This release introduces many new components and features, including:

• Zend_Amf with support for AMF0 and AMF3 protocols
• Dojo Toolkit 1.2.1
• Support for dijit editor available in the Dojo Toolkit
• Zend_Service_Twitter
• ZendX_JQuery in extras library
• Metadata API in Zend_Cache
• Google book search API in Zend_Gdata
• Preliminary support for GData Protocol v2 in Zend_Gdata
• Support for skip data processing in Zend_Search_Lucene
• Support for Open Office XML documents in Zend_Search_Lucene indexer
• Performance enhancements in Zend_Loader, Zend_Controller, and server components
• Zend_Mail_Storage_Writable_Maildir enhancements for mail delivery
• Zend_Tool in incubator
• Zend_Text_Table for formatting table using characters
• Zend_ProgressBar
• Zend_Config_Writer
• ZendX_Console_Unix_Process in the extras library
• Zend_Db_Table_Select support for Zend_Paginator
• Global parameters for routes
• Using Chain-Routes for Hostname-Routes via Zend_Config
• I18N improvements
o Application wide locale for all classes
o Data retrieving methods are now static
o Additional cache handling methods in all I18N classes
o Zend_Translate API simplified
• File transfer enhancements
o Support for file elements in subforms
o Support for multifile elements
o Support for MAX_FILES_SIZE in form
o Support for breaking validation chain
o Support for translation of failure ,messages
o New IsCompressed, IsImage, ExcludeMimeType, ExcludeExtension validators
o Support for FileInfo extension in MimeType validator
• Zend_Db_Table_Select adapater for Zend_Paginator
• Support for custom adapters in Zend_Paginator
• More flexible handling of complex types in Zend_Soap


The Zend Framework team would like to thank everyone who made this release possible. As always, our generous ZF community has provided countless new features, bug fixes, documentation translations, etc. We'd also like to thank Adobe Systems and Wade Arnold for contributing the new Zend_Amf component. A big thanks to PHP Belgium and everyone who participated in bug hunt day and/or the Zend Framework bug hunt week.


Source:- prlog.org/

Zend Framework 1.7 Includes DB2/400 Adapter

Zend Technologies, the commercial entity behind the open source PHP programming language and its related development tools, has delivered a new release of its suite of PHP tools. Zend Framework 1.7 includes a general release of the new DB2/400 adapter introduced earlier this year, which should improve the interoperability of PHP applications and DB2/400 data. The update also includes various other AJAX-related enhancements.

Zend provided an early release of the DB2/400 adapter with the delivery of Zend Core for IBM i 2.6 in September. At the time, Zend said the new adapter would provide better, faster, and more secure access to existing data and applications residing on System i server.

After poking and prodding at beta sites and the resolution of various technical issues, the DB2/400 adapter was declared ready for prime time at Adobe Systems's MAX conference in San Francisco last month, which was the venue for the launch of Zend Framework 1.7.

Zend Framework 1.7 brings other enhancements, in addition to the new data adapter. For instance, load times have improved by 25 to 50 percent, Zend says, and support for the Action Message Format (AMF) data transfer protocol should improve the product's integration with Adobe's Flex and Flash programming technologies for creating rich Internet applications (RIAs).

Other enhancements include a new editor for the Dojo Toolkit, called dijit. Dojo, which was introduced to System i shops with Zend Core for IBM i 2.6, is an open-source collection of JavaScript tools designed to help developers implement graphical and architectural elements of AJAX applications. Zend Framework 1.7 also introduces support for JQuery, a popular AJAX library that was contributed by the Zend community to the larger open source community.

In further news, Zend is now selling support subscriptions for IBM i customers utilizing Zend Framework 1.7. The subscriptions give customers access to Zend resources for gaining support over the Web and troubleshooting or answering basic questions. The standard support package costs $1,500 and gives customers access to five Web-based incidents and two hours of consulting, while the premium package, which costs $2,500, provides 10 Web-based incidents and three hours of consulting.

Source:- itjungle.com/

Zend Framework Coding Standard for PHP

Naming Conventions

1. Classes: -

Zend Framework standardizes on a class naming convention whereby the names of the classes directly map to the directories in which they are stored. The root level directory of the ZF standard library is the "Zend/" directory, whereas the root level directory of the ZF extras library is the "ZendX/" directory. All Zend Framework classes are stored hierarchially under these root directories..

Class names may only contain alphanumeric characters. Numbers are permitted in class names but are discouraged in most cases. Underscores are only permitted in place of the path separator; the filename "Zend/Db/Table.php" must map to the class name "Zend_Db_Table".

If a class name is comprised of more than one word, the first letter of each new word must be capitalized. Successive capitalized letters are not allowed, e.g. a class "Zend_PDF" is not allowed while "Zend_Pdf" is acceptable.

These conventions define a pseudo-namespace mechanism for Zend Framework. Zend Framework will adopt the PHP namespace feature when it becomes available and is feasible for our developers to use in their applications.

See the class names in the standard and extras libraries for examples of this classname convention. IMPORTANT: Code that must be deployed alongside ZF libraries but is not part of the standard or extras libraries (e.g. application code or libraries that are not distributed by Zend) must never start with "Zend_" or "ZendX_".

2. Filenames: -

For all other files, only alphanumeric characters, underscores, and the dash character ("-") are permitted. Spaces are strictly prohibited.

Any file that contains PHP code should end with the extension ".php", with the notable exception of view scripts. The following examples show acceptable filenames for Zend Framework classes.:

Zend/Db.php
Zend/Controller/Front.php
Zend/View/Helper/FormRadio.php

File names must map to class names as described above.

3. Functions and Methods: -

Function names may only contain alphanumeric characters. Underscores are not permitted. Numbers are permitted in function names but are discouraged in most cases.

Function names must always start with a lowercase letter. When a function name consists of more than one word, the first letter of each new word must be capitalized. This is commonly called "camelCase" formatting.

Verbosity is generally encouraged. Function names should be as verbose as is practical to fully describe their purpose and behavior.

These are examples of acceptable names for functions:

filterInput()
getElementById()
widgetFactory()

For object-oriented programming, accessors for instance or static variables should always be prefixed with "get" or "set". In implementing design patterns, such as the singleton or factory patterns, the name of the method should contain the pattern name where practical to more thoroughly describe behavior.

For methods on objects that are declared with the "private" or "protected" modified, the first character of the variable name must be an underscore. This is the only acceptable application of an underscore in a method name. Methods declared "public" should never contain an underscore.

Functions in the global scope (a.k.a "floating functions") are permitted but discouraged in most cases. Consider wrapping these functions in a static class.

4. Variables: -

Variable names may only contain alphanumeric characters. Underscores are not permitted. Numbers are permitted in variable names but are discouraged in most cases.

For instance variables that are declared with the "private" or "protected" modifier, the first character of the variable name must be a single underscore. This is the only acceptable application of an underscore in a variable name. Member variables declared "public" should never start with an underscore.

As with function names (see section 3.3) variable names must always start with a lowercase letter and follow the "camelCaps" capitalization convention.

Verbosity is generally encouraged. Variables should always be as verbose as practical to describe the data that the developer intends to store in them. Terse variable names such as "$i" and "$n" are discouraged for all but the smallest loop contexts. If a loop contains more than 20 lines of code, the index variables should have more descriptive names.

5. Constants: -

Constants may contain both alphanumeric characters and underscores. Numbers are permitted in constant names.

All letters used in a constant name must be capitalized.

Words in constant names must be separated by underscore characters. For example, EMBED_SUPPRESS_EMBED_EXCEPTION is permitted but EMBED_SUPPRESSEMBEDEXCEPTION is not.

Constants must be defined as class members with the "const" modifier. Defining constants in the global scope with the "define" function is permitted but strongly discouraged.

Source:- framework.zend.com/

Zend Framework Coding Standard for PHP

PHP File Formatting

1. General

For files that contain only PHP code, the closing tag ("?>") is never permitted. It is not required by PHP, and omitting it prevents the accidental injection of trailing whitespace into the response.
IMPORTANT: Inclusion of arbitrary binary data as permitted by __HALT_COMPILER() is prohibited from PHP files in the Zend Framework project or files derived from them. Use of this feature is only permitted for some installation scripts.

2. Indentation

Indentation should consist of 4 spaces. Tabs are not allowed.

3. Maximum Line Length

The target line length is 80 characters. That is to say, ZF developers should strive keep each line of their code under 80 characters where possible and practical. However, longer lines are acceptable in some circumstances. The maximum length of any line of PHP code is 120 characters.

4. Line Termination

Line termination follows the Unix text file convention. Lines must end with a single linefeed (LF) character. Linefeed characters are represented as ordinal 10, or hexadecimal 0x0A.

Note: Do not use carriage returns (CR) as is the convention in Apple OS's (0x0D) or the carriage return/linefeed combination (CRLF) as is standard for the Windows OS (0x0D, 0x0A).

Source:- framework.zend.com/