Rust Studio/Built with Rust
Built with Rust
A data grid, charts, a Kanban board, a scheduler and a Markdown editor, all Rust, all included as samples.
UI component suites sell grids, charts, boards, schedulers and editors. Here is each of those as a small Ruststudio sample, built entirely with Rust: the data and the rules are Rust, the page is plain HTML and JavaScript that Rust serves, and there is nothing to install but Rust. Create one from New Project > Samples and showcase, press F5 and open the address it prints.
The applications
| Application | Like the component | What Rust does |
|---|---|---|
| Data grid | a data grid with sorting, filtering and paging | holds 100,000 rows; every sort, search and page change is a Rust function call. On a laptop, with a release build, sorting and paging all 100,000 rows took about 54 milliseconds |
| Charts dashboard | a chart suite | works out totals, shares and growth; the page draws bar, line and donut charts as SVG with tooltips, with no chart library |
| Kanban board | a board with cards | keeps the cards and enforces the rules (title length, known columns); two windows stay in step |
| Scheduler | a calendar and scheduler | checks every date (leap years included) and time, lists a month in order |
| Markdown editor | a rich text or Markdown editor | renders the preview, counts words, and turns raw HTML into text so a pasted <script> can never run |
| To-do list API | a first REST service | shared state, JSON in and out, status codes, and tests that call the API without a server |
| Word count | a first command-line tool | files, standard input, options, with tests and no dependencies |
Why these are good first looks at Rust
- They are small. Each application is one
main.rsof about 100 to 250 lines plus a page, so you can read it in one sitting. - They are tested. Every sample has unit tests next to the code (
cargo test), including the rules that matter: dates, limits, escaping. The Markdown editor has a test that a<script>in the text comes out as text. - They are honest about what Rust does. The data grid shows the time Rust took on every request. The page "Why choose Rust" has the measurements and says where Rust is not the fastest.
- They are starting points. Each README ends with things to try: add a column, a fourth product, a new board column, an end time for events.
Using the same ideas in your own project
- Put the rules in plain functions and methods, and keep the HTTP code thin: that is what makes them easy to test.
- Use the packages from the Rupm view for the usual chores:
json-toolsfor JSON,config-toolsfor settings,http-toolsfor calling other services,log-toolsfor logging. - Use the Debug panel's Immediate window to look inside a running handler.
Keep exploring
Why choose Rust
Rust compared with Go, C#, Java, Node and Python on speed, memory, size and the bugs each language lets through, with…
Ruststudio user guide
How to use every part of Ruststudio: projects, the editor, find and replace, debugging with threads and the Immediate…
Download Rust Studio
Download Rust Studio, the free Rust IDE by FOWLGUARD for Windows 10 and 11, macOS and Linux. Per-user install, no adm…