From c4cf99f7b47f8bb5d245f5d1cf2373a50a9438bb Mon Sep 17 00:00:00 2001 From: thomas Date: Sun, 11 Apr 2010 10:50:47 +0000 Subject: [PATCH] [MANUAL] English: - unified classnames with classname git-svn-id: http://framework.zend.com/svn/framework/standard/trunk@21821 44c647ce-9c0f-0410-b52a-842ac1e357ba --- .../manual/en/module_specs/Zend_Filter.xml | 2 +- .../manual/en/module_specs/Zend_Filter_Input.xml | 3 +- .../en/module_specs/Zend_Http_Client-Advanced.xml | 22 +++++----- .../manual/en/module_specs/Zend_Http_Client.xml | 11 ++--- .../manual/en/module_specs/Zend_Http_Response.xml | 4 +- .../Zend_Ldap-API-Ldap-Node-RootDse.xml | 5 ++- .../Zend_Ldap-API-Ldap-Node-Schema.xml | 5 ++- .../en/module_specs/Zend_Ldap-API-Ldap-Node.xml | 10 +++-- .../manual/en/module_specs/Zend_Ldap-API-Ldap.xml | 12 ++--- .../manual/en/module_specs/Zend_Log-Overview.xml | 7 +-- .../en/module_specs/Zend_Oauth-GettingStarted.xml | 14 +++--- .../en/module_specs/Zend_Paginator-Advanced.xml | 2 +- .../Zend_Search_Lucene-QueryLanguage.xml | 4 +- .../en/module_specs/Zend_Session-BasicUsage.xml | 8 ++-- .../manual/en/module_specs/Zend_Tool-Extending.xml | 6 +-- .../manual/en/module_specs/Zend_Tool-Usage-CLI.xml | 8 ++-- .../module_specs/Zend_Tool_Framework-Extending.xml | 4 +- .../en/module_specs/Zend_Validate-Between.xml | 4 +- .../en/module_specs/Zend_Validate-GreaterThan.xml | 4 +- .../en/module_specs/Zend_Validate-Hostname.xml | 5 ++- .../en/module_specs/Zend_Validate-StringLength.xml | 5 ++- .../manual/en/tutorials/multiuser-sessions.xml | 51 ++++++++++++---------- .../manual/en/tutorials/paginator-control.xml | 13 +++--- .../manual/en/tutorials/paginator-together.xml | 3 +- .../en/tutorials/quickstart-create-layout.xml | 4 +- 25 files changed, 117 insertions(+), 99 deletions(-) diff --git a/documentation/manual/en/module_specs/Zend_Filter.xml b/documentation/manual/en/module_specs/Zend_Filter.xml index 4bca230ae..c58ec9105 100644 --- a/documentation/manual/en/module_specs/Zend_Filter.xml +++ b/documentation/manual/en/module_specs/Zend_Filter.xml @@ -78,7 +78,7 @@ echo $htmlEntities->filter('"'); // " The first argument of this method is a data input value, that you would pass to the filter() method. The second argument is a string, which corresponds to the basename of the - filter class, relative to the Zend_Filter namespace. The + filter class, relative to the Zend_Filter namespace. The staticFilter() method automatically loads the class, creates an instance, and applies the filter() method to the data input. diff --git a/documentation/manual/en/module_specs/Zend_Filter_Input.xml b/documentation/manual/en/module_specs/Zend_Filter_Input.xml index cc41ac254..eadd147cd 100644 --- a/documentation/manual/en/module_specs/Zend_Filter_Input.xml +++ b/documentation/manual/en/module_specs/Zend_Filter_Input.xml @@ -148,7 +148,8 @@ $validators = array( An object instance of one of the classes that implement - Zend_Filter_Interface or Zend_Validate_Interface. + Zend_Filter_Interface or + Zend_Validate_Interface. Zend_Http_Client does the same - when redirecting on a 301 or 302 response, all GET and POST parameters are reset, and a GET request is sent to the new location. This behavior can be changed by setting the 'strictredirects' configuration @@ -45,7 +45,7 @@ $client->setConfig(array('strictredirects' => false)); Adding Cookies and Using Cookie Persistence - Zend_Http_Client provides an easy interface for adding cookies + Zend_Http_Client provides an easy interface for adding cookies to your request, so that no direct header modification is required. This is done using the setCookie() method. This method can be used in several ways: @@ -67,12 +67,12 @@ $client->setCookie($cookie); ]]> - For more information about Zend_Http_Cookie objects, see + For more information about Zend_Http_Cookie objects, see . - Zend_Http_Client also provides the means for cookie stickiness - + Zend_Http_Client also provides the means for cookie stickiness - that is having the client internally store all sent and received cookies, and resend them automatically on subsequent requests. This is useful, for example when you need to log in to a remote site @@ -102,7 +102,7 @@ $client->request('GET'); ]]> - For more information about the Zend_Http_CookieJar class, see + For more information about the Zend_Http_CookieJar class, see . @@ -167,15 +167,15 @@ $client->setHeaders(array( This method takes a file name as the first parameter, a form name as the second parameter, and data as a third optional parameter. If the third data parameter is NULL, the first file name parameter - is considered to be a real file on disk, and Zend_Http_Client will - try to read this file and upload it. If the data parameter is not + is considered to be a real file on disk, and Zend_Http_Client + will try to read this file and upload it. If the data parameter is not NULL, the first file name parameter will be sent as the file name, but no actual file needs to exist on the disk. The second form name parameter is always required, and is equivalent to the "name" attribute of an >input< tag, if the file was to be uploaded through an HTML form. A fourth optional parameter provides the file's content-type. If - not specified, and Zend_Http_Client reads the file from the disk, + not specified, and Zend_Http_Client reads the file from the disk, the mime_content_type function will be used to guess the file's content type, if it is available. In any case, the default MIME type will be application/octet-stream. @@ -219,7 +219,7 @@ $client->request('POST'); Sending Raw POST Data - You can use a Zend_Http_Client to send raw POST data using the + You can use a Zend_Http_Client to send raw POST data using the setRawData() method. This method takes two parameters: the first is the data to send in the request body. The second optional parameter is the content-type of the data. While this parameter is @@ -263,8 +263,8 @@ $client->setRawData($xml)->setEncType('text/xml')->request('POST'); HTTP Authentication - Currently, Zend_Http_Client only supports basic HTTP authentication. - This feature is utilized using the setAuth() + Currently, Zend_Http_Client only supports basic HTTP + authentication. This feature is utilized using the setAuth() method, or by specifying a username and a password in the URI. The setAuth() method takes 3 parameters: The user name, the password and an optional diff --git a/documentation/manual/en/module_specs/Zend_Http_Client.xml b/documentation/manual/en/module_specs/Zend_Http_Client.xml index 65f2df8ac..0cff7e285 100644 --- a/documentation/manual/en/module_specs/Zend_Http_Client.xml +++ b/documentation/manual/en/module_specs/Zend_Http_Client.xml @@ -18,9 +18,9 @@ The class constructor optionally accepts a URL as its first parameter - (can be either a string or a Zend_Uri_Http object), and an array or - Zend_Config object containing configuration options. Both can be left out, - and set later using the setUri() and setConfig() methods. + (can be either a string or a Zend_Uri_Http object), and an array + or Zend_Config object containing configuration options. Both can + be left out, and set later using the setUri() and setConfig() methods. Instantiating a Zend_Http_Client Object @@ -45,11 +45,12 @@ $client->setConfig($config); - Zend_Http_Client uses Zend_Uri_Http to validate URLs. This means + Zend_Http_Client uses + Zend_Uri_Http to validate URLs. This means that some special characters like the pipe symbol ('|') or the caret symbol ('^') will not be accepted in the URL by default. This can be modified by setting the 'allow_unwise' option of - Zend_Uri to 'TRUE'. See Zend_Uri to 'TRUE'. See for more information. diff --git a/documentation/manual/en/module_specs/Zend_Http_Response.xml b/documentation/manual/en/module_specs/Zend_Http_Response.xml index 2beb6cbb9..3bb49ce69 100644 --- a/documentation/manual/en/module_specs/Zend_Http_Response.xml +++ b/documentation/manual/en/module_specs/Zend_Http_Response.xml @@ -15,9 +15,9 @@ - In most cases, a Zend_Http_Response object will be instantiated + In most cases, a Zend_Http_Response object will be instantiated using the fromString() method, which reads a string containing an HTTP - response message, and returns a new Zend_Http_Response object: + response message, and returns a new Zend_Http_Response object: Instantiating a Zend_Http_Response Object Using the Factory Method diff --git a/documentation/manual/en/module_specs/Zend_Ldap-API-Ldap-Node-RootDse.xml b/documentation/manual/en/module_specs/Zend_Ldap-API-Ldap-Node-RootDse.xml index 27706aa66..386171152 100644 --- a/documentation/manual/en/module_specs/Zend_Ldap-API-Ldap-Node-RootDse.xml +++ b/documentation/manual/en/module_specs/Zend_Ldap-API-Ldap-Node-RootDse.xml @@ -33,7 +33,10 @@ Zend_Ldap_Dn getDn() - Gets the DN of the current node as a Zend_Ldap_Dn. + + + Gets the DN of the current node as a Zend_Ldap_Dn. + diff --git a/documentation/manual/en/module_specs/Zend_Ldap-API-Ldap-Node-Schema.xml b/documentation/manual/en/module_specs/Zend_Ldap-API-Ldap-Node-Schema.xml index 65e35d530..b49f73ac5 100644 --- a/documentation/manual/en/module_specs/Zend_Ldap-API-Ldap-Node-Schema.xml +++ b/documentation/manual/en/module_specs/Zend_Ldap-API-Ldap-Node-Schema.xml @@ -32,7 +32,10 @@ Zend_Ldap_Dn getDn() - Gets the DN of the current node as a Zend_Ldap_Dn. + + + Gets the DN of the current node as a Zend_Ldap_Dn. + diff --git a/documentation/manual/en/module_specs/Zend_Ldap-API-Ldap-Node.xml b/documentation/manual/en/module_specs/Zend_Ldap-API-Ldap-Node.xml index bb9cc119c..993e764b6 100644 --- a/documentation/manual/en/module_specs/Zend_Ldap-API-Ldap-Node.xml +++ b/documentation/manual/en/module_specs/Zend_Ldap-API-Ldap-Node.xml @@ -166,8 +166,9 @@ Zend_Ldap_Dn getCurrentDn() - Gets the current DN of the current node as a Zend_Ldap_Dn. - This does not reflect possible rename-operations. + Gets the current DN of the current node as a + Zend_Ldap_Dn. This does not reflect possible + rename-operations. @@ -175,8 +176,9 @@ Zend_Ldap_Dn getDn() - Gets the original DN of the current node as a Zend_Ldap_Dn. - This reflects possible rename-operations. + Gets the original DN of the current node as a + Zend_Ldap_Dn. This reflects possible + rename-operations. diff --git a/documentation/manual/en/module_specs/Zend_Ldap-API-Ldap.xml b/documentation/manual/en/module_specs/Zend_Ldap-API-Ldap.xml index 9f0c5044b..abe724a29 100644 --- a/documentation/manual/en/module_specs/Zend_Ldap-API-Ldap.xml +++ b/documentation/manual/en/module_specs/Zend_Ldap-API-Ldap.xml @@ -142,8 +142,8 @@ Zend_Ldap disconnect() - Disconnects the Zend_Ldap instance from the LDAP - server. + Disconnects the Zend_Ldap instance from the + LDAP server. @@ -154,10 +154,10 @@ - Connects the Zend_Ldap instance to the given LDAP server. - All parameters are optional and will be taken from the - LDAP connection and binding parameters passed to the - instance via the construtor or via + Connects the Zend_Ldap instance to the given + LDAP server. All parameters are optional and will be + taken from the LDAP connection and binding parameters + passed to the instance via the construtor or via Zend_Ldap::setOptions() when set to NULL. diff --git a/documentation/manual/en/module_specs/Zend_Log-Overview.xml b/documentation/manual/en/module_specs/Zend_Log-Overview.xml index 5bf2713b2..a5f7d57cd 100644 --- a/documentation/manual/en/module_specs/Zend_Log-Overview.xml +++ b/documentation/manual/en/module_specs/Zend_Log-Overview.xml @@ -235,9 +235,10 @@ $logger->setEventItem('pid', getmypid()); Log PHP Errors - Zend_Log can also be used to log PHP errors. Calling - registerErrorHandler() will add Zend_Log before the current - error handler, and will pass the error along as well. + Zend_Log can also be used to log PHP errors. + Calling registerErrorHandler() will add + Zend_Log before the current error handler, and will pass the + error along as well. diff --git a/documentation/manual/en/module_specs/Zend_Oauth-GettingStarted.xml b/documentation/manual/en/module_specs/Zend_Oauth-GettingStarted.xml index 677d1380b..8cbca0407 100644 --- a/documentation/manual/en/module_specs/Zend_Oauth-GettingStarted.xml +++ b/documentation/manual/en/module_specs/Zend_Oauth-GettingStarted.xml @@ -14,8 +14,8 @@ Assuming we have obtained a key and secret, we can start the OAuth workflow by setting up a Zend_Oauth_Consumer instance as - follows passing it a configuration (either an array or - Zend_Config object). + follows passing it a configuration (either an array or Zend_Config + object). In addition, you should note several other configuration values not - explicitly used: requestMethod and requestScheme. By default, - Zend_Oauth_Consumer sends requests as POST (except for a + explicitly used: requestMethod and requestScheme. By default, + Zend_Oauth_Consumer sends requests as POST (except for a redirect which uses GET). The customised client (see later) also includes its authorization by way of a header. Some services may, at their discretion, require alternatives. You can reset the requestMethod (which defaults @@ -175,9 +175,9 @@ if (!empty($_GET) && isset($_SESSION['TWITTER_REQUEST_TOKEN'])) { Success! We have an authorized access token - so it's time to actually use the Twitter API. Since the access token must be included with every - single API request, Zend_Oauth_Consumer offers a ready-to-go HTTP client - (a subclass of Zend_Http_Client) to use either - by itself or by passing it as a custom HTTP Client to another library or + single API request, Zend_Oauth_Consumer offers a + ready-to-go HTTP client (a subclass of Zend_Http_Client) to use + either by itself or by passing it as a custom HTTP Client to another library or component. Here's an example of using it standalone. This can be done from anywhere in your application, so long as you can access the OAuth configuration and retrieve the final authorized access token. diff --git a/documentation/manual/en/module_specs/Zend_Paginator-Advanced.xml b/documentation/manual/en/module_specs/Zend_Paginator-Advanced.xml index 7abeaa20c..9a43d50e9 100644 --- a/documentation/manual/en/module_specs/Zend_Paginator-Advanced.xml +++ b/documentation/manual/en/module_specs/Zend_Paginator-Advanced.xml @@ -255,7 +255,7 @@ interface Zend_Paginator_AdapterAggregate The interface is fairly small and only expects you to return an instance of Zend_Paginator_Adapter_Abstract. An Adapter Aggregate instance is then recognized by both Zend_Paginator::factory and the constructor of - Zend_Paginator and handled accordingly. + Zend_Paginator and handled accordingly. diff --git a/documentation/manual/en/module_specs/Zend_Search_Lucene-QueryLanguage.xml b/documentation/manual/en/module_specs/Zend_Search_Lucene-QueryLanguage.xml index 3dca2f9a2..5a4024378 100644 --- a/documentation/manual/en/module_specs/Zend_Search_Lucene-QueryLanguage.xml +++ b/documentation/manual/en/module_specs/Zend_Search_Lucene-QueryLanguage.xml @@ -268,8 +268,8 @@ roam~0.8 - So Zend_Search_Lucene sets a limit of matching terms per query (subquery). This limit - can be retrieved and set using + So Zend_Search_Lucene sets a limit of matching terms per query + (subquery). This limit can be retrieved and set using Zend_Search_Lucene::getTermsPerQueryLimit()/Zend_Search_Lucene::setTermsPerQueryLimit($limit) methods. diff --git a/documentation/manual/en/module_specs/Zend_Session-BasicUsage.xml b/documentation/manual/en/module_specs/Zend_Session-BasicUsage.xml index f18d786cd..61c6dd066 100644 --- a/documentation/manual/en/module_specs/Zend_Session-BasicUsage.xml +++ b/documentation/manual/en/module_specs/Zend_Session-BasicUsage.xml @@ -26,10 +26,10 @@ $myNamespace = new Zend_Session_Namespace('myNamespace'); // $myNamespace corresponds to $_SESSION['myNamespace'] ]]> - It is possible to use Zend_Session in conjunction with other code that uses - $_SESSION directly. To avoid problems, however, it is highly recommended - that such code only uses parts of $_SESSION that do not correspond to - instances of Zend_Session_Namespace. + It is possible to use Zend_Session in conjunction with other code + that uses $_SESSION directly. To avoid problems, however, it is highly + recommended that such code only uses parts of $_SESSION that do not + correspond to instances of Zend_Session_Namespace. diff --git a/documentation/manual/en/module_specs/Zend_Tool-Extending.xml b/documentation/manual/en/module_specs/Zend_Tool-Extending.xml index 14e137c0e..3a8298204 100644 --- a/documentation/manual/en/module_specs/Zend_Tool-Extending.xml +++ b/documentation/manual/en/module_specs/Zend_Tool-Extending.xml @@ -818,9 +818,9 @@ class Zend_Tool_Framework_Client_Storage Zend_Tool_Project Extensions - Zend_Tool_Project exposes a rich set of functionality and capabilities that make the - task of creating new providers, specficially those targetting project easier and more - manageable. + Zend_Tool_Project exposes a rich set of functionality and + capabilities that make the task of creating new providers, specficially those targetting + project easier and more manageable. diff --git a/documentation/manual/en/module_specs/Zend_Tool-Usage-CLI.xml b/documentation/manual/en/module_specs/Zend_Tool-Usage-CLI.xml index d77cc4113..b48c90e0d 100644 --- a/documentation/manual/en/module_specs/Zend_Tool-Usage-CLI.xml +++ b/documentation/manual/en/module_specs/Zend_Tool-Usage-CLI.xml @@ -385,10 +385,10 @@ zf configure dbadapter "adapter=Pdo_Sqlite&dbname=../data/test.db" -s developmen DbTable - The DbTable provider is responsible for creating Zend_Db_Table - model/data access files for your application to consume, with the proper - class name, and in the proper location in the application. The two - important pieces of information are the DbTable name, + The DbTable provider is responsible for creating + Zend_Db_Table model/data access files for your application to + consume, with the proper class name, and in the proper location in the application. + The two important pieces of information are the DbTable name, and the actual database table name. For example: diff --git a/documentation/manual/en/module_specs/Zend_Tool_Framework-Extending.xml b/documentation/manual/en/module_specs/Zend_Tool_Framework-Extending.xml index b71c8f8f2..a17fdfdbc 100644 --- a/documentation/manual/en/module_specs/Zend_Tool_Framework-Extending.xml +++ b/documentation/manual/en/module_specs/Zend_Tool_Framework-Extending.xml @@ -125,8 +125,8 @@ environment variable. If the environment variable ZF_CONFIG_FILE is set, then its value will be used as the location of the configuration file to use with the Console Client. The - ZF_CONFIG_FILE can point to any Zend_Config readable INI, XML - or PHP File. + ZF_CONFIG_FILE can point to any + Zend_Config readable INI, XML or PHP File. diff --git a/documentation/manual/en/module_specs/Zend_Validate-Between.xml b/documentation/manual/en/module_specs/Zend_Validate-Between.xml index d04724bbb..3426efe4e 100644 --- a/documentation/manual/en/module_specs/Zend_Validate-Between.xml +++ b/documentation/manual/en/module_specs/Zend_Validate-Between.xml @@ -12,8 +12,8 @@ Zend_Validate_Between supports only number validation - It should be noted that Zend_Validate_Between supports only the validation of numbers. - Strings or dates can not be validated with this validator. + It should be noted that Zend_Validate_Between supports only the + validation of numbers. Strings or dates can not be validated with this validator. diff --git a/documentation/manual/en/module_specs/Zend_Validate-GreaterThan.xml b/documentation/manual/en/module_specs/Zend_Validate-GreaterThan.xml index eed8a9258..5847dda5b 100644 --- a/documentation/manual/en/module_specs/Zend_Validate-GreaterThan.xml +++ b/documentation/manual/en/module_specs/Zend_Validate-GreaterThan.xml @@ -12,8 +12,8 @@ Zend_Validate_GreaterThan supports only number validation - It should be noted that Zend_Validate_GreaterThan supports only the validation of - numbers. Strings or dates can not be validated with this validator. + It should be noted that Zend_Validate_GreaterThan supports only + the validation of numbers. Strings or dates can not be validated with this validator. diff --git a/documentation/manual/en/module_specs/Zend_Validate-Hostname.xml b/documentation/manual/en/module_specs/Zend_Validate-Hostname.xml index c3e02e4bf..37c200c40 100644 --- a/documentation/manual/en/module_specs/Zend_Validate-Hostname.xml +++ b/documentation/manual/en/module_specs/Zend_Validate-Hostname.xml @@ -90,7 +90,8 @@ if ($validator->isValid($hostname)) { - The Zend_Validate_Hostname constants are: ALLOW_DNS to allow only + The Zend_Validate_Hostname constants are: + ALLOW_DNS to allow only DNS hostnames, ALLOW_IP to allow IP addresses, ALLOW_LOCAL to allow local network names, and ALLOW_ALL to allow all three types. To just check for IP addresses @@ -112,7 +113,7 @@ if ($validator->isValid($hostname)) { As well as using ALLOW_ALL to accept all hostnames types you can combine these types to allow for combinations. For example, to accept DNS and Local - hostnames instantiate your Zend_Validate_Hostname object as so: + hostnames instantiate your Zend_Validate_Hostname object as so: Zend_Validate_StringLength supports only string validation - It should be noted that Zend_Validate_StringLength supports only the validation of - strings. Integers, floats, dates or objects can not be validated with this validator. + It should be noted that Zend_Validate_StringLength supports only + the validation of strings. Integers, floats, dates or objects can not be validated with + this validator. diff --git a/documentation/manual/en/tutorials/multiuser-sessions.xml b/documentation/manual/en/tutorials/multiuser-sessions.xml index fc64e284f..600359377 100644 --- a/documentation/manual/en/tutorials/multiuser-sessions.xml +++ b/documentation/manual/en/tutorials/multiuser-sessions.xml @@ -24,9 +24,9 @@ In PHP, the session problem is solved by the session extension which utilizes some state tracking, typically cookies, and some form of local storage which is - exposed via the $_SESSION superglobal. In Zend Framework, the component Zend_Session - adds value to the PHP session extension making it easier to use and - depend on inside object-oriented applications. + exposed via the $_SESSION superglobal. In Zend Framework, the component + Zend_Session adds value to the PHP session + extension making it easier to use and depend on inside object-oriented applications. @@ -34,24 +34,26 @@ Basic Usage of Zend_Session - The Zend_Session component is both a session manager as well as an - API for storing data into a session object for long-term persistence. - The Zend_Session API is for managing the options and behavior of a - session, like options, starting and stopping a session, whereas Zend_Session_Namespace - is the actual object used to store data. + The Zend_Session component is both a session manager as well as + an API for storing data into a session object for long-term + persistence. The Zend_Session API is for + managing the options and behavior of a session, like options, starting and stopping a + session, whereas Zend_Session_Namespace is the actual object used + to store data. While its generally good practice to start a session inside a bootstrap process, this is generally not necessary as all sessions will be automatically started upon the first - creation of a Zend_Session_Namespace object. + creation of a Zend_Session_Namespace object. - Zend_Application is capable of configuring Zend_Session for you as part of the - Zend_Application_Resource system. To use this, assuming your project uses - Zend_Application to bootstrap, you would add the following code to your - application.ini file: + Zend_Application is capable of configuring + Zend_Session for you as part of the + Zend_Application_Resource system. To use this, assuming your + project uses Zend_Application to bootstrap, you would add the + following code to your application.ini file: - Most Zend Framework components that use sessions need nothing more to use Zend_Session. - At this point, you an either use a component that consumes Zend_Session, or start - storing your own data inside a session with Zend_Session_Namespace. + Most Zend Framework components that use sessions need nothing more to use + Zend_Session. At this point, you an either use a component that + consumes Zend_Session, or start storing your own data inside a + session with Zend_Session_Namespace. - Zend_Session_Namespace is a simple class that proxies data via an easy to use - API into the Zend_Session managed $_SESSION superglobal. The reason - it is called Zend_Session_Namespace is that it effectively namespaces the data inside - $_SESSION, thus allowing multiple components and objects to safely store and retrieve - data. In the following code, we'll explore how to build a simple session incrementing - counter, starting at 1000 and resetting itself after 1999. + Zend_Session_Namespace is a simple class that proxies data via an + easy to use API into the Zend_Session managed + $_SESSION superglobal. The reason it is called + Zend_Session_Namespace is that it effectively namespaces the data + inside $_SESSION, thus allowing multiple components and objects to safely store and + retrieve data. In the following code, we'll explore how to build a simple session + incrementing counter, starting at 1000 and resetting itself after 1999. counter > 1999) { Additionally, if you wanted to use the DbTable - save handler for Zend_Session, you'd add the following code to your application.ini: + save handler for Zend_Session, you'd add the following code to + your application.ini: Zend_View. To get started with the pagination control, create + a new view script somewhere in your view scripts path. You can name it anything you want, + but we'll call it "controls.phtml" in this text. The reference manual contains various + examples of what might go in the view script. Here is one example. - The next step is to tell Zend_Paginator which view partial can be used to render - the navigation controls. Put the following line in your application's bootstrap file. + The next step is to tell Zend_Paginator which view partial can be + used to render the navigation controls. Put the following line in your application's + bootstrap file. paginator as $item) { Now navigate to your project's index and see Paginator in action. What we have discussed in this tutorial is just the tip of the iceberg. The reference manual and API documentation can tell you more about what you can do with - Zend_Paginator. + Zend_Paginator. - diff --git a/documentation/manual/en/tutorials/quickstart-create-layout.xml b/documentation/manual/en/tutorials/quickstart-create-layout.xml index 9c53f9321..1cb70e59f 100644 --- a/documentation/manual/en/tutorials/quickstart-create-layout.xml +++ b/documentation/manual/en/tutorials/quickstart-create-layout.xml @@ -41,8 +41,8 @@ - To get started using Zend_Layout, first we need to inform our bootstrap to use the - Layout resource. This can be done using the + To get started using Zend_Layout, first we need to inform our + bootstrap to use the Layout resource. This can be done using the zf enable layout command: -- 2.11.4.GIT