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
What I want is a sort of flowing, nested panel mechanism; rich.live demo comes close, but I need to learn me some naming: you can't nest live displays, but that feels like what I want to do. Our Python-based asset pipeline can take under a second for a no-op incremental run, or days for a production run. Steps within steps, subprocesses, layers, and what I want to do is like rich.live / bazel / docker, but sometimes I want to collapse the output into a transient sub-panel of its own, that may eventually be deleted or replaced with a summary, and if there's another one below one that expires, it'll skootch on up.
Converting "Bingo" for "iOS": Started 3.15pm Running 03:38:27 ...spinner...
[21.05.13] warning: unreferenced texture: Anagram.tga
- Manifest: 11.5s: 113,718 root assets, 425 out of date (replaces a collapsed section)
- Properties: 2.8s (another replacement)
- Converting Textures:
- | 117: PlaceHolder.tga -> 01010249 [PNG]: 0.2s
- | 118: Zippity.bmp: ..spinner..
- | | - Validation: OK
- | | - Collect Parameters: OK
- | | - Convert: <commandline> ..spinner..
- | | | <last N lines from subprocess>
- Exporting Converted Assets:
- | 204: PlayerCheats.ini -> f0f0f0f0f0.dat
- | 205: Unicorns.shader -> deadbeef.dat
And when all the textures have been converted, that entire section collapses down to a "Done" type line, and the exporting pane might zip upwards.
Do I just do all this with tables and Live is just the renderer?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
What I want is a sort of flowing, nested panel mechanism; rich.live demo comes close, but I need to learn me some naming: you can't nest live displays, but that feels like what I want to do. Our Python-based asset pipeline can take under a second for a no-op incremental run, or days for a production run. Steps within steps, subprocesses, layers, and what I want to do is like rich.live / bazel / docker, but sometimes I want to collapse the output into a transient sub-panel of its own, that may eventually be deleted or replaced with a summary, and if there's another one below one that expires, it'll skootch on up.
And when all the textures have been converted, that entire section collapses down to a "Done" type line, and the exporting pane might zip upwards.
Do I just do all this with tables and Live is just the renderer?
Beta Was this translation helpful? Give feedback.
All reactions