rumtk-web-0.3.7
Platform
- x86_64-unknown-linux-gnu
Feature flags

docs.rs

Rust

rumtk-web 0.3.7

Web framework part of the RUMTK framework that attempts to simplify and expedite dashboard development in Healthcare.

Crate
Source
Builds
Feature flags

Coverage
4.31%
9 out of 209 items documented3 out of 54 items with examples
Size
Source code size: 306.76 kB This is the summed size of all the files inside the crates.io package for this release.
Documentation size: 5.08 MB This is the summed size of all files generated by rustdoc for all configured targets
Links
Homepage
MedicalMasses-L-L-C/rumtk
3 0 7
crates.io
Dependencies
Versions
Owners

Rumtk-Web

Rust's Universal Medical Toolkit is a toolkit being developed to put together a set of tools and libraries to facilitate communication and automation in medicine.

rumtk-web is the subframework meant to facilitate the construction of dashboards in Healthcare.

Goal

To provide a very fast and efficient web framework for building reliable dashboards.
To provide Server Side Rendering capabilities in healthcare dashboards.
To provide a simple and customizable system for putting together these dashboards.

Features

Healthcare Web Dashboard Library
- Server Side Rendering.
- High Performance Web framework (see MedicalMasses L.L.C.'s website which uses this framework).
- Simple old-school organization of web project via the Askama templating engine.
- Mechanism for component definition.
- Mechanism for rendering components that is familiar to React users while being based on pure SSR.
- Mechanism for registering user made components (can be used to override library components).
- Mechanism for statically defining web page layout in Rust.
- Mechanism for rendering pages.
- Mechanism for bundling CSS via component level and as part of a global minified bundle generated on first run.
- Usage of HTMX as a very light JS front end to extend HTML tag functionality.
- Mechanism for falling back to local copies of HTMX and FontAwesome as needed if CDNs are down.
- Features exposed via Rust macros.
- Tests
- Fuzz Targets

Contributing

In its initial stages, I will be pushing code directly to the main branch. Once basic functionality has been stablished, everyone including myself is required to open an issue for discussions, fork the project, and open a PR under your own feature or main branch. I kindly ask you include a battery of unit tests with your PR to help protect the project against regressions. Any contributions are very appreciated.