On Fri, Jun 26, 2015 at 3:01 AM, Softeisbieger <j.kitschke@gmx.de> wrote:
> I am uncertain how to handle different work flows, though. The user should
> be able to define these 'on the fly' and I have no idea how to express this
> in terms of django. What I know about a workflow:
there's a thing known as a workflow engine, with extensive theory,
definitions, terminology, research and implementations. Check some of
theory in wikipedia[1].
as is common in Django, a very useful first stop is
djangopackages.com, where you can find a comparison grid of workflow
engines already created for Django[2]
some of them are quite capable, and even if miss something you would
like, they're not too hard to adapt, once you have the theory well
understood.
Of course, if you're new to Django, first you _have_ to do the
tutorial, or lots of things might not make sense.
[1]: https://en.wikipedia.org/wiki/Workflow_engine
[1.1]: https://en.wikipedia.org/wiki/Business_process_modeling
[1.2]: https://en.wikipedia.org/wiki/Petri_net
[1.3]: https://en.wikipedia.org/wiki/Kahn_process_networks
[2]: https://www.djangopackages.com/grids/g/workflow/
--
Javier
--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CAFkDaoRU5qqhQrdSmSfeE3KJzCxxd6icqEdahp9uQ6GnL-HSBA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment