• Add fallback function for timeout of requests

• Use multiple origins for rss feed
• Rebase
• Fixes

About this one, we have two options:

• remove the support of configuring the notifications, making the install file unnecessary
• test this on Windows and OsX to see how they work and have the file installed.

@rizzitello idk if I like the cut on the letters. If I have space, why the letters are cut?

Sith comments

fix commit name

• Make 3dview focus when opening a file Problem: Can make the button focused
• Move widget to an scroll area

Rebase

@bcooksley yes it would. I will ping @tcanabrava to see what we can do about that.

After:

Rebase

Rebase

Rebase

Sith comment

Also, I need help on this to make the button on the stack be selected. @tcanabrava help!

No its not.
It's better be on our widgets stack. Instead of a hidden thing on settings. The user can access easily with one click, instead of two(settings -> profiles), that is the current setup.

Rebase

Rebase
Tomaz + Sith comments

Sith suggestion

• Remove profiles from atelierui.rc

I thought that was better to move to our current stack of widgets instead of the dialog.
Thougths are nice

Its just a wait of time use data var.

Sith and tomaz comments

• Add quick connect guide on welcome screen

We read the profile before connection. We don't have any event that monitor changes on the profile to make updates on the ui. I think that its safer if the use disconnects and connects again to reload the profile, so we can have a little more security on that.

• Rebase master

• Move the widget to the other area
• Change the text on the network error

Technical comments

1- About the rss feed: This welcome screen was inspired on the KDevelop one, that also gets the rss feed from the internet. If no internet connection is found, a message that a problem occurred is shown to the user. Show the news is a good thing because the user can keep track of our work, see what updates are coming and so on. This aggregates value to our product.
2- I added that inside the atcoreinstance because as comment before that log can't be on the entry point of atelier. I talked with more than 10 people, included designers, that said that is a bad thing, that kills accessibility.
In my mind, Atelier isnt for advanced users. Our public target are people that have a few or none experience with 3dprinting, because of that we need to have a good entry point on the software so they can, intuitively, know what to do. On the field of UX design we call those users personas, and this persona specific is the 'stupid' one. As I said before, the actual entry point inst intuitive at all. A user doesn't know what to do with a log that will throw a lot of info to him. I would rather work on a feedback system for the user. That is much better than the actual condition.
3- Atelier isnt just a tool to 3dprinting. It haves the goal to make the life of the user better. If we go only on the side of practicality and minimalism, we won't get many users. With my experience at work, we need to aggregate value, with we don't do that, the product/project are doomed.
4- "Instead of providing that let us just bury it under disabled stuff so you never can see it until you are successfully connected." -> Sith, I already told you that we can do things better, lockdown the log, until the printer is connected, was my first attempt when creating the AtCoreInstance. What I think is that in the case of an error, we can enable the log area so the user can check the log if they want to, as you made on the current status. You are assuming that the user will check the log in the case of an error, what I assume is that the user will or disconnect/connect the printer to the pc, or close and open atelier again. We can never assume what the user will do. However, we can do things better, we can elaborate a way to make the log available if the user wants to check it otherwise I think that we will just scare him.

Remove non used alias qrc

Preview of the changes:

Apparently, the problem with AtCore was fixed. Now we have a problem with QWT.

Rebase

rebase master

Maybe I could try to use SnoreNotify from @vonreth : https://github.com/KDE/snorenotify instead of KNotification.
Needs just to discover the boilerplate needed for that.

looks nice, but only allow that on the related widgets(3dview and editor)
doesnt make sense to have that on the videowidget for example.

Looks sane and works. Approve now or you will add the push_to_front thing?

I have the impression if the user has more than one instance printing, you will show a notification for each one. I think that if at least one is true, one dialog will be enough.
You break the switch, not the for...
I was trying to test here, but Atelier isn't finding fake printer ports...

@patrickelectric Kate has a view manager, that changes the factory when something changes see https://github.com/KDE/kate/blob/master/kate/kateviewmanager.cpp#L610
As you can see to activate a new view it removes the previous one.

@patrickelectric The problem is that since we dont remove the views, they start to have conflict and the files are not managed properly by KTextEditor and guiFactory(Main Window).
See the discussion on telegram.

@cullmann would you be able to give us a insight about this?
We are using KTextEditor, and the current code is crashing when Atelier closes if we have two or more files open.
Thanks

• Open two files
• Edit the second file
• Save the edition on second file
• Open the second file again (You can close it or open as a third file)
• it will give to you that warning. The file wasn't properly saved because the views are messed up.