Antoine Beyeler

@mariana-s-fernandes any motivation to tackle this one? ;)

@tyehle Any opinion on this?

@jwlarocque Thanks for the feedback. IIRC, we had some discussion on ordering already. Moving offset after `invert_x/y` would definitely break existing workflow. I'm not sure what would be the consequences...

I like this idea of explicitly listing transforms in order! This is how it could look like in the toml config file: ```toml [gwrite.demo] # ... # scale_x = 10...

I like the readability and conciseness of your first proposal (TOML array but SVG-like transform syntax). It somehow strikes a nice balance between self-explanatory, not too hacky in the context...

Great input thanks–we could definitely do something like this. Now, to shake things up, here is a completely different approach that just occurred to me: use actual vpype commands instead...

It randomly occurred to me that using the [jinja](https://jinja.palletsprojects.com/en/3.1.x/) templating engine might be a good avenue as well. In retrospect, possibly for vpype expression as well. Amongst the advantages I...

Well we have `last_x`/`last_y` lying around for the computation of `dx`/`dy`. Wouldn't it be trivial to just add them to the template variables? Am I missing something?

> It seems like @abey79 convinced @jleibs that `pixi shell` is not the best recommendation, and that the summary should be > > ``` > pixi run -e examples py-build...

List Item 2.0 is close to ready for this, but I'm encountering a number of issues: - `DataUi` implementations makes widespread use of `ui.label(...)` even for `UiVerbosity::Small`, which is bad...