JQuery Helpers AjaxLink Helper The AjaxLink helper uses jQuery's ajax capabilities to offer the creation of links that do ajax requests and inject the response into a chosen DOM element. It also offers the possibility to append simple jQuery effects to both the link and the response DOM element. A simple example introduces its functionality:
view->ajaxLink("Link Name", "url.php", array('update' => '#container')); ?> ]]> This example creates a link with the label "Link Name" that fires an ajax request to url.php upon click and renders the response into the div container "#container". The function header for the ajaxLink is as follows: function ajaxLink($label, $url, $options, $params); The options array is very powerful and offers you lots of functionality to customize your ajax requests. Available options are: AjaxLink options Option Data Type Default Value Description update string false Container to inject response content into, use jQuery CSS Selector syntax, ie. "#container" or ".box" method string Implicit GET or POST Request method, is implicitly chosen as GET when no parameters given and POST when parameters given. complete string false Javascript callback executed, when ajax request is complete. This option allows for shortcut effects, see next section. beforeSend string false Javascript callback executed right before ajax request is started. This option allows for shortcut effects, see next section. noscript boolean true If true the link generated will contain a href attribute to the given link for non-javascript enabled browsers. If false href will resolve to "#". dataType string html What type of data is the Ajax Response of? Possible are Html, Text, Json. Processing Json responses has to be done with custom "complete" callback functions. attribs array null Additional HTML attributes the ajaxable link should have. title, id, class string false Convenience shortcuts for HTML Attributes. inline boolean false Although far from best practice, you can set javascript for this link inline in "onclick" attribute.
To enlighten the usage of this helper it is best to show another bunch of more complex examples. This example assumes that you have only one view object that you want to display and don't care a lot about html best practices, since we have to output the jQuery environment just before the closing body tag. Zend Framework jQuery AjaxLink Example
  • ajaxLink("Example 1", "/ctrl/action1", array('update' => '#content', 'noscript' => false, 'method' => 'POST')); ?>
  • ajaxLink("Example 2", "/ctrl/action2", array('update' => '#content', 'class' => 'someLink'), array('param1' => 'value1', 'param2' => 'value2')); ?>
  • ajaxLink("Example 3", "/ctrl/action3", array('dataType' => 'json', 'complete' => 'alert(data)')); ?>
  • ajaxLink("Example 4", "/ctrl/action4", array('beforeSend' => 'hide', 'complete' => 'show')); ?>
  • ajaxLink("Example 5", "/ctrl/action5", array( 'beforeSend' => 'myBeforeSendCallbackJsFunc();', 'complete' => 'myCompleteCallbackJsFunc(data);') ); ?>
jQuery(); ?> ]]> You might have already seen that the 'update', 'complete', and 'beforeSend' options have to be executed in specific order and syntax so that you cannot use those callbacks and override their behaviour completely when you are using ajaxLink(). For larger use cases you will probably want to write the request via jQuery on your own. The primary use case for the callbacks is effect usage, other uses may very well become hard to maintain. As shown in Example Link 5, you can also forward the beforeSend/complete Callbacks to your own javascript functions. Shortcut Effects You can use shortcut effect names to make your links actions more fancy. For example the Container that will contain the ajax response may very well be invisible in the first place. Additionally you can use shortcut effects on the link to hide it after clicking. The following effects can be used for callbacks: complete callback: 'show', 'showslow', 'shownormal', 'showfast', 'fadein', 'fadeinslow', 'fadeinfast', 'slidedown', 'slidedownslow', 'slidedownfast'. These all correspond to the jQuery effects fadeIn(), show() and slideDown() and will be executed on the container specified in update. beforeSend callback: 'fadeout', 'fadeoutslow', 'fadeoutfast', 'hide', 'hideslow', 'hidefast', 'slideup'. These correspond to the jQuery effects fadeOut(), hide(), slideUp() and are executed on the clicked link. ajaxLink("Example 6", "/ctrl/action6", array('beforeSend' => 'hide', 'complete' => 'show')); ?> ]]> jQuery UI Library Helpers The jQuery UI Library offers a range of layout and form specific widgets that are integrated into the Zend Framework via View Helpers. The form-elements are easy to handle and will be described first, whereas the layout specific widgets are a bit more complex to use. jQuery UI Form Helpers The method signature for all form view helpers closely resembles the Dojo View helpers signature, helper($id, $value, $params, $attribs). A description of the parameters follows: $id: Will act as the identifier name for the helper element inside a form. If in the attributes no id element is given, this will also become the form element id, that has to be unique across the DOM. $value: Default value of the element. $params: Widget specific parameters that customize the look and feel of the widget. These options are unique to each widget and described in the jQuery UI documentation. The data is casted to JSON, so make sure to use the Zend_Json_Expr class to mark executable javascript as safe. $attribs: HTML Attributes of the Form Helper The following UI widgets are available as form view helpers. Make sure you use the correct version of jQuery UI library to be able to use them. The Google CDN always offers you the latest released version. autoComplete($id, $value, $params, $attribs): The AutoComplete View helper is part of jQuery UI since version 1.8 and creates a text field and registeres it to have auto complete functionality. The completion data source has to be given as jQuery related parameters 'url' or 'data' as described in the jQuery UI manual. colorPicker($id, $value, $params, $attribs): ColorPicker is still a ZendX_JQuery element for legacy reason, but was removed from jQuery UI completly. datePicker($id, $value, $params, $attribs): Create a DatePicker inside a text field. This widget is available since jQuery UI 1.5 and can therefore currently be used with the Google CDN. Using the 'handles' option to create multiple handles overwrites the default set value and the jQuery parameter 'startValue' internally inside the view helper. slider($id, $value, $params, $attribs): Create a Sliding element that updates its value into a hidden form field. Available since jQuery UI 1.5. spinner($id, $value, $params, $attribs): Create a Spinner element that can spin through numeric values in a specified range. This element was removed from the 1.6 jQuery UI release and has not been re-released yet. Showing jQuery Form View Helper Usage In this example we want to simulate a fictional web application that offers auctions on travel locations. A user may specify a city to travel, a start and end date, and a maximum amount of money he is willing to pay. Therefore we need an autoComplete field for all the currently known travel locations, a date picker for start and end dates and a spinner to specify the amount. autoComplete("location", "", array('source' => array('New York', 'Mexico City', 'Sydney', 'Ruegen', 'Baden Baden'))); ?>
datePicker("startDate", '', array( 'defaultDate' => '+7', 'minDate' => '+7', 'onClose' => new Zend_Json_Expr('myJsonFuncCechkingValidity'))); ?>
datePicker("endDate", '', array( 'defaultDate' => '+14', 'minDate' => '+7', 'onClose' => new Zend_Json_Expr('myJsonFuncCechkingValidity'))); ?>
spinner("bid", "", array('min' => 1205.50, 'max' => 10000, 'start' => 1205.50, 'currency' => '€')); ?>
]]> You can see the use of jQuery UI Widget specific parameters. These all correspond to those given in the jQuery UI docs and are converted to JSON and handed through to the view script. Using an Action Helper to Send Data to AutoComplete The jQuery UI Autocomplete Widget can load data from a remote location rather than from an javascript array, making its usage really useful. Zend Framework currently providers a bunch of server-side AutoComplete Helpers and there is one for jQuery too. You register the helper to the controller helper broker and it takes care of disabling layouts and renders an array of data correctly to be read by the AutoComplete field. To use the Action Helper you have to put this rather long statement into your bootstrap or Controller initialization function: You can then directly call the helper to render AutoComplete Output in your Controller _helper->autoComplete(array("New York", "Bonn", "Tokio")); } } ]]> jQuery UI Layout Helpers There is a wide range of Layout helpers that the UI library offers. The ones covered by Zend Framework view helpers are Accordion, Dialog, Tabs. Dialog is the most simple one, whereas Accordion and Tab extend a common abstract class and offer a secondary view helper for pane generation. The following view helpers exist in the jQuery view helpers collection, an example accompanies them to show their usage. dialogContainer($id, $content, $params, $attribs): Create a Dialog Box that is rendered with the given content.on startup. If the option 'autoOpen' set to false is specified the box will not be displayed on load but can be shown with the additional dialog("open") javascript function. See UI docs for details. tabPane($id, $content, $options): Add a new pane to a tab container with the given $id. The given $content is shown in this tab pane. To set the title use $options['title']. If $options['contentUrl'] is set, the content of the tab is requested via ajax on tab activation. tabContainer($id, $params, $attribs): Render a tab container with all the currently registered panes. This view helper also offers to add panes with the following syntax: $this->tabContainer()->addPane($id, $label, $content, $options). accordionPane($id, $content, $options): Add a new pane to the accordion container with the given $id. The given $content is shown in this tab pane. To set the title use $options['title']. accordionContainer($id, $params, $attribs): Render an accordion container with all the currently registered panes. This view helper also offers to add panes with the following syntax: $this->accordionContainer()->addPane($id, $label, $content, $options). Showing the latest news in a Tab Container For this example we assume the developer already wrote the controller and model side of the script and assigned an array of news items to the view script. This array contains at most 5 news elements, so we don't have to care about the tab container getting to many tabs. news AS $article): ?> tabPane("newstab", $article->body, array('title' => $article->title)); ?>

Latest News

tabContainer("newstab", array(), array('class' => 'flora')); ?> ]]>