I'm very excited to create a few CLI utilities using this library (especially since Core 3 gives us the beginnings of single EXE deployment) but I am not sure how best to layout the code.
The bundled example is somewhat helpful to get an idea how to build the main UI, but is not as helpful when building something more sophisticated with dialogs, wizards, or background IO/tasks.
Some of this information can be found by mining the issues or PRs. Please don't think I am complaining (too much) :). I admire your work, but I want to understand how to harness it.
Are there any examples (maybe community tools built using gui.cs) which demonstrate doing something real and might be recommended for patterns/architectures/techniques?
Hi,
there is a "Used by" Button on top of this page, where you can see projects using this library.
Just have a look at the most starred projects how they use the lib:
https://github.com/migueldeicaza/gui.cs/network/dependents?package_id=UGFja2FnZS0xNTg1ODA4MzM%3D
Wow, I did not know about this "used by" feature - that is so cool!
@gitblit I would love to add more samples and documentation to address any specific questions you have.
@migueldeicaza One simple example is an application with several "screens" - eg
That's a great list. Even better to pair those screens with some async IO and not just an in-memory/singleton provider. Maybe hit the Github API and show the list of open issues or open PRs in this repo?
PowerShell core now has a Terminal.gui based cmdlet: Out-ConsoleGridView.
PS> Install-Module Microsoft.PowerShell.ConsoleGuiTools
PS> ls | out-consolegridview
The code is here: https://github.com/PowerShell/GraphicalTools here:
Oh this is delightful!
Got a screenshot to share on twitter?
Oh this is delightful!
Just wait until my PRs to make it better get accepted (after the ones I've added to Termina.gui get accepted). The key is the current version is way too hard to exit out of.
UICatalog is merged. Closing this issue. If there are scenarios you want added to UICatalog open a new issue with a title prefixed by "UI Catalog: ". Thanks.
Most helpful comment
That's a great list. Even better to pair those screens with some async IO and not just an in-memory/singleton provider. Maybe hit the Github API and show the list of open issues or open PRs in this repo?