New listings

Demonstrate a web environment where 'public' (i.e. non-authenticated) users and 'member' users have access restrictions, and to what context they may visit those resources. In a lot of ways this broad concept relates very well to small-medium sites of a lot of Zend developers (in my opinion). For purpose of clarity we will assume this is a SIG group for Mac Users to discuss all things Mac OS X-related. The site has 3 areas (home, news, tutorials) that are for the general public. Members can also view a discussion forum, community newsletter and support request area for members to share common problems.

Web site developers are familiar with a concept that a site consists of pages but Zend Framework proposes Controller/Action idea. Undoubtedly, Controller/Action is cool but how is it relevant to real world tasks? In other words, how is Controller/Action connected to the standard form flow?

I was wondering about how to extend a singleton class such that you could retrieve the new class when retrieving the singleton later. In particular, Zend_Controller_Front is a singleton, but what if I want to extend it later? A number of plugins in the Zend Framework, particularly view helpers and routing functionality, make use of the singleton; would I need to alter all of these later so I could make use of the new subclass ?

One of the new features to hit the Zend Framework since 0.7 is Zend_Controller_ModuleRouter and its sibling Zend_Controller_ModuleRewriteRouter. This allows for separating out sets of controlers, models and views into their own modules.

This article can be useful to anyone who is trying to add a PHP application, like WordPress or MediaWiki to the Web application that uses the Zend_Controller class, which is a part of Zend Framework.

This tutorial is for developers who want to learn about creating a simple mashup, a Web application that uses information from different sources. It uses the Zend Framework's Zend_Services component and the principle of Representational State Transfer (REST) to demonstrate how to seamlessly include information to extra resources related to our feeds.
Using the examples of Amazon Web Services (AWS), Flickr Services, and Yahoo! Search Web services, this tutorial teaches you how to apply the PHP Zend Framework to quickly search those sites for relevant information. You will integrate this functionality into the Chomp feed reader developed in the previous parts of this series.

In Part 8 of this series, we added Yahoo!, Amazon, and Flickr results to the Chomp application. Now we're going to improve performance by loading only the data the user requests, when the user requests it.

Zend_View is a class for working with the "view" portion of the model-view-controller pattern. That is, it exists to help keep the view script separate from the model and controller scripts. It provides a system of helpers, output filters, and variable escaping.
Zend_View is template system agnostic; you may use PHP as your template language, or create instances of other template systems and manipulate them within your view script.
Essentially, using Zend_View happens in two major steps: 1. Your controller script creates an instance of Zend_View and assigns variables to that instance. 2. The controller tells the Zend_View to render a particular view, thereby handing control over the view script, which generates the view output.

Zend_Service_Yahoo is a simple API for using many of the Yahoo! REST APIs. Zend_Service_Yahoo allows you to search Yahoo! Web search, Yahoo! News, Yahoo! Local, Yahoo! Images.

Zend_Service_Flickr is a simple API for using the Flickr REST Web Service.