Interfaces auto-connect for prusa-slicer snap

Hello there,

I’d like to request auto-connect on the following interfaces, for newly created prusa-slicer snap.

  • home. Reasoning is that, being a 3d printing slicing program, it takes mesh files (STLs, OBJs, etc.) and converts to G-CODE and/or image streams to be consumed on the printers. Both input files and/or output files can/should be stored somewhere, so user can handle, store or even modify them.

  • removable-media and mount-observe. Many (if not all) printers come with an SD card slot, since that helps prevent input code shortages (PC freezes, etc.), since stopping printing in the middle of a part is often a non-recoverable error and may lead to hours of wasted time, electricity and material (filament). PrusaSlicer allows the user to save G-CODE files directly to a plugged SD card, if there’s one and, as such, it must be able to detect and access the media.

Store entry:

Please let me know if you have any doubts.

Thanks!!

The home interface is already autoconnected on classic distro.

+1 to auto-connect mount-observe since it seems a reasonable request if the application is dealing with SD cards.

As for removable-media, the description for prusa-slicer says “takes 3D models (STL, OBJ, AMF) and converts them into G-code instructions for FFF printers or PNG layers for mSLA 3D printers” so this falls broadly into the “media viewers/editors” category. Not to mention, common practice for this application is saving the media to an SD card so it may be placed in the printer to avoid printing hiccups.

A cursory glance at https://www.prusa3d.com/prusaslicer/ shows this is “a mature, well-known application”.

What remains is vetting the publisher according to at least one these criteria:

  • the snap’s (vetted) publisher is a mature, well-known entity
  • the snap’s (vetted) publisher is the upstream of the software
  • if the snap is published by someone other than upstream, the publisher must be vetted and either be an established committer to the upstream or the wider snap ecosystem (eg, an established well-known contributor to the software itself, a member of the snapcrafters group, etc)the publisher must be vetted and either be an established committer to the upstream or the wider snap ecosystem (eg, an established well-known contributor to the software itself, a member of the snapcrafters group, etc)

@ivo.cavalcante states a disclaimer on https://snapcraft.io/prusa-slicer which reads “This is an unofficial package , under development. Please report any issues to , unless reproducible in upstream version - and, thus, not a packaging problem.

which does not meet either of the first 2 criteria. @advocacy - can someone vet @ivo.cavalcante using this criteria: “the publisher must be vetted and either be an established committer to the upstream or the wider snap ecosystem (eg, an established well-known contributor to the software itself, a member of the snapcrafters group, etc)”?

@advocacy - if @ivo.cavalcante doesn’t meet these criteria, perhaps other options are available, like @ivo.cavalcante joining snapcrafters, snapcrafters being a collaborator on prusa-slicer, the snap packaging upstreamed, upstream commenting that they trust @ivo.cavalcante with the packaging, or something else.

Thanks for returning. I must have misunderstood the docs, was under impression that home interface auto-connect should be explicitly requested. As such, please ignore it.

I intend to take the snap upstream, once it’s mature. Not sure if they’ll be interested, since they already provide an AppImage as part of release process, but I’ll give it a shot anyway.

As for Snapcrafters, not sure how to proceed.