Hello forums!!
I would like to know which design pattern would be useful in the following case:
There are many modules and each module consists of many actions(multi stage actions). for example:
Module A consists of action1.1, action1.2, action1.3 etc.
Module B consists of action2.1, action2.2, action2.3 etc.
The actions can be sequential(For example:action1.1-> action1.2-> action1.3) or can be altered as per preferences( For example:action1.1-> action1.3-> action1.2) within a module.
How this can be accomplished using OOP design pattern or else? Any ideas ??
Thanks in advance for the valueable help.
design pattern for this case ??
Moderator: General Moderators
Re: design pattern for this case ??
knock knock !! any example please?
Re: design pattern for this case ??
- Are modules classes and actions methods?
-- yes
- Do they need additional Parameters?
-- may or may not
- Are there requirements to the module configuration?
-- Class runs the methods as sequence of methods(like i stated: action1.1-> action1.2-> action1.3) in a default but it can be configureable also
Hope this may help.
-- yes
- Do they need additional Parameters?
-- may or may not
- Are there requirements to the module configuration?
-- Class runs the methods as sequence of methods(like i stated: action1.1-> action1.2-> action1.3) in a default but it can be configureable also
Hope this may help.
- Christopher
- Site Administrator
- Posts: 13596
- Joined: Wed Aug 25, 2004 7:54 pm
- Location: New York, NY, US
Re: design pattern for this case ??
The words Modules and Actions already have meanings as the relate to dispatched controllers. What do the things you are talking about actually do? What are they?
(#10850)