PrusaSlicer on IpadOS?  

RE: PrusaSlicer on IpadOS?

@tellojsu

I’m with you. My work laptop does everything I need for work, and I’m not going out to buy a new laptop just for the slicer. I have an iPad and iPhone that I can make designs as needed with OnShape and right now the only hiccup is pulling out my antiquated personal laptop to run the slicer. I do t think it’s coming soon but hopefully it comes before this 12 year old brick of mine dies. 

RE: PrusaSlicer on IpadOS?

@neophyl

I have been using Shaper3D on iPad Pro and really like it. Would be great to have Prusaslicer on iPad Pro also.

RE: PrusaSlicer on IpadOS?

Makes me wonder if it would be easier to have prusaslicer support a set of command line arguments to output a gcode file. That would enable an “online” way to get a gcode and avoid the laptop. I am in the same boat. Have an iPad Pro and use shapr3d and it works great. Hate having to send to desktop to just open slice and load on prusa. Ideally I would just send the gcode file directly from iPad to my prusa over Bluetooth or wireless. 

RE: PrusaSlicer on IpadOS?

Prusa Slicer can be used from the command line.  I'm not sure personally of what is needed but I have seen issues raised about it on github so I know its possible.

https://github.com/prusa3d/PrusaSlicer/wiki/Command-Line-Interface

RE: PrusaSlicer on IpadOS?

Posted by: @neophyl

Prusa Slicer can be used from the command line.  I'm not sure personally of what is needed but I have seen issues raised about it on github so I know its possible.

https://github.com/prusa3d/PrusaSlicer/wiki/Command-Line-Interface

Interesting. If someone get the cli working in OctoPrint then in theory we can use it within OctoPrint for slicing.

RE: PrusaSlicer on IpadOS?

Are you guys talking about this? https://github.com/OctoPrint/OctoPrint-Slic3r

RE: PrusaSlicer on IpadOS?

@clawsar

You can use AstroPrint online to slice for free (Cura 3.6.0)

RE:

I have the students licence, the app isn’t very bad but threads and the plug in must be implemented, another lack is the timeline, I really need it.

RE: PrusaSlicer on IpadOS?

Is there any new updates about having a App slicer in the upcoming future? Really like to just work off a ipad and not have to grab my laptop when downloading and slicing files to print.

thanks.

RE: PrusaSlicer on IpadOS?

No word.  I saw it asked multiple times by text during vlogs and there was no official or unofficial comments.  

Posted by: @strgermishuys

Is there any new updates about having a App slicer in the upcoming future? Really like to just work off a ipad and not have to grab my laptop when downloading and slicing files to print.

 

thanks.

RE: PrusaSlicer on IpadOS?

https://twitter.com/bubnikv/status/1567382648959516672

Vojtěch Bubník on Twitter: "@ikb3d @Bryan_Vines We are actively investigating the options. As you commented, the tablet port would require a UI revamp, thus a lot of short and long term investment, maybe hiring another developer with iOS skills, another one with Android skills to be allocated for the tablet builds." / Twitter

RE: PrusaSlicer on IpadOS?

Sweet gods no. Otherwise we'll end up with the horribly compromised UI of Win11. Every couple of months they swap emphasis from touch to mouse/keyboard. They can't decide weather they want to sell Surfaces of an OS. Very nearly launched into a Microsnot rant .....

Pretty please Mr. Prusa by all means port to similar hardware but once you go down Android/iOS/whatever you start the inevitable slide into neither chalk nor cheese and nobody will be happy.

RE: PrusaSlicer on IpadOS?

Building an iPad app is substantially different from an Android app and the two efforts shouldn’t be considered as a single project.

As I mentioned previously in this thread, and it is only MORE true now, an iPad app and a Mac App can be built from the same code base and UX.

Apple has made the tools required to have a single code base that works on both platforms.

A first step could even be to only support mouse and keyboard on the iPad which all iPads are now capable of.

Android and Windows (and Linux) are not the same. Integrated stack. An Android port is 100% a new platform, but an iPad App is not.

RE: PrusaSlicer on IpadOS?

@Unteins

> As I mentioned previously in this thread, and it is only MORE true now, an iPad app and a Mac App can be built from the same code base and UX.

but then you also wrote:

> I don't think creating an iOS version is inherently difficult if wxWidgets is sufficiently mature on iOS. Even if it isn't, the majority of the work would be on the wxWidgets library, not on PrusaSlicer itself. Keeping the versions in sync shouldn't require a huge amount of work, unless you decide to remove wxWidgets and call native UI APIs on iOS. That's not to say that the UI would feel GOOD on iOS, it might be a bit clunky and too "desktop", especially if wxWidgets is immature on iOS. 

While it is all true, it says nothing about the effort of each of the tasks required. There is no wxWidgets support of iOS, we don't think there ever will and we don't have the resources to write iOS support for wxWidgets. We believe that the easiest would be to ditch wxWidgets on iOS, which means a complete UI rewrite.

RE: PrusaSlicer on IpadOS?

That would make sense to a degree. But, if you’re ditching it on iOS you should strongly consider ditching it on MacOS as well.

At which point the long term effort is adding 1 platform and removing another + a little additional effort.

Alternatively, update the UX library to something that supports more target platforms which would make it possible to maintain a single code base instead of having a fork.

Projects like VLC switched to QT because of challenges with wxWidgets. There’s also Flutter from Google as another.

And yes, of course, either of these would add additional resources and cost and take time. However, PrusaSlicer is open source and surely there are people in the Prusa community and the larger printing community who might contribute, if such an effort were initiated by Prusa. 

RE: PrusaSlicer on IpadOS?

I wonder if there are any install counts for windows and notWindows. No particular fan of either MS or WinWhatever, if as I suspect the favorite is obvious, why waste the enormous time and effort required to do something as marginal and IMHO stupid? Surely it would make more sense to address the 2264 open issues?

On the subject of open source, yer it's open source but it's got Joe's name on it, it's problably as much work to audit the code of some unknown bloke than to write it yourself.

The real measure of how much support there is for an iOS would be if a project appeared on Github to fork PS. Prove me wrong.