Skip to content
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.

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

Cura 5555 ufp specification #12

Open
wants to merge 6 commits into
base: master/s-line
Choose a base branch
from
Open
Changes from 5 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
25 changes: 25 additions & 0 deletions docs/ufp.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,25 @@
# Ultimaker Format Package (UFP)

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Overall the documentation is very marginal. I'm missing things like:

  • The fact that it is based on the Open Packaging Convention
  • More elaborate goal of the format (combine tool path + preview images + metadata)
  • Backwards compatibility policy
  • Versioning policy
  • Implementation details in the libCharon library
  • The plan to make this the default filetype for all UM printers
  • Why it is different than 3MF (which could also have been an option, but we decided to not add the original 3D file which is a 3MF requirement)
  • The plan to make it forward-compatible with 3MF if we ever decide to add the original 3D model anyways (for example for cloud based re-slicing)
  • What is this Ultimaker G-code flavour?
  • The allowed file type and size for the thumbnail
  • Future support for multiple thumbnails (this was in the original spec iirc)
  • A representative example?
  • Probably some more things...


## Purpose:

The goal of this file type is to provide required data for the 3D printer to perform a print job.

## Structure:

A UFP file contains the following files:</br>

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In Markdown you can use the following format for a list:

  • item 1
  • item 2
  • item 3
    • subitem

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why not make 1 list with the file path and description per list item?

`\.rels`</br>

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why backslashes?

`\Metadata\thumbnail.png`</br>
`\Cura\`</br>
`\3D\model.gcode`</br>
`\[Content_Types].xml`</br>

* The rels and content type files are filled with the required XML data.
* The thumbnail.png is a medium sized rendering of the 3D shape to show during file selection. There can be only one thumbnail.
* The model.gcode describes how a 3D printer should print a job.
* Possible content of Cura folder :
* *.xml.fdm_material – files describe materials specifications which might be needed for a print job.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Missing the material signature file (which is why this whole thing is needed).


## Notes:

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just use this:

  • item 1
  • item 2

etc.

* For the interchange of files between the Slicer and Printers, currently, ASCII GCODE files are used, in a specific Ultimaker flavor.
* In future development, the content of folder Cura might be changed.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is kind of vague. In documentation you don't want to be vague.