I like the idea of workflow engine or "rules" engine. Actually, Cake is a framework to design application, but having the user (or parameters) designing is own "flow" once the application is done is a step further. The danger is to become very complex and degrading performances. In my mind, it would be a super component that would manage other components and also the action "redirect" .... Actually, considering ACL as a starting point ..( a bit of "create_function" with parameters in it) you could have a component redirecting you based on system rules as well as user rules.
Well, this are just ideas (surely crazy, I know cake only for few months). I have done a workflow engine in a "previous life" with other technology and also targeted to a specific business.. The problem is the notion of "Workflow" that everyone interprets differently, according to business needs. Something to think about anyway. On Jul 20, 10:14 pm, "Chris Hartjes" <[EMAIL PROTECTED]> wrote: > On 7/20/07, Kunthar <[EMAIL PROTECTED]> wrote: > > > 2. If cake claims to be a real alternative MVC it has to own workflow > > engine internal, > > What does having it's own internal workflow engine have to do with > Cake's implementation of MVC? > > Chris Hartjes > Senior Developer > Cake Development Corporation > > My motto for 2007: "Just build it, damnit!" > > @TheBallpark -http://www.littlehart.net/attheballpark > @TheKeyboard -http://www.littlehart.net/atthekeyboard --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
