ghostkeeper / convertto3mf Goto Github PK

I wish to implement some form of error handling. Some cases that need to be handled for certain are:

• What happens when an input file is incorrectly formed? As far as possible, ConvertTo3mf should try to repair as far as it reasonably can, but if it's impossible to read out any data we should give an error message to let the user know.
• Give an error message if the file can't be read for whatever reason (e.g. file doesn't exist, no read permissions, etc).
• Give an error message if the file can't be written for whatever reason (e.g. no write permissions, not enough disk space, etc).
• Give an error when running out of memory.
• Give an error if the input file is not a known file type. Currently whichever file type returns the highest score would win, even if that score is extremely low. We need to implement a lower threshold for this and return an error if all file types report below that threshold.

In order to improve usability and the feeling of openness around this application, we need to build a bit of a community around it. This includes:

• Adding a Contributing page.
• Adding templates for issues.
• Writing down documentation better on how to build the application.

While this application serves my personal need in its current state, I'd like to expand its functionality to what other people might need. One of the pillars of this is to be feature-complete for 3MF. While there are many features in 3MF, one of the most prominent ones is the ability to store textures.

The OBJ format that ConvertTo3mf currently reads has support for textures as well. To implement this feature, we need to implement reading textures from OBJ, storing them in our intermediary data structure, and then writing them to the 3MF file.

If there is an official way to include filament swap in the 3MF standard , then that should be the way to go.

However in the meantime at least for Prusa Slicer, the way they mark filament swap layer is via a file in ./Metadata/Prusa_Slicer_custom_gcode_per_print_z.xml, for example the content of that file may look like:

<?xml version="1.0" encoding="utf-8"?>
<custom_gcodes_per_print_z>
<code print_z="5.3000001907348633" type="0" extruder="1" color="#6CC52D" extra="" gcode="M600
G1 E0.5 F1500 ; prime after color change"/>
<mode value="SingleExtruder"/>
</custom_gcodes_per_print_z>

What was I am trying to do: I was trying to make a makefile that would generated 3mf files with filament swap at various z height

While this application serves my personal need in its current state, I'd like to expand its functionality to what other people might need. One of the pillars of this is to be feature-complete for 3MF. While there are many features in 3MF, one of the most prominent ones is the ability to store colours.

The OBJ file format that ConvertTo3mf is currently able to read also has the ability to store colours. We need to read those colours from that file format, store them in our intermediary data structure, and then write them out to the 3MF file.

To reduce anxiety and increase users' willingness to wait on the result, we should implement a textual progress bar in the terminal for the entire conversion progress. Above or below this progress bar we should write down what the application is currently doing.