 The only issue I've been having is to add the .qrc resource file to the project since it's cmake. I did however modify the cmakelists.txt file to include it. Artem made temporary assets which I've included it in the welcome center's images folder
 I only wish we didn't have to do cmake tbh cause it makes the process of working with qt creator that much harder since it's overlap of two documentation resources
 Just want to clarify: we can't just use QMake instead? It would make this 10x easier.
 @SamuelBanya [I only wish we didn't have to do cmake tbh cause it makes the process of working …], There is documentation available for doing it with CMake
 @SamuelBanya [Just want to clarify: we can't just use QMake instead? It would make this 10x ea …], Nope, I very much disagree after using both extensively :)
 Can you point me in the right direction cause #qt only helped so much last night and it's been a pain in qt creator itself. If it's qmake it automatically does everything for you
 I don't do terminal based edits because qt + c++ is pretty complex already and I rely on qt creator to at least make sense of most of it
 :)
 @SamuelBanya [I don't do terminal based edits because qt + c++ is pretty complex already and I …], Then maybe we should sit down at one point and help you make sense of it
 Alright thats a better approach because I would even more so prefer to just do away with qt creator anyway I'm just a bit scared because there are so many moving parts in that single project. Otherwise I'm used to just running one file scripts in Python or adjusting JavaScript scripts.
 I tried looking even in the CMake side of things but mostly their docs point you to their book which I don't want to buy just for a single module
 Unless there are better docs on it with qt
[19:54] <lynorian> bot seems dead
[19:55] <lynorian> although not sure I can contribute much more for today
 @SamuelBanya [Alright thats a better approach because I would even more so prefer to just do a …], Why are you using c++qt instead of pyqt?
 Because Simon wants cmake
 Cause it's upstream
 I would definitely want to use python instead though
 But I've been learning c++ to compensate though it's still damn hard as a newbie.
 If we would agree to use that instead would you want to help me develop it?
 *stabs @tsimonq2*
 *points up* Why, Simon, why.
 well now i know why
 Fwd from tsimonq2: PyQt is slow
 Fwd from tsimonq2: CMake > QMake
 I agree that c++ is more efficient than python, but is that needed for a welcome center? @tsimonq2
 Software-properties Is done in pygtk and pyqt
 The WC (welcome center, bad acronym) supposed to be run only once. It could also be an offline webpage
 So it's not a program to be run more than once?
 Artems vision for it is like a one stop hub
 I kind of like that a lot so we don't have to have deep dives into menus
 Though I do know keyboard shortcuts exist through and they ARE handy. It might be nice for a newbie to just rely on the gui first
 I want as much people to feel comfortable to come over to our distro and I really feel we should be pushing for that, especially with new beginners.
 Maybe my understanding of what the WC is is wrong. I thought that it was like the "tour" windows has
 True
 (Photo, 1280x762) https://i.imgur.com/myj3hqf.jpg
 This is what Artem was thinking
 I do like your idea for an offline webpage though the functionality is needed to open up actual programs within the OS
 Which doesn't sound like an offline webpage could do
 Though honestly if we do another collab program let's shoot for python so I can get Hans to help me out consistently.
 Or rather past the April release, Hans, are there any Python related scripts we could both work on for ease of use for our users?