I'm not sure we're quite on the same page: I'm not looking to inspect
the state, but more be notified when certain edges are traversed.
That said: what's the best practice when you want to visualize the
current state of a machine? In this case, the machine is for a unit of
work in a scheduling app, and the UI has a list of these units where
it'd make sense to show the current state.
The unit of work also forms the boundary API between the from end object
model and the pool/scheduling back end. As such, each side can naturally
call inputs methods on the machine, as I believe automat intends, but
it's how to get notified by an output?
So, the front end may want to say "I no longer need this UoW done,
please kill it", the back end then needs to run the code to kill
whatever's running the UoW.
Likewise, when the backend finishes a UoW, it wants to call either
machine.result(...) or machine.error(...) to say what happened, but how
do I wire in the front end bit that needs to get called when this happens?
cheers,
Chris
On 07/03/2021 22:34, Glyph wrote:
Automat is designed to make this sort of thing intentionally annoying,
as you have discovered:).
The idea is that if you want to know this sort of internal state, it’s
for a specific reason. That's not a blanket "No" — see for example how
automat deals with serialization — but each such interface should be
minimal and thoughtfully designed. Otherwise a state machine library
just becomes a bunch of complex infrastructure around making an
arbitrary series of function calls, and loses all of its helpful
formalisms.
So probably we do need to make a change to automat if you really need
to do this, but first it's important to know what your use-case is. In
a lot of cases the answer is "just make an output. Stop trying to make
the application see into the guts of the framework." But without
knowing it’s impossible to say!
-g
Hi,
Apologies if there's a better list for this, please let me know where...
I've grown to like Glyph's automat package a lot, but in a current
project, I have observers that need to know when a machine changes state.
What's the best way to let those observers know?
cheers,
Chris
_______________________________________________
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
https://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python
_______________________________________________
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
https://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python
_______________________________________________
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
https://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python
