Hi Trytonistas,
the grasbauer-crew is still allive and well. We only have a shortened
timeline with our current project, because the ISO-certification of the
company we are working for is coming soon - we as a two-person-company
are totally blocked with the daily changes in the current project. We
still stuck in Tryton 2.0, because we don't have the capacities to
translate all our stuff to 2.2 or later while we are still in production
with our tryton 2.0 extensions. So I don't know a lot about the
improvements allready done in the trunk, but I have a doubt about a
requirement of the workflow-engine:
if a workflow changes to a next state, the states (required, invisible)
of some fields are changing depending of the state, defined in
pyson-domains. It would be helpful, if the workflow engine is checking
this further states on writing and setting the fields to required on the
fly. We have implemented some workaround in the write-method of the
models, but I think there should be a pre-evaluation of the required
fields in the next state of the workflow.
Don't know if I miss something - but this was a issue in the last weeks
we solved with ugly workarounds.
Still looking forward to have more time left for
contributing/reviewing/discussing stuff in the tryton-community
Jan
+++ tryton rocks +++
--
[email protected] mailing list
