You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When updating a progress or pulse bar it would be very convenient if it was possible to still use blocking PHP.
Specifically, it is quite easy to imagine a developer wanting to display zenity progress on a large set of SQL queries, updating the progress bar as he goes through every step. Currently this is only possible by manually ticking the loop. It would be nice if there could be some kind of support for this.
The text was updated successfully, but these errors were encountered:
I agree that this would be convenient, but I'm unsure if this is actually feasible..
The current waitFor() method is out of place with the rest of this library, so perhaps it's best to remove this in a future version? Instead, I would suggest we give at least two examples that build on top of https://github.com/clue/php-block-react:
wait for a zenity to quit
start zenity, do blocking work, update zenity, do blocking work, close zenity
Yeah, those seem much more in place. I think a clear distinction between those two strategies would also make the library much less confusing for new users to try out.
And of course it would be convenient for the kind of work I do as well.
When updating a progress or pulse bar it would be very convenient if it was possible to still use blocking PHP.
Specifically, it is quite easy to imagine a developer wanting to display zenity progress on a large set of SQL queries, updating the progress bar as he goes through every step. Currently this is only possible by manually ticking the loop. It would be nice if there could be some kind of support for this.
The text was updated successfully, but these errors were encountered: