Skip to content

[Request] - Multiple templates #186

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
andyrobreid opened this issue Jun 22, 2021 · 9 comments
Closed

[Request] - Multiple templates #186

andyrobreid opened this issue Jun 22, 2021 · 9 comments
Labels
status: closedByBot status: markedForAutoClose Issue will be closed automatically status: waitingForTestFeedback type: enhancement New feature or request

Comments

@andyrobreid
Copy link

As far as I'm aware and have tested. You can only have 1 template or profile as mentioned in #2.

Is there development for multiple templates or even a template for each vendor?
@OllisGit OllisGit added status: waitingForFeedback Wating for Customers feedback type: enhancement New feature or request labels Oct 24, 2021
@OllisGit
Copy link
Owner

Hi @MadeforMaking,

currently I have no idea how the UI should look like for that feature. So maybe you can create some UI-Mockups how the template management should be.

Thx in advance
Olli

@andyrobreid
Copy link
Author

I'll have a look soon, busy with work atm, but a simple mock shouldn't take long.

@timn
Copy link

timn commented Jan 10, 2022

I just came across this as well and I was confused when I tried to create templates for, e.g., PETG and PLA.

Before trying SPM I used Filament Manager, that has profiles which make it really easy to collect generic information. I wanted to try SpoolManager as it seems to be more actively maintained. If SPM would enable to collect certain types of filament in one place as a profile, e.g., vendor, material, density, cost etc., then when creating a specific a spool you could select a profile and add additional information such as color, weight etc. That could be done in the settings to decouple it from the specific spool management on the dashboard. Just my two cents.

@OllisGit
Copy link
Owner

Hi,
thanks for the input. I also rethink about an solution. The easiest way to implement is as follows:

  • You can mark as many spools as you like as a template spool (current: only one is allowed)
  • When you create a new spool you can select from a list of template spools

image

image

@OllisGit OllisGit added the status: inAfterNextRelease Will be implemented/fixed after next release label Jan 11, 2022
@timn
Copy link

timn commented Jan 12, 2022

That would already be an improvement! What would help is to distinguish creating a template from creating a spool (or gray out fields not needed for a template once the checkmark is made). In the overview list for spools a filter for templates would also be helpful.

@OllisGit OllisGit added status: analysing and removed status: waitingForFeedback Wating for Customers feedback status: inAfterNextRelease Will be implemented/fixed after next release labels Jan 29, 2022
@OllisGit OllisGit added status: inNextRelease Will be implemented/fixed in next release and removed status: analysing labels Feb 14, 2022
OllisGit added a commit that referenced this issue Feb 17, 2022
@OllisGit
New Version 1.7.0rc1
aad7330 
- E #246 EventBus-Events to support MQTT-Topics
- E #186 multiple templates (with field selection)
- E #191 Include PTFE tube length for remaining check
- E #221 Preview of QR-Code
- E #207 Define IP/URL for QR-Code generation
- E #220 Output of database id in QR-Code view
- E #236, B #228 Output of total spools in tab-view
- E Output of database id in QR-Code and in table

- B #245 Show last weight digit
- B #235 custom colorname not stored
- B #225 copy was disabled during printing
@OllisGit
Copy link
Owner

Hi,

in the latest RC-Verison 1.7.0rc1 I changed a lot of stuff, maybe this issue is also solved.
Please test and give feedback

Thx, in advance
Olli

@OllisGit OllisGit added channel:RC status: waitingForTestFeedback and removed status: inNextRelease Will be implemented/fixed in next release labels Feb 17, 2022
OllisGit added a commit that referenced this issue Feb 17, 2022
@OllisGit
Preparation of Version 1.7.0
6bdfebf 
- E #246 EventBus-Events to support MQTT-Topics
- E #186 multiple templates (with field selection)
- E #191 Include PTFE tube length for remaining check
- E #221 Preview of QR-Code
- E #207 Define IP/URL for QR-Code generation
- E #220 Output of database id in QR-Code view
- E #236, B #228 Output of total spools in tab-view
- E Output of database id in QR-Code and in table

- B #245 Show last weight digit
- B #235 custom colorname not stored
- B #225 copy was disabled during printing
@OllisGit
Copy link
Owner

Hi,
new Version 1.7.0 is released.

Please test and give feedback.

Thx, in advance
Olli

@github-actions
Copy link

This issue has been automatically marked for closing, because it has not had activity in 30 days. It will be closed if no further activity occurs in 10 days.

@github-actions github-actions bot added the status: markedForAutoClose Issue will be closed automatically label Apr 18, 2022
@github-actions
Copy link

This issue was closed, because it has been already marked for 10 days with no activity.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
status: closedByBot status: markedForAutoClose Issue will be closed automatically status: waitingForTestFeedback type: enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@timn @OllisGit @andyrobreid