Zendcasts Forum

First, break down what your end user's will end up doing into steps. If you're using the MVC components of Zend, then you'll want to create controller actions for the intermediate steps, each of which accepts data and returns the appropriate information for the next step via AJAX.

With the case you provided, the initial step is selecting a city. Once the city is selected, your front end needs to make a request to a controller action that looks up and returns the addresses associated with the city to the front end. With that information, your front end can build the control needed for the next step.

If you give more information on what you're using, such as client side libraries (jQuery, etc.) I can provide a more concrete example.

Cool.. It all works. I inserted at my newone controller request to db for selected values and inserted them and it all works. If someone wants i can post my code. Thanks for help .

P.S. i don't know if my solution is the best (in terms of speed). But i don't know how make it better.

Last edited by nikz2 (2009-12-17 16:21:48)

[code=php]
public function newoneAction()
    {
        $this->PreAccess();
        $edos_civiles = $this->dbservice->getEdos_Civiles();
        $colonias = $this->dbservice->getColonias();
        $municipios = $this->dbservice->getMunicipiosByColony($this->_getParam('colonia_id'));
        $cp = $this->dbservice->getCodigos_PostalesByMunicipio($this->_getParam('municipio_id'));
        if ($cp!=null) $cp=$cp->toArray();
        if ($municipios!=null) $municipios=$municipios->toArray();
        //$codigos_postales->toArray(),$municipios->toArray()
        $this->view->form1 = new App_forms_newoneForm($edos_civiles->toArray(),$colonias->toArray(),$municipios,$cp);
        $this->doPostBackInsert();
        ....
}

    private function doPostBackInsert()
    {
        if ($this->getRequest()->isPost())
            {
                $paramArray = array();
                $paramArray = $this->getRequest()->getParams();
                unset($paramArray['controller']);
                unset($paramArray['module']);
                unset($paramArray['action']);
               
                //var_dump($paramArray);
                 if ($this->view->form1->isValid($paramArray))
                 {
                     unset($paramArray['Guardar']);
                     $this->view->message = $this->dbservice->insertData($paramArray,'Default_Model_AdolescenteTable');
                    
                 }
                 else
                 {
                     $this->view->message = 'Hubo un error. Datos no fueron registrados.';
                     $this->view->errorElements = $this->view->form1->getMessages();
                     //var_dump($this->view->errorElements);
                 }
            }
    }

[/code]
well.. I would be gratefull to hear any comment. What could i modify, do better, why, etc.

P.S. as you can see i'm new to zend and php and to web programming. That's why i supose i could do better a lot of things .

Last edited by nikz2 (2009-12-17 18:32:48)

I'll echo Manuel's comments on the naming conventions. Take a look at http://framework.zend.com/manual/en/cod … tions.html It's not the biggest deal in the world, but it will make your code more readable to others.

I also second using getValues() via the form object. Together, isValid() and getValues() serve as a "black box" for your controller to pass an array of input data through. Upon calling getValues(), your form will have applied any required manipulations (filters, etc.) and will have removed any indexes that the form does not contain an element for. This means that you would not need to call "unset()" on the request parameters which are irrelevant to your form.

Ex:

[code=php]
...
// Assume $requestParams contains data in "controller", "action", "module", "a", "b", "c", "d" and "e"
$requestParams = $this->getRequest()->getParams();

// assume your form has elements named "a", "b", and "c"
if ($form->isValid($requestParams)) {

    // $validatedFormData will only contain indexes for "a", "b" and "c". If there were any filtering objects attached to any elements, they will have manipulated the data as per their rules
    $validatedFormData = $form->getValues();
}
...
[/code]

I also personally like to keep all controller action logic encapsulated under one method in the controller, rather than spreading it out across multiple methods. It makes for "bigger" methods, but I find it's more organized and emphasizes the simplicity of MVC...which reminds me to look at ways of cutting down on controller responsibility when it starts to get too big. That's just me though.

Try to make all variable names self descriptive and meaningful. Example: instead of naming your form "form1", name it something like "newUserForm", "userLoginForm" or something that signifies what its responsibility is.

Last edited by ryan.horn (2009-12-18 23:45:27)