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

Feature: gCode viewer and file browser? #36

Open
calonmerc opened this Issue Nov 8, 2017 · 3 comments

Comments

Projects
None yet
2 participants
@calonmerc

calonmerc commented Nov 8, 2017

Wondering if there's anything on your roadmap for implementing a gCode viewer (similar to that in Octoprint currently, uses a socket stream to pass data continuously)?

Or any thoughts on implementing a file browser per-printer that would allow starting the print remotely?

@kennethjiang

This comment has been minimized.

Owner

kennethjiang commented Dec 4, 2017

@calonmerc sorry for the delay. I was just back from an extended trip this week.

I guess your request to have gcode viewer and to remotely start print job are related. So I'm trying to address them both here.

I have not considered remote job starting as a feature on the roadmap because I think, more often than not, a user will have to do some work (taking previous print off the plate, leveling the bed, making sure the filament is what you want, etc) on the printer before kicking off the job.

Let me know if you do freqently need to start print job remotely.

@calonmerc

This comment has been minimized.

calonmerc commented Dec 7, 2017

I personally do, as I tend to get jobs for printing when I've left the house, but I always leave my printer clean and ready to go. Having to change filament would change that, as well, but generally I print in the same filament for most things. Otherwise, remote gcode would be more appreciated!

@kennethjiang

This comment has been minimized.

Owner

kennethjiang commented Dec 8, 2017

Ok I see the reasons why remote starting will be very helpful to you.

Both remote starting and gcode viewer can be quite complex to implement. I will put them on the roadmap and prioritize them against other features.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment