Snapmaker Luban printing needs to be more filament centric. By this I mean that each filament (parameter set) should have its own separate values (configuration) maintained independent of the projects. Any differences between a “filament settings” and a “Project’s settings” for a filament parameter, should be highlighted so that the end user is made aware of the difference.
In other words have the filament parameters managed separately from the projects. If a project’s value is set different from its filament value, highlight this to the end user.
You can already create and save and name different presets.
Luban is meant to be a basic entry level slicer.
If you want more control use Cura or Prusaslicer. They already have settings preset for different brands and types of filaments.
Under the File pull down, it lists: New Project, Open Project, Recent Project, Case Library, Save Project, Save As, Import Object, Export Object, Export G-code, and Exit. What do you mean by save and name different presets. Perhaps you a referring to the project Export and Import buttons under the Material and Printing Settings.
From a logical structural view point the filament parameters (temperatures, fan speed, print speeds, retraction) need to belong to the filament object.
The way Luban is now organized, the project parameters, which includes the filament parameters, blend and change as multiple projects get reviewed and managed (saved) to the point that it is frustrating.
What happens now if an old project used a filament that was deleted or renamed? Currently, the logic falls apart. What should happen (in my opinion), is that the filament settings stored in the old project should recreated the.old filament settings and the filament should be flagged as a.a legacy filament (previously used). In other words. the filament settings need to be analyzed over the life=cycle of the application.