Hey Lays,

just a small (aesthetic) advise for the futur of your project: try to stay consistent in your conventions. You use CamelCase in some files, Camelized_Snake or snake_case in other, and even some unicase.

Pick one a stay with it. It's easier to maintain. You might also have a look at some of the kde projects to see how we organize projects.

It's not the most important thing, but it looks pro, and it's easier to get people to help you.

Out of this, I saw the pictures on planetkde: it's amazing. Your project is really great! Keep up!

Cheers
Olivier

Le 21/11/2015 21:36, Lays Rodrigues a écrit :
Hi, guys!
The new version of Br-Print GUI (Pandora) is avalable today!
After some weeks working on a big project remodeling, I finalized the tests to make this version available. One of the problems I was facing was the fact that I wrote the MainWindow as a God Class and it was doing too much unnecessarily. From that start point, the new challenge was to brake it all apart and make tiny
classes that do what it is suposed to do.
Was a great divide and conquer job to obtain this new version.
Thanks to Tomaz feedbacks and some tips from the internet, I could learn much more about Qt programming, OOP, and how to make a more easy to read and elegant code. Now we are facing some problems with memory leaking and thread synchronization, but they will be solved as fast as possible.
Now we're going to port the project to KDE's Playground.
If You want to take a look at this new code, access:
github.com/Simple-BR/Br-Print3D <http://github.com/Simple-BR/Br-Print3D>
See ya!
=D
__
*Lays Rodrigues*
*Developer Front-End at Br-Print3D Project*
*Student of Computer Science at UFF/PURO*
Organizadora da Semana da Computação UFF-PURO
www.facebook.com/semanacomputacaopuro <http://www.facebook.com/semanacomputacaopuro>
www.facebook.com/brprint3d <http://www.facebook.com/brprint3d>





Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

Reply via email to