• QString() for empty strings

• rebase

• rebase

• Tomaz Suggestion

In D17106#364685, @tcanabrava wrote:

Just a nitpick, an empty QString should be QString(), not QString("")

Just a nitpick, an empty QString should be QString(), not QString("")

• fix Typo in listWidget name

• Split a change off

• More Clazy fixes

• Internal Review

D16144 and D16129 Handle the bed size transformation.
Delta settings are not read. For those I would think we can set the height of the QSize to 0. Then we can check in the render the depth/height is 0 to know if we use width as radius for delta preview.

Some of this has been done @ervin has helped here among the remaining tasks are

• Camera Control needs to be expanded upon
• Handle previews for delta Printers.

Landed https://cgit.kde.org/atelier.git/commit/?id=d73b93a76eda1f97d587e5442655108d3ed24c72

In D15547#327353, @tcanabrava wrote:

This bit is in two reviews or I'm missing something?

This bit is in two reviews or I'm missing something?

In T9542#158516, @patrickelectric wrote:

@abetts One of the most important things in a 3D printer are:

• 4 Axis control
  • To control X, Y, Z, and E (the extruder, the guy that extrude plastic to create the 3D object)
  • The control need to be able to move with steps from 10cm to 0.01mm. (This values can change from printer to printer).
  • The extruder control should have a extruder multiplier that changes the extrusion quantity from 0.5x to 2x.
• Temperature control
  • This sets the temperature in the extruder and the heated bed. The max values should be set by the user.
• Command mode
  • The user should be able to send machine code to the printer, allowing some personalization.
  • This command code should output data from the printer and show to the user as well, like a normal terminal.
• Visualization tools.
  • Should show any temperature indicator with target and actual temperature, from both extruder and bed.
  • Should show the 3D model in a widget and what is already done by the printer and what should be done yet, this is usually done painting the lines in the 3D model with different colours.
• Connection widget:
  • This tool is used to select the serial port, or the tcp connection used to connect in the 3D printer.
  • Is also necessary to select the baud rate in a combobox, but also be able to allow the user to put the baudrate value as a normal text.
  • Should have a connec button
  • And also shows if the printer is connect or disconnected.
    
    Others usable widgets:
• Profile settings:
  • Set the settings of the 3D printer, like X, Y , Z max distance
  • Colour of the filament
  • Price of the filament (this is used to calculate the price of the model that is printing)
  • Max bed and extruder temperature per filament.
  • Printer name
  • Firmware type and etc
    
    This are the necessary widgets and to allow a minimum functionality in a 3D printer host.

@abetts One of the most important things in a 3D printer are:

• 4 Axis control
  • To control X, Y, Z, and E (the extruder, the guy that extrude plastic to create the 3D object)
  • The control need to be able to move with steps from 10cm to 0.01mm. (This values can change from printer to printer).
  • The extruder control should have a extruder multiplier that changes the extrusion quantity from 0.5x to 2x.
• Temperature control
  • This sets the temperature in the extruder and the heated bed. The max values should be set by the user.
• Command mode
  • The user should be able to send machine code to the printer, allowing some personalization.
  • This command code should output data from the printer and show to the user as well, like a normal terminal.

None of those really apply to the people who are 3d printing today.

In T9542#158511, @rizzitello wrote:

We do not know who our target users are. We really really need to decide upon a few "User Profiles" I think that will guide us alot in our interface choices.

We do not know who our target users are. We really really need to decide upon a few "User Profiles" I think that will guide us alot in our interface choices.

In T9542#158509, @rizzitello wrote:

The who model downloading / purchase section. We can't slice on atelier so this is currently not useful to our users.

The who model downloading / purchase section. We can't slice on atelier so this is currently not useful to our users.

Thank you for the comments. If you were to take anything out or add anything to the mockup, what would that be?

Hello Andres, Thank you for your first mockup.
But I would like to comment some points.

In T9542#158105, @rizzitello wrote:

The 3 interfaces of 3d printng that i find are most common.

1. Standard Desktop size, this has all our controls and options. Most people don't really like to use this to print because you have to leave your computer on for several days at a time and that will usually use more power than the printer to run the device.

The 3 interfaces of 3d printng that i find are most common.

Ok team, here is a first take at a mobile interface. Right now I am only thinking of this as an interface for phones. For a tablet or horizontal device, we would only stretch the UI horizontally or just do better placement but the same elements would be there. Please note that these are pre-made wireframes. They are meant to convey an idea only and not a final design. Focus on elements, menus and main ideas.

Some corrections/notes:

• Should be able to use in smartphones as well.
• 3D rendering of the gcode and update of the viewer while showing the printing progress.
• View for multiple camera monitoring
• The extruder and extrusion/retract need to handle multiple extruders.
• The extrusion and retract should allow the user to control the length of the filament (not a simple up down arrow).
• Panel for connectivity configuration (connecting to remote service of atcore).
• Show notifications for when:
  • print start
  • print finish
  • Something is wrong (YOUR PRINTER IS IN FIRE !)
    • If possible, showing a picture with the notification, showing the actual state of the printer.
  • Allow specific notifications like: Changing layer and etc.

We are going to a new UI for Atelier written with QML.
That interface needs to be adaptative for small screens like a RaspPi 7" touchscreen, and desktop screens.

Once your connected the connected Instance no longer updates the list of devices . (Or it stops when you start to print) . I will look in to this further when i get to my printer

1. I started a job from Atelier
2. For some reason the connection was lost during that(Maybe bad contact with the cable or whatever)
3. The printer stopped and Atelier didn't update with any new info.

If your printing how are you not connected? I don't understand how that even happens

I missed connection during print time, and the log isn't my main widget during that. So a feedback for the user about an error is needed.

These messages should be provided via atcore:atcoreMessage

• rebase

You probably want to keep x11 and wayland.

• rebase

• Rebase

• Apol's Suggestions
• Add Cleanups

In D13604#280010, @laysrodrigues wrote:

I think that for this we should wait to move Atelier from Playground to Extragear.

I think that for this we should wait to move Atelier from Playground to Extragear.

In D13392#275124, @tcanabrava wrote:

Sorry.

Sorry.

I was planning on using a combnation of the 3d view and the text editor to do this. The Simple form would be implimented within the text editor. This would just allow you to inject command(s) at a layer and/or where the cursor is. With the 3d viewer I'd like to allow the user to select the location of the command injection visually. Advance the 3d preview to a specific point in the print and select "inject Command" . This will let the user do any kinds of injection they can think of and very easy to select the exact location where these actions will happen. We only need to do a few things for the two widgets we will have really nice support for this.