Manufacturer Logo Support

[akira69]

With the end-goal of pretty label printing, manufacturer logo support in FilaMan is an important first step

PR #28 adds backend logo storage/import/clear support, serves stored manufacturer logo files, exposes the new manufacturer logo fields in API responses, and surfaces manufacturer logos across the manufacturers, filament, and spool UI. But only this-fully user managed logos.

A Phase 2 and next logical step is to enable a logo database that a user can upload/link/sync to their Filaman instance.

• why not serve the logos as part of Filaman directly?: who knows about copyright or other such potential pitfalls in logo file ownership. therefore it makes sense Filaman not be provided with any company's IP.
• Rather, Filaman provides a interface for upload of a bulk-logo .zip file or direct fetch from an existing database (as a plugin most likely)
  • https://github.com/MarksMakerSpace/filament-profiles is an existing public database of "label friendly" logos, and print variations; this could be directly linked into Filaman as a logo source, and synchronized from for all the manufacturers in a user's local Filaman database.
• I did a whole bunch of work for spoolman to incorporate logo sync with this specific github repository, and provided a mechanism for .zip file upload.
  • you can review all the manufacturer logos (if you wish) before sync via a nice import window
  • one could also upload their own .zip with the same review flow
  • There is an integrated function to auto-generate a print-logo from an uploaded color logo
  • See the code here: feat(vendors/logos): add GitHub logo-pack sync workflow (no bundled assets) Donkie/Spoolman#872
  • Visualize it here:

A Phase 3 to bring logos to labels themselves, that's a separate discussion point

[akira69]

the latest version of Filaman supports logos. thanks @ManuelW77!

I will then bring out features from PR #28 into new PRs :

1. multi color filament presentation: first quick pass: feat: add multicolor shading to detail pages akira69/filaman-system#8
2. user uploadable logos: first quick pass feat: add manufacturer logo upload overrides akira69/filaman-system#9
3. manufacturing page logo column: first quick pass feat: move manufacturer logos into separate column akira69/filaman-system#10

[ManuelW77]

1. multi color filament presentation: first quick pass: feat: add multicolor shading to detail pages akira69/filaman-system#8

What does it mean? I don't understand.

2. user uploadable logos: first quick pass feat: add manufacturer logo upload overrides akira69/filaman-system#9

Nope, because i want Logos at the FilaManDB for all Users.

[akira69]

1. multi color filament presentation: first quick pass: feat: add multicolor shading to detail pages akira69/filaman-system#8

What does it mean? I don't understand.
@ManuelW77
means showing the color nature of the filament when mulit color in the view, here an example of visualization of striped and gradient (similar on spool page):

[akira69]

2. user uploadable logos: first quick pass feat: add manufacturer logo upload overrides akira69/filaman-system#9

Nope, because i want Logos at the FilaManDB for all Users.

maybe the hero feature is rather to modify this to be the submission platform for filamandb logos somehow, perhaps as a plugin.

[bnc-rainman]

2. user uploadable logos: first quick pass feat: add manufacturer logo upload overrides akira69/filaman-system#9

Nope, because i want Logos at the FilaManDB for all Users.

maybe the hero feature is rather to modify this to be the submission platform for filamandb logos somehow, perhaps as a plugin.

@ManuelW77
Da die Logos ausschließlich zentral über die FilamanDb kommen sollen.
Wäre es auch möglich das Logo von Amazon Basic zu fixen und von https://super-filament.de/ zu ergänzen?

Eine Alternative, bei der man sich nicht ganz so hilflos füählt, wäre trotzdem schön.

[akira69]

@ManuelW77 : what do you think about these? Generally, what's the right place for discussion? would discord be a better place for discussion and feedback about feature concepts and such? meaning, for all the discussion points I had started here? Seems there's a low interaction via github.

Once I get the logo / printed label stuff working as I would like to be able to adjust filaman to achieve, then I feel great about going all-in!

[akira69]

@ManuelW77 : I went to look for filamandb: where can one place a new logo? did I miss something in the UI? e.g. Hobby Lobby manufacturer. I have a bunch of those spools, but don't find a logo in filamandb: this was my basis for considering the upload interface. Today, how can one submit / request a logo inclusion to Filamandb? it's not a separate repo in github that I could find. Or did I miss something in the filaman web app?

the logo I'd upload is:
https://www.reddevelopment.com/chandler-101-centers/wp-content/uploads/sites/29/2024/09/hobby-lobby-logo-300x58_logo.webp

[ManuelW77]

I added the Logo to the DB
https://db.filaman.app/manufacturers/detail?slug=hobby-lobby

[akira69]

✅ Phase 1 complete (upstream v1.2.1): Base logo storage, serving, and UI display shipped upstream — great work @ManuelW77!

In my fork, building on top:

akira69#9 — user-uploadable logo overrides: lets a user supply their own logo for any manufacturer locally (for cases like @ManuelW77 noted where the "right" logo for a user may differ)
akira69#10 — manufacturer logo column in the manufacturers table, making logos visible at-a-glance

For Phase 2 (logo sync), I now have a clearer picture after the Hobby Lobby exchange. There are two natural directions:

Variant A — sync logos down from FilamentDB into local Filaman (for manufacturers already there); most useful for the majority of known manufacturers
Variant B — a workflow for submitting a logo to FilaManDB from within Filaman (for missing ones like Hobby Lobby was); this is what @ManuelW77 was describing as the preferred direction
Both of these make sense as a plugin. Variant B could be as simple as a deep-link into [db.filaman.app] with the right manufacturer context pre-filled. Planning both variants now.