day-process 0.7.7

What a Day process has without a user interface: identity, directories, startup services and the FFI panic guard
Documentation
  • Coverage
  • 66.67%
    22 out of 33 items documented0 out of 16 items with examples
  • Size
  • Source code size: 30.5 kB This is the summed size of all the files inside the crates.io package for this release.
  • Documentation size: 271.1 kB This is the summed size of all files generated by rustdoc for all configured targets
  • Ø build duration
  • this release: 5s Average build duration of successful builds.
  • all releases: 4s Average build duration of successful builds in releases after 2024-10-23.
  • Links
  • daybrite/day
    28 4 1
  • crates.io
  • Dependencies
  • Versions
  • Owners
  • marcprux

day-process

What a Day process has before, and without, a user interface.

Day is a Rust framework for building apps with native desktop and mobile controls, plus HTML controls on the web.

[!NOTE] Usually an indirect dependency. App code reaches these through day. A part that runs without a window, such as a background worker or a push handler, depends on this crate directly.

It supplies the app's id and its data, cache and configuration directories; the registry of services that start with the process; native notification delivery; and the guard that keeps a Rust panic from unwinding into foreign code. It depends on no toolkit, widget or reactive code.

Documentation

Source · Contributing · MPL-2.0