summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAge
* Fix broken link in `backends` documentationStephan Sokolow2019-10-25
| | | | (Revealed by cargo-deadlinks)
* Add a backend based on KDE's `kdialog`Stephan Sokolow2019-10-25
|
* Release v0.2.1v0.2.1Robin Krahl2019-06-30
|
* Fix input and password dialogs for zenity backendRobin Krahl2019-06-30
| | | | | | | | Previously, we tried to read the user input from zenity’s stderr although it is written to stdout. This patch changes the zenity backend to read from stdout instead of stderr. It also removes trailing newlines from the user input, as zenity adds a newline when writing the input.
* Fix links in crate documentationRobin Krahl2019-01-11
|
* Release v0.2.0v0.2.0Robin Krahl2019-01-11
|
* Add usage example to readmeRobin Krahl2019-01-11
|
* Add the stdio backendRobin Krahl2019-01-11
| | | | | | | This patch adds the stdio backend which acts as a fallback backend and uses standard input and output. For password queries, the rpassword crate is used to suppress output. Also, default_backend is changed to return Stdio if Dialog is not available.
* Check DISPLAY environment variable in default_backendRobin Krahl2019-01-11
| | | | | | | This patch changes the default_backend to also check the DISPLAY environment variable. If it is set, there probably is a X server running, so we try to use the zenity backend. Otherwise, the dialog backend is used.
* Check the DIALOG environment variable in default_backendRobin Krahl2019-01-11
| | | | | This patch changes the logic in default_backend to respect the DIALOG environment variable that may contain the name of the backend to use.
* Return Box<dyn Backend> in default_backend()Robin Krahl2019-01-11
| | | | | | | | | | This patch refactors the default_backend function to return a Box<dyn Backend> instead of impl Backend. This will allow us to dynamically choose the backend implementation in a future patch. To keep the current interface, we change show_with to accept both a reference to a backend instance as well as a reference to a boxed backend instance. This also means we have to implement AsRef<Self> for the backend structs.
* Document the Zenity backend in the crate commentRobin Krahl2019-01-11
|
* Release v0.1.1v0.1.1Robin Krahl2019-01-11
|
* Fix link in readmeRobin Krahl2019-01-11
|
* Implement Display for the Error enumRobin Krahl2019-01-11
|
* Move Error enum to the error moduleRobin Krahl2019-01-11
| | | | | | | | | The trait implementations for the Error enum contain a lot of boilerplate code and are not very insightful. Therefore this patch moves the Error enum, its trait implementations and the related Result type definition from the main module to the error module. The Error and Result types are re-exported from the main module so that the public interface does not change.
* Implement zenity backendRobin Krahl2019-01-08
|
* Add the Password dialog boxRobin Krahl2019-01-08
|
* Release v0.1.0v0.1.0Robin Krahl2019-01-08
|
* Refactor io::Error into custom Error enumRobin Krahl2019-01-08
|
* Add question dialog boxesRobin Krahl2019-01-08
|
* Add input dialog boxesRobin Krahl2019-01-08
| | | | | | This patch implements input dialog boxes. This required some refactoring in the dialog backend to allow additional arguments after the width and the height.
* Move tests/ to examples/Robin Krahl2019-01-08
| | | | | | | So far it is hard to write unit tests for this crate as we don’t have much logic. The existing tests are usage examples, therefore they are moved to the examples directory. They can be run with `cargo run --example <name>`.
* backends/Dialog: Add support for output handlingRobin Krahl2019-01-08
| | | | | | | | dialog(1) uses stdin to display the dialog boxes and prints output to stderr (if applicable). This patch changes the command invocation in the Dialog backend to capture stderr. stdin and stdout are inherited from the main process so that dialog can display the dialog boxes and receive user input.
* Implement message boxes using the dialog backendRobin Krahl2019-01-08
| | | | | | This patch adds a first dialog box type, message boxes, and a first backend, the dialog(1) tool. It does not yet address the problems of output handling and backend selection.
* Create project skeletonRobin Krahl2019-01-08