In my django programming, very often I find myself writing a view that has "stages", that is, the view manages several distinct situations that are identified by checking if a given dictionary key is present or not (that is, if a given button was pressed or was another one).
The list of buttons that can be pressed is dinamically generated in the previous stage, in what I call a list of candidate 'next' stages. I imagine mayself a special callable, a custom class f.i., that holds the abstract structure of the whole dinamic management of buttons to show, and stages to manage. The class would avoid some repeating code, namely, the names of the buttons, and the tree (or graph) of stages, uo to the final processing of the data. This also involves some form tweaking, such as deleting form keys for a stage that doesn't need these keys, etc. I'm sure this has been invented before, but I don't know how or by whom, or how to call it in a way that is recognizable to seasoned django developers. I'll continue coding like that until I realize how to do better, I'm eager of someone telling me how to do better, or understand better the area of problem I'm dealing with. haroldo --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
