Re-work UI to expose underlying operations #485
Loading…
x
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
abra
is gaining more UI magical powers and@forest
has given a spark of inspiration and some direction in this thread.Today we just dump everything to
--debug
and theabra
output just hangs waiting for stuff to work or fail. That is because we haven't really had a "UI layer" to deal with this stuff.That's changing in #484 and I can see that it would allow you to, in one place in the code "start the UI" then "run the logic" and have "the logic" send back updates to "the UI" to update a list of operations, with indicators of progress and such (e.g. "starting this, running this, finished this").
I wouldn't start such a refactor without more feedback. I won't pick this up now but I think it would be a really great improvement. Leaving this for "another day".
Related: toolshed/organising#657
Re-work UI of underlying operations of `abra`to Re-work UI to expose underlying operationsAmazing idea, think this would the waiting a lot more bearable.
And it might lead to useful bug reports about exactly which steps are timing out for different recipes?