yldbouk / dpwt Goto Github PK

Since there are no options that can do exactly what we want, I believe the easiest solution is to create a backend that relies on other applications. Here is a rundown on what the backend might do. A script monitors the print db for the first queued job. When a job is first in line, it checks to see if the printer is ready to print something through this solution. If not, wait. If it is ready, slice the file, then begin printing it, checking the status every few minutes. If it errors, send a notification through some solution, like slack or discord (discord allows for webhooks, so it might be easier). When it is done printing, set the job status as needs processing. Notify the requester and the admin (we can notify the user by checking the state of their print and displaying a banner). When it is done, the admin would ready the printer for a new print, and set the job as done. Repeat.

Issues with this method:

• if a job is outgoing, it will make every other job wait for the job to be done, even if the next job is on a different printer.
• that’s it so far.

Change the header so that It is retrieved from one file instead of defined every time. Much like the footer. Vars could be used for page-specific links. Also probably replace login/logout with account link.

It's pretty bad.

• Add a new role called "changepassword"
• Make users with "changepassword" role have a popup on the first login to change password.
• Add reset password option in the admin console.
• Limit reset password option so the admin can not change the password of people with higher perms.

• User data and permissions are stored in session storage, which means you have you sign out and back in for it to update.

Possible Fixes:

• We could fetch user data every time we visit a page.
• Create a rng column that updates each time a change is made to the user.

Context

• For the first possible fix, we could access the login database and compare the variables there with current session storage.
• For the second possible fix, you can make a column that creates a random string every time the user data is changed. The string will be stored in the user data upon sign in. Then, on every page, it compares the string with the column. If discrepancies found, log the person out.

Create a form on the website to submit feedback. There will be something like three check boxes: issue, new feature and one just general feedback. Once submitted, if issue, webhook the issue to github with issue label. If a new feature, give that corresponding label.

• Create Page
• Create Script

-Here is an issue with some things what we might like to do in the future.

Pages

• Rewrite the 3D View Page
• Rewrite Printer Management Page (Refer to comment 552298803)
• Fill Up Home Page
• Replace <center> Tags With CSS
• Make Header Better with Dropdowns

Scripts

• Make scripts more compact.
• Get rid of error page and instead add message to script with back button.

A solution must be in place to print the .gcodes in the queue on the appropriate printer.

Add dropdowns to the header to make navigation easier. (#29)

The software can be found here at this Link. The goal is to set up on the laptop/server.

Add a user settings tab that appears after sign-in that when click on will allow the user to change their password and other information about their account. For example, "email, password, username, and name"

Rebranding from DPWT to QMaster on external sites. Internally will still be known as DPW

T.

For some reason, jobs and users are not showing up in the web, and I can't find the issue.

Same thing as account change, but specifically with printer lock, not other columns.

This could be easily done by checking the session selected printer, then querying the db. If locked, unset printer session variables and return to printer select page.

Admins or higher can not sign in when the selected printer is locked. Create a bypass for it.

When adding to queue using Auto Accept on the request page, it appears on queue in the db, but isn't actually added.

The script that resets the passwords apparently does not check that the password input and the reconfirm input are the same before changing it.

Set up the pause button so that it removes the job from Repetier queue and other things.

Instead of setting a printer when signing in, the printer should be asked for when making a new job. This will help eliminate the possibility of adding a job to the wrong printer.

This needs to be in place to automatically take the files that are in the "Queue" from the website upload. Then the converter will automatically place the new .gcode into the correct queue for that printer.

The purpose of this is to add settings on the website to control the slicer so the user can choose to add a raft and or supports to their object. This information can then be fed to the slicer so it can determine whether or not to print with a raft and/or supports.

Add a confirm password spot for the voluntary password reset, and add responses on the login page.

We need something to be in the homepage so it isn’t blank. Just something about what it is.

It looks bad.

When performing an action, such as pausing a job, the page loads too fast before the sql code actually executes, Just add a half second delay before reloading the page.

This explains everything.

Get the printer data from query instead of session data.

There are some padding issues on some pages, like the sign up page. Just add some padding. Also check all other pages for errors (typos, missing links, etc.).

why is this a thing this is going to cause issues oh god please why

Create a way like a button in job manager to re-add to queue. This is intended for jobs that don't print correctly.

We need to move the 3d file from /console/uploads to /console/uploads/__accepted.

Extension to #28
Check local storage for agreedToConsent. If false or doesn’t exist, show consent form warning of misuse. If agreed to, change agreedToConsent to true. If declined, redirect to home page. If agreedToConsent Is true, do not show form.

When loading feedback page, check of the user is blacklisted. If so, disable the form. Do the same in the script in case the page is altered.

This is for when the user is creating a job request and they can choose their color. So when printing is in session requests that are flagged with the same color can be printed at the same time.