@programminginc - страница 404

LoneWolf

Anybody run my code.

klimi

Anybody run my code.

Yes sir!

LoneWolf

No, I'm a junior.

klimi

No, I'm a junior.

yes junior!

Dima

junior's code = stackoverflow code

Dima

junior's code = stackoverflow code

klimi

junior's code = stackoverflow code

thats mine xD

klimi

LoneWolf

Yes sir!

Note that there is a correction at "backslash n", there should be single quotes.

klimi

hm?

LoneWolf

Arrhh, I think I have embarrassed myself due to my delayed replies and lack of devices. I will try to come back when I get a new smartphone this week.

klimi

i don't understand

Anonymous

Which header file for GUI Gtk or qt => Linux Which one for windows ?

klimi

gtk or qt

klimi

qt is better tho

klimi

if you are speaking about native ones then winapi

klimi

(WinForms)

Anonymous

if you are speaking about native ones then winapi

Oh 👍

Anonymous

qt is better tho

😱

klimi

i will give you link

klimi

😱

it looks +- same on all platforms

klimi

Which header file for GUI Gtk or qt => Linux Which one for windows ?

are you familiar with qt?

Anonymous

Oh Ram usage in qt is higher than gtk ?

klimi

oh

klimi

idk

Anonymous

are you familiar with qt?

More with gtk

BinaryByter

qt is better tho

qt is a little shit

BinaryByter

its overcomplicated

klimi

More with gtk

you can do gui on windows with gtk too

BinaryByter

use gtk

BinaryByter

it is a lot better

klimi

https://www.quora.com/Which-is-less-system-intensive-gtk+-or-qt

klimi

it is a lot better

hmmm

BinaryByter

These days machines are fast. Very very fast.

BinaryByter

I hate this argument

Bader

writing tests should be a fun action

tests are fun :)

BinaryByter

tests are fun :)

L O L

Dima

tests are fun :)

yes

klimi

it is a lot better

Developing for QT is a bliss for a C++ developer. Every single aspect of it is so well documented that you really envy it, because you know that you will never document your own API that good. Even code adaptation between major releases is made easy to do due their clarity on explaining every single change thoughtfully and with great didactic. Their API itself is quite a work of art, a show of well wrote C++ OO code. That being said, QT is locked in C++. It don't have anywhere near the same amount of language bindings as GTK. I believe that this is due QT's overbearing nature, since it is a tad lot more than just a GUI toolkit, so creating bindings to other languages is a difficult task without a fairly large team. Indeed comparing QT with GTK is quite unfair from a developer POV. QT is a application framework that happens to have a GUI toolkit geared towards creating multi platform applications, with a SQL framework, XML parsing framework, network bindings, thread API, multimedia API to access camera, soundcard and mic, a event system that extends way beyond GUI... while GTK is just a GUI toolkit and nothing more.

Dima

if you thinking that tests are production time waste then it seems you never worked in a real production environment

klimi

Developing for QT is a bliss for a C++ developer. Every single aspect of it is so well documented that you really envy it, because you know that you will never document your own API that good. Even code adaptation between major releases is made easy to do due their clarity on explaining every single change thoughtfully and with great didactic. Their API itself is quite a work of art, a show of well wrote C++ OO code. That being said, QT is locked in C++. It don't have anywhere near the same amount of language bindings as GTK. I believe that this is due QT's overbearing nature, since it is a tad lot more than just a GUI toolkit, so creating bindings to other languages is a difficult task without a fairly large team. Indeed comparing QT with GTK is quite unfair from a developer POV. QT is a application framework that happens to have a GUI toolkit geared towards creating multi platform applications, with a SQL framework, XML parsing framework, network bindings, thread API, multimedia API to access camera, soundcard and mic, a event system that extends way beyond GUI... while GTK is just a GUI toolkit and nothing more.

https://www.reddit.com/r/linuxmasterrace/comments/6ee9sy/gtk_vs_qt_what_do_you_prefer_and_why_2017_edition/

BinaryByter

Developing for QT is a bliss for a C++ developer. Every single aspect of it is so well documented that you really envy it, because you know that you will never document your own API that good. Even code adaptation between major releases is made easy to do due their clarity on explaining every single change thoughtfully and with great didactic. Their API itself is quite a work of art, a show of well wrote C++ OO code. That being said, QT is locked in C++. It don't have anywhere near the same amount of language bindings as GTK. I believe that this is due QT's overbearing nature, since it is a tad lot more than just a GUI toolkit, so creating bindings to other languages is a difficult task without a fairly large team. Indeed comparing QT with GTK is quite unfair from a developer POV. QT is a application framework that happens to have a GUI toolkit geared towards creating multi platform applications, with a SQL framework, XML parsing framework, network bindings, thread API, multimedia API to access camera, soundcard and mic, a event system that extends way beyond GUI... while GTK is just a GUI toolkit and nothing more.

yea the docs are nice

BinaryByter

if you thinking that tests are production time waste then it seems you never worked in a real production environment

indeed

BinaryByter