It is matter of personal taste, off course. With FormWizardComponent
all multi-page-form-requests are calling only one public method of
controller.
Also 'ways' in FormWizard are quite usable - for example:
// ways used in InstallerController
array(
'install' => array('
_installStart',
'_checkFSPermissions',
'_checkOrSetDbConfig',
'_checkOrMakeDbStructure',
'_installApp',
'_recap'
),
'upgrade' => array(
'_upgradeStart'
'_fetchUpgradePackage',
'_upgradeApp',
'_recap'
)
)
All of above functionality is handled by _only_ public method:
InstallerController::admin_index().
-- if app is not installed yet, controller switches way to 'install'
-- if app is installed and not current, controller uses way 'upgrade'
-- if app is installed and current, method admin_index() just renders
informational view
Sure, with FormWizard every 'step' requires implement one view and 2
methods, but you don't have to care about session at all, you can use
different models in different steps of your wizard (and obtain
collected data any time you need them), you can easily switch 'ways',
clear steps (reset wizard)... ;)
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Cake
PHP" group.
To post to this group, send email to cake-php@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/cake-php?hl=en
-~----------~----~----~----~------~----~------~--~---
