Hi Everyone,
We've been asked to demo Cake to our organisation, by quickly
developing a simple application.
Essentially what this application does is allow employees to register
themselves on via a 4 step web-based form, and then add themselves to a
group made up of already registered employees for training. Once
they've completed sign up then they can perform basic functions like
move themselves in and out of various groups, and can keep doing it up
until the point that that an administrator 'approves' the group that
they are in, at which point they are locked down.
For admins, there is an admin interface that allows them to directly
CRUD the records of employees and groups, as well as having access to
all the typical 'remove member from group', 'add this memeber to a
group' stuff, as well as approving (locking down) the group.
So, basically two different interfaces to do exactly the same thing -
one is a very controlled process for employees, and the other is a very
high-level process for administrators. But although one is tightly
controlled and one is not, they are both performing simillar actions
('add to group') etc, and sharing a lot of presentation logic (eg.
group overview) too.
What would be the best way to go about structuring an application like
this? How do you structure a multi-page form into a controller (one
action per page perhaps)? How can we avoid re-writing common functions
like add-to-group, or preserving common interface elements (like the
group overview page) between the registration and the admin interface?
Any help appreciated! Thanks, A
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Cake
PHP" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/cake-php
-~----------~----~----~----~------~----~------~--~---
