It's that point in Mango where I need to start the really nasty bits: checkout. Since everyone wants something different, it seems that basing things on Class::Workflow at least makes this possible. Handel touched on checkout by not implementing one at all and instead just allowing a set of plugins to molest an order record one plugin at a time in an combination of groups of plugins.
The problem of course, is that C::W makes my brain melt when I try to layer it on top of my old school views of checkout.
I've started to look at http://is.tm.tue.nl/research/patterns/ which helps, but since there are far smarter people in here than I, now's the time for input.
If you were in my shoes, what approach would you take? I'm envisioning some form of Class::Workflow (yaml from config) that defines each step in terms of what Cat Controller/actions and what plugins each action runs. That seems a bit too tied into Cat itself, and doesn't address the overall problem of what to display for each step (preview? shipping options? payment page, etc) if you seperate the workflow from the presentation.
Anyone done heavy lifting of Class::Workflow inside of a Catalyst app before?
-=Chris
signature.asc
Description: OpenPGP digital signature
_______________________________________________ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/
