CommandDotNet
Gui.cs
CommandDotNet | Gui.cs | |
---|---|---|
3 | 59 | |
550 | 9,107 | |
- | 0.6% | |
5.9 | 9.2 | |
4 months ago | 7 days ago | |
C# | C# | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
CommandDotNet
-
Simple Command line Project Helper (Would love feedback)
Have you seen https://github.com/bilal-fazlani/commanddotnet? Disclaimer: I'm one of the maintainers What you've thrown together does seem similar to CliFx in some respects, as you mentioned in another thread. It looks like a command must be defined as a class. I once created a framework that followed that approach and ultimately found it limiting. I've found it to be more expressive to use methods to define commands, although both are possible with CommandDotNet. For example, we can use the position of parameters in the methods to define the position in the command. Defining operands (positional parameters) via properties, we automatically position them based on position in the file, which was interesting because .net does not guarantee order of properties when reflecting them. We were able to use CallerLineNumber to get this. You might look into that. To answer the question of `Is the use of the project simple and have any benefit over using other parsers?` I'd say that CommandDotNet, CliFx, Spectre and even MS's System.CommandLine have a head start on tackling some of the more complex features and already have some community around them. It think this project has a bit of catchup to do. For example, you can see the CommandDotNet features at https://commanddotnet.bilal-fazlani.com/features/ A lot of the design went into making it a simple as possible to define a command using c# conventions, like parameter positions, NRT, optional parameters, etc. Fore example, we use nullability to determine if an argument is required, although it's also possible to use DataAnnotations or FluentValidations to perform more complex validations. That all takes a bit of time to support. I'd say if you're looking to experiment and play around, keep at it. It's unlikely you're going to get a lot traction in the space though, especially since MS has their own framework. If you want to contribute code that's more likely to be used and seen by others, look at System.CommandLine or one of the other main tools. If you continue with this one, feel free to use CommandDotNet for reference if you'd like hit me up for questions on the discussions, or feel free to bring ideas to CommandDotNet and contribute.
-
How to generate a CLI interface for CRUD operations?
Someone asked a similar question about a https://github.com/bilal-fazlani/commanddotnet/, which is a tool I help maintain.
-
Spectre.Console is a .NET Standard 2.0 library that makes it easier to create beautiful console applications.
Have you seen CommandDotNet by chance? It has an integration with Spectre.Console. It provides some powerful test tools and what I think is a simpler and more flexible way to define commands.You can check out the features page to see what's available.
Gui.cs
- Forget MAUI; Get TUI! - C#'s best cross platform console UI toolkit ships first 2.0 alpha package (Terminal.Gui)
-
Hello everyone, I made a Windows 10/11 Multitool app with Winforms. I'm just gonna share some screenshots.
Thanks but I'm sticking with Terminal.Gui
-
Made a simple text based little game to re-learn c#
Used this neat library to handle the GUI gui-cs/Terminal.Gui: Cross Platform Terminal UI toolkit for .NET (github.com)
-
What your hidden nuget gems ?
Terminal.GUI - cross platform terminal UI for .NET: https://github.com/gui-cs/Terminal.Gui
-
Textual (TUI framework) widget gallery
Two I've used are Terminal.Gui for .net https://github.com/gui-cs/Terminal.Gui and BubbleTea for Go https://github.com/charmbracelet/bubbletea
-
UI framework for games on Linux with c#
In that case you can use console (https://github.com/gui-cs/Terminal.Gui) to make games.
-
Managing Powershell collections graphically
As you can see the tool is always integrated into the terminal because it has built on a cross platform UI toolkit based on a fantastic open source project called Terminal.Gui. Now you can select the objects by using space bar and than confirm the selection with enter. The result will be:
-
What python/C# GUI library would be best for my project?
C# - https://github.com/gui-cs/Terminal.Gui
-
c# native with a gui
Since you mentioned minimal GUI, have you thought of a TUI? I haven't spiked it out but I would guess Terminal.Gui would work with Native AOT
-
GTK support for macOS is being worked on for those who want to create applications for macOS.
I've had to resort to make TUIs with https://github.com/gui-cs/Terminal.Gui because there's no sane way to make a GUI app in Linux without a 300-files boilerplate or obscure languages.
What are some alternatives?
Sharprompt - Interactive command-line based application framework for C#
spectre.console - A .NET library that makes it easier to create beautiful console applications.
CliFx - Class-first framework for building command-line interfaces
Command Line Parser - The best C# command line parser that brings standardized *nix getopt style, for .NET. Includes F# support
CsConsoleFormat - .NET C# library for advanced formatting of console output [Apache]
Sieve - ⚗️ Clean & extensible Sorting, Filtering, and Pagination for ASP.NET Core
Power Args - The ultimate .NET Standard command line argument parser
Fluent Command Line Parser - A simple, strongly typed .NET C# command line parser library using a fluent easy to use interface
CommandLineUtils - Command line parsing and utilities for .NET
Console Framework - Cross-platform toolkit for easy development of TUI applications.
Docopt - Port of docopt to .net