(discussion) : Features and ideas

[akira69]

---> Moved to Discussions

(Discussion) : Features and Ideas

@ManuelW77

I had done a bunch of work on donkie/spoolman to add some features to that to get close to my goal
I was working to include spoolease integration, and a whole bunch of other stuff.
Over some weeks, I got little feedback. It doesn't seem spoolman is being actively developed. That led to some frustration. It was then I stumbled upon filaman. This 3d print management system is a great leap from spoolman, and achieves a lot of the goals that I was trying to add to spoolman. Yet, some of the ideas I had for spoolman could be integrated here. Here's what I have in mind - would love your feedback on each.

---

• 1) Create plugin for filament-swatch to work in Filaman
• filament swatch looks totally cool and is a nice way to visualize your database of spools, etc.
  • original repo: https://github.com/Disane87/spoolman-filament-swatch
• to Embed Filament Swatch into Spoolman, only few tweaks to that source code were necessary:
  • https://github.com/akira69/spoolman-filament-swatch/tree/feat/spoolman-hosted-mode
  • certainly more code changes would be needed on the filament-swatch side to interface to filaman rather than Spoolman - Though I broadly assume it'd not be too difficult.
• I had integrated Filament Swatch into Spoolman as proof of concept:
  • https://github.com/akira69/Spoolman_Labels/tree/feat/hosted-applications-framework-workspace
  • as Filaman already supports plugins, this may be be relatively easy - a lot of the spoolman work I had done for this was around "applications" - which Filaman basically solves by the existing plugin solution.
  • Here's an image of the tool embedded into Spoolman (would/could be similar in Filaman):

I'd give this one a 'nice to have' and would need agreement/alignment with Disane87 unless forked directly.

#41

---

• 2) (Issue) The Filaman UI is slow to populate when you have a large database (e.g. after sync of spoolmandb) - there must be some improvements to code to speed this up. I'd intend to debug/inspect to improve speed.
  (bug) Slow UI/Table Population with large database #42

---

• 3) Add filament label printing (to label swatches, etc - spool independent)
• already included in feat: add filament label printing #26
• Add Filament label printing capability #34

---

• 4) Add label export workflow (PNG/AML): In case print not working with your given printer
• already included in feat(export): add inline PNG/AML export to label print pages #27
• Add label Export workflow #35

---

• 5) Add Manufacturer Logos to UI, basic capability
• already included in feat(manufacturers): add manufacturer logo support #28
• Manufacturer Logo Support #36

---

• 6) Add a "advanced" tab to label print/export (default is the simple interface as it is)
  Advanced Label Printing/Export Design - with Logo support #37
• include logo handling and inclusion to labels - see feat(manufacturers): **Logos for vendors** logo-aware UI and label workflows (core, no bundled assets) Donkie/Spoolman#857 print improvements
• Use of spoolman-like label design UI, including preset management and saving
• Separate label logo,Title,Body & QR code sections with individual controls and content management
• "inverted" text capability, etc.
• Results:
  Logo Example:

Interface:

---

• 7) Add Plugin for manufacturer logo sync/bulk upload
  Manufacturer Logo Support #36
• next logical step from PR feat(manufacturers): add manufacturer logo support #28
• is in discussion with @ManuelW77
• enable download of manufacturer labels from an existing repo: https://github.com/MarksMakerSpace/filament-profiles
• enable zip upload of user managed logo files
• interface for logo match confirmation and manufacturer sync
• see feat(vendors/logos): add GitHub logo-pack sync workflow (no bundled assets) Donkie/Spoolman#872 for inspiration
• Results:
  existing github repo sync mechanism

---

• 8) Add "Formula" extra field capability JSON (by plugin most likely - or under/next to existing extra fields entry points)
• a user may want to have a dynamic "extra field" that is based on mathematical functions of existing fields
• e.g. "time since last dried", "time since last used", etc.
• see wip(settings): formula fields JSON-first base and preview akira69/Spoolman_Labels#14 for inspiration
• Results:
  Entry table

JSON interface with operators/helpers and field name variables listed

#38

---

• 8a) Extend formula helper with guided coding/variable picking with type aware interface
• see wip(settings): formula field guided builder follow-up akira69/Spoolman_Labels#13 for inspiration

https://github.com//discussions/38

---

• 9) Add table filtering/sorting to columns
• Current implementation has filtering in the top area, separated from the table iteslf. This is fine, but removes some workflows.
• Enable filtering and sorting for every column on the column header itself
• Enable filtering and sorting by extra-fields (see Add filtering and sorting for custom fields Donkie/Spoolman#773 for inspiration)
  individual column filter and sorting button enabled

https://github.com//discussions/39

---

• 10) column resize and reorder
• Introduce a reusable table interaction layer for column resizing and horizontal-scroll behavior across key list/settings tables. It also guards the new saved column-width state so a malformed local-storage entry recovers to defaults instead of blanking the page.
• inspired by feat(ui/tables): resizable columns with horizontal scroll + autofit Donkie/Spoolman#861
• lets the user define the visualization of a table
  Increase usability, data content, and visualization of all tables in Filaman #40

---

• 11) global action buttons (edit/delete) from text to icons with tooltips
• why have a cluttered UI with "Delete" and "Edit"?
• rather icons with tooltips:
  Increase usability, data content, and visualization of all tables in Filaman #40

---

• 12) extra fields as selectable in table views
• Tied with item 9 above : you should be able to use the extra field as a visible column in the table views
• Currently I don't see the extra fields as a option to show in table view
  Increase usability, data content, and visualization of all tables in Filaman #40

---

• 13) Spoolmandb plugin improvement
• Issue Unable to import certain manufactures from SpoolmanDB #15 seems real
• I had lots of problems with the import function using this plugin.
• Extend the language of spoolmandb import plugin to english. Jetzt ist nur Deutsch. Und, mein Deutsch lesen ist nicht so gut ;)

[ManuelW77]

Please give me a bit of time for the logo, label and filament things.
I work hard to deploy a Filament Platform with all this things, which is in sync with FilaMan.
Maybe i can release it next week, have to implement some little things an do some testing.

[akira69]

Please give me a bit of time for the logo, label and filament things. I work hard to deploy a Filament Platform with all this things, which is in sync with FilaMan. Maybe i can release it next week, have to implement some little things an do some testing.

Yes of course! I only wish to indicate what I'm thinking about and take your input if it's worth to bring over/work according to your vision.

Viel Glück!

[akira69]

by the way I'll move this over to discussions (point by point) for later back-and-forth when I get some time.
for now, as it is.

[akira69]

by the way I'll move this over to discussions (point by point) for later back-and-forth when I get some time. for now, as it is.

Done, now in as discussions & Issues