Advanced Label Printing/Export Design - with Logo support

[akira69]

Assuming Discussion #36 is implemented, the next step is to provide a means to both incorporate the logo into the label and provide a more flexible label arrangement.

Therefore I imagine: a "advanced" tab to label print/export (default is the simple interface as it is)

• Reference implementation concept in Spoolman at feat(manufacturers): **Logos for vendors** logo-aware UI and label workflows (core, no bundled assets) Donkie/Spoolman#857

• includes logo handling and inclusion of logos to labels

• Use of spoolman-like label design UI, including preset management and saving : let the user define and save different label layouts

• Use of spoolman-like label template design: much more flexibility on order and detail of what is shown in a given label print-out

  • Separate label logo,Title,Body & QR code sections with individual controls and content management: let the user define content and design of a label's different sections

• "inverted" text capability: shamelessly allow a user to make a label as designed in http://www.3dfilamentprofiles.com

• Results:
  Logo Example:

Interface:

[akira69]

@ManuelW77 I got this running here:
akira69#14
it's setup as a tab in the print interface, so the current interface is not affected at all. with this interface one could customize this pretty widely - it's what I would like to have anyway - or something like it.

details are in the PR on my repo - but here are some example images of it working:

[akira69]

@ManuelW77 Curious on your feedback here - is this something you'd consider to implement? or something like it? the current label generation tab is very limited in customizability - this concept retains that simple interface and output, while adding an advanced design option.

[akira69]

I did update/improve via my PR akira69#14

Implementation

• Adds a dedicated spool print route and wires the spool detail Print Label action to it.
• Keeps the original print settings preview/layout behavior under its own tab.
• Adds a label designer tab with:
  • preset save/load/delete support
  • live preview with zoom controls
  • Separates each label in to Sections: Logo|Title|Subtitle|info|Info Column 2|QR
    Each with individual enablement and detail controls
  • autosizing title/subtitle format inputs
• Extends template parsing/rendering to support:
  • {token} insertion
  • optional wrapped blocks like {Text: {token}}
  • \n line breaks
  • **bold** and *italic*
  • ==inverse== for white on black
  • @@inverse@@ for filament-color inverse with automatic black/white foreground contrast
  • [size=120]...[/size] inline size control
  • {color_swatch[1]} and wider swatches via bracketed width values
• Refines QR custom URL behavior and wording so the difference between encoded values and the base URL is clearer.
• Adds matching i18n keys in English and German.

Screenshots

1. Label Examples

Template Syntax References for all text modifiers

• Shows: Complete syntax help covering all features
• Demonstrates: All token, wrapping, sizing, bold, italic, and inverse features

All variables from Filaman are clickable/searchable/collapsible for use in the Format sections

Preset save and recall

Addition of color Filaman label inset

(Fix) increased original logo resolution & QR Resolution

Classic Print Settings Tab Maintained

• Shows: Original Print Settings tab intact and untouched
• Demonstrates: Separation of classic workflow from new designer

[akira69]

Implementation summary (akira69#14):
The advanced label designer is fully functional as a second tab in the print interface (original tab unchanged). Key capabilities:

Section-based layout (Logo / Title / Subtitle / Info / Info 2 / QR) with individual enable/content controls
Preset save/load/delete
Full template syntax: {token}, bold, italic, ==inverse==, [@@color-inverse@@], [size=N]...[/size], {color_swatch[N]}
All Filaman fields available as clickable tokens
Live preview with zoom
This directly addresses the original goal and the logo-in-labels use case from discussion #36. Would really value @ManuelW77's feedback on whether this approach fits the upstream vision.

[akira69]

ok now it's a PR here: #80