maud VS cad-plus

I would like to mention maud in this context:

https://github.com/lambda-fairy/maud

It is refreshingly different from other Rust templating libraries. It uses a proc-macro that compiles your HTML into Rust code. I also happen to use it in conjunction with HTMX and it works very well for me (at least in small projects).

You can also use HTML templating with crates like askama, tera and maud! This can be combined with the power of lightweight JavaScript libraries like htmx to speed up time to production. You can read more about this on our other article about using HTMX with Rust which you can find here.. We also collaborated with Stefan Baumgartner on an article for serving HTML with Askama!

I think a lot of us reach for Jinja-style templates so it feels a little more like we're writing bare HTML. But they're of course still just templates, and they need a build step before they become valid HTML.

So it's true, if you're willing to use a DSL embedded in your server language (like JSX), then you'll have the full language tooling available to you. And this probably isn't giving up much over language-specific templates.

A JSX-equivalent for the Rust server-side rendering world would probably be maud [1] or leptops [2].

[1] https://github.com/lambda-fairy/maud

[2] https://github.com/leptos-rs/leptos

Maud as a performant templating engine that will ensure your templates are well-formed at compile-time and, in effect, minify the generated HTML output by not passing through unnecessary whitespace.

Maud is a fast Slim/Haml-esque templating engine which will automatically minify your HTML at no extra charge because whitespace isn't significant in its syntax.

If you want to do backend development, give actix-web or Axum a try. If you need templating, take a look at Maud and if you want an ORM, take a look at SeaORM.

Personally, I'd recommend Maud if you don't need something with runtime reloading. Not only is it much faster, it implements a template language that is effectively the Rust-syntax equivalent to Slim or Haml using a procedural macro, so you get compile-time verification that your HTML output is well-formed.

For templating, Maud is fast, gives compile-time well-formedness guarantees, and outputs minified HTML by default as a side-effect of it being based on Rust macros. (It's of a similar design philosophy to Slim and Haml)

Hi, I have released Beta 3 version of the CAD+ Toolset for SOLIDWORKS which has many features to automate SOLIDWORKS (including free features in the Community edition). One of the most popular features is Properties+ (Standard edition) which allows batch adding, removing, changing custom properties of files, configurations, and cut-list items from SOLIDWORKS or from Windows File Explorer (you do not even need to have SOLIDWORKS installed to use this feature). Here is a detailed demonstration: A simple way to manage SOLIDWORKS custom properties. This is one of the use cases: Propagate and reconcile SOLIDWORKS custom properties from the template. If you want to give it a try you can download the Beta 3 version by clicking the Try Future Version from the web-site. You can then request a free trial license.

Here is the link to the actual QR code project: https://github.com/xarial/cad-plus/tree/dev/src/Drawing, but you will need to pull the full solution. All the references are Nuget packages, so just restore - and you should be good to compile and run. Run SwAddIn project and you will see the menu in SOLIDWORKS. Let me know if any issues.