mirror of
https://github.com/maziggy/bambuddy.git
synced 2026-05-09 08:25:54 +02:00
[GH-ISSUE #567] [Feature]: Printer Page - Add a print button on the printer card #371
Labels
No labels
A1
automated
automated
bug
bug
Closed due to inactivity
contrib
dependencies
dependencies
duplicate
enhancement
feedback
hold
invalid
Notes
P1S
pull-request
security
ThumbsUp
user-report
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/bambuddy-maziggy-1#371
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @aneopsy on GitHub (Mar 2, 2026).
Original GitHub issue: https://github.com/maziggy/bambuddy/issues/567
Originally assigned to: @aneopsy on GitHub.
Problem or Use Case
Current Quick Print UX
The existing workflow to launch a quick print requires too many steps and creates unnecessary friction.
That's five distinct steps with redundant actions, especially having to re-locate a file immediately after uploading it, just to start a simple print.
Proposed Solution
Streamlined Quick Print UX
We want to simplify the printing workflow by reducing friction and unnecessary steps.
Proposed flow:
The whole process goes from four deliberate actions down to a seamless, guided sequence.
Bonus - Optional file saving:
The upload modal includes a "Save to File Manager" checkbox, enabled by default. Users can uncheck it to skip saving the file, which is especially useful for quick test prints and avoids cluttering the file manager with throwaway files.
Alternatives Considered
No response
Feature Category
File Manager
Priority
Would improve my workflow
Mockups or Examples
No response
Contribution
Checklist
@maziggy commented on GitHub (Mar 2, 2026):
What's about making the printer card a file drop zone? Not sure, but it just came to my mind.
@aneopsy commented on GitHub (Mar 2, 2026):
I thought about that, but I found a couple of pros and cons.
Pros:
Cons:
I can implement both options so we can test them and evaluate later whether they both still make sense to keep.
@maziggy commented on GitHub (Mar 2, 2026):
I agree.