-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Include AppImage metadata #2732
Comments
The icon problem is likely caused by the following issue: |
@goncalossilva please verify with the upcoming PrusaSlicer 2.1.0-beta.
Cura has in its desktop file:
@bubnikv The PrusaSlicer 2.0.0 AppImage is lacking any |
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
<#2732?email_source=notifications&email_token=ABMPSI4XJ23CS2B27XUK5FDQKYFC3A5CNFSM4IKQDPI2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD7IQRWA#issuecomment-533792984>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABMPSI2LXUM2ZVPWOXXXW6TQKYFC3ANCNFSM4IKQDPIQ>
.
|
It allows the user to double-click, e.g., a |
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:
*.obj:
*.amf:
*.3mf:
I would suggest sticking with the "official" media types (except obj). That means PrusaSlicer would use:
|
I have updated the AppImage with 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:
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. 👍 |
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:
I would be happy to dig further into this and try to contribute, but the process is undocumented as discussed in #1253.
The text was updated successfully, but these errors were encountered: