Prusaslicer: Include AppImage metadata

Created on 9 Aug 2019  Â·  9Comments  Â·  Source: prusa3d/PrusaSlicer

Version

2.0.0

Operating system type + version

Linux / AppImage

Behavior

PrusaSlicer's basic AppImage support seems incomplete. There are a few key missing bits:

  1. Icon. If using appimaged, the app has no icon. I presume it is missing one in the correct location. Cura seems to handle this here, similar to other apps. Looking at #451 it seems like this has worked at some point, but it's not showing for me on the latest version.
  2. File associations. Similarly, it is not automatically associated with *.stl and other supported files. Cura also does this well, which I presume is a combination of having a desktop file and installing it during compilation.

I would be happy to dig further into this and try to contribute, but the process is undocumented as discussed in #1253.

All 9 comments

The icon problem is likely caused by the following issue:
https://github.com/prusa3d/PrusaSlicer/issues/1431#issuecomment-502438554

Icon. If using appimaged, the app has no icon.

@goncalossilva please verify with the upcoming PrusaSlicer 2.1.0-beta.

File associations. Similarly, it is not automatically associated with *.stl and other supported files.

Cura has in its desktop file:

MimeType=model/stl;application/vnd.ms-3mfdocument;application/prs.wavefront-obj;image/bmp;image/gif;image/jpeg;image/png;text/x-gcode;application/x-amf;application/x-ply;application/x-ctm;model/vnd.collada+xml;model/gltf-binary;model/gltf+json;model/vnd.collada+xml+zip;

@bubnikv The PrusaSlicer 2.0.0 AppImage is lacking any MimeType= in its desktop file. Adding it there should do the trick.

I have asked @lukasmatena to look into it. The purpose of MimeType is not
clear to me. What types should we put there for our slicer?

so 21. 9. 2019 v 14:08 odesílatel probonopd notifications@github.com
napsal:

Icon. If using appimaged, the app has no icon.

@goncalossilva https://github.com/goncalossilva please verify with the
upcoming PrusaSlicer 2.1.0-beta.

File associations. Similarly, it is not automatically associated with
*.stl and other supported files.

Cura has in its desktop file:

MimeType=model/stl;application/vnd.ms-3mfdocument;application/prs.wavefront-obj;image/bmp;image/gif;image/jpeg;image/png;text/x-gcode;application/x-amf;application/x-ply;application/x-ctm;model/vnd.collada+xml;model/gltf-binary;model/gltf+json;model/vnd.collada+xml+zip;

PrusaSlicer 2.0.0 is lacking any MimeType= in its desktop file. Adding it
there should do the trick.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/prusa3d/PrusaSlicer/issues/2732?email_source=notifications&email_token=ABMPSI4XJ23CS2B27XUK5FDQKYFC3A5CNFSM4IKQDPI2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD7IQRWA#issuecomment-533792984,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABMPSI2LXUM2ZVPWOXXXW6TQKYFC3ANCNFSM4IKQDPIQ
.

The purpose of MimeType is not clear to me.

It allows the user to double-click, e.g., a .stl file, and it will be opened in PrusaSlicer.

I was confused why Cura would want to register for image/bmp;image/gif;image/jpeg;image/png

Good question indeed. In fact I think it is not a good idea to do that.

There are quite a few discrepancies between what PrusaSlicer can open/import and what's in that list. This should probably be cleaned up and updated.

*.stl:

  • model/stl (official)
  • application/vnd.ms-pki.stl (also used)
  • application/pla (also used)

*.obj:

  • ~text/plain (apparently official, too broad to be used...)~
  • text/prs.wavefront-obj (also used)

*.amf:

*.3mf:

I would suggest sticking with the "official" media types (except obj). That means PrusaSlicer would use:

MimeType=model/stl;text/prs.wavefront-obj;application/x-amf;model/3mf;application/vnd.ms-3mfdocument;

I have updated the AppImage with
MimeType=model/stl;application/vnd.ms-3mfdocument;application/prs.wavefront-obj;application/x-amf;
from Cura. It will be contained in the PrusaSlicer 2.2.0 final.

Closing.

Thanks @bubnikv! Borrowing from Cura is a great improvement. I don't know if you saw the comment above, but not all types are up-to-date, nor are Cura and PrusaSlicer completely on par in what they can open and import. A better list that's tailored specifically to PrusaSlicer is:

MimeType=model/stl;text/prs.wavefront-obj;application/x-amf;model/3mf;application/vnd.ms-3mfdocument;

I'd be happy to PR this but it doesn't look like it's OSS. The reasoning is 2 comments above this one, and I'm happy to discuss further if needed. :+1:

Was this page helpful?
0 / 5 - 0 ratings

Related issues

pricedev picture pricedev  Â·  4Comments

i-make-robots picture i-make-robots  Â·  3Comments

guestisp picture guestisp  Â·  3Comments

Tirpitz93 picture Tirpitz93  Â·  3Comments

Foxtrek64 picture Foxtrek64  Â·  4Comments