Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.arch.embedded > #12411

Re: [OT] Good Qt Book

From Sebastian Doht <seb_doht@lycos.com>
Newsgroups comp.arch.embedded
Subject Re: [OT] Good Qt Book
Date 2013-07-04 22:47 +0200
Organization A noiseless patient Spider
Message-ID <kr4mmc$uun$1@dont-email.me> (permalink)
References <cfmdnVW9tLOzg1fMnZ2dnUVZ5oednZ2d@giganews.com>

Show all headers | View raw


Am 26.06.2013 00:48, schrieb Tim Wescott:
> I'm sure that there is at least one good forum on Qt.  But I know most of
> y'all, I more or less trust your judgment, and I think another embedded
> software guy is going to do a better job of recommending a book than a
> typical desktop programmer.
>
> I have O'Reilly's book on Qt, but it's an older version that covers Qt 3,
> and it doesn't go into much detail on some things that are puzzling to me
> as I try to write things more complicated than "hello world", like
> exactly what defines the lifetime of an object and what are good
> strategies to rope large applications together with the whole "slot/
> signal" paradigm.
>
> So -- do you do Qt programming?  Do you have any books to recommend?
>


If you use Qt4, a book about Qt3 is rather useless, lots of things have 
changed. The O'Reilly seems to be good but I have not looked at one for 
a while (I am sure a German book won't help you much). I do only litte 
GUI stuff with Qt once a while and the online documentation is really a 
great ressource.
Just beware that the Qt framework can handle a lot of stuff but its main 
focus is GUI and not performance. I heard stories were performance of 
applications using Qt for everything was an issue. The signal-slot 
paradigm can also become a mess to debug for applications using rather 
complicated control work. Thats why it is always a good to use Qt only 
for the GUI frontend and let it talk to a backend application doing the 
real work.

Best regards,

Sebastian

Ps: To say at least something useful: The lifetime of a Qt Object is 
bound to the lifetime of its parent which is usually some visual element 
(Dialog, Widget, MainForm etc.)

Back to comp.arch.embedded | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

[OT] Good Qt Book Tim Wescott <tim@seemywebsite.really> - 2013-06-25 17:48 -0500
  Re: [OT] Good Qt Book Sebastian Doht <seb_doht@lycos.com> - 2013-07-04 22:47 +0200
    Re: [OT] Good Qt Book Tim Wescott <tim@seemywebsite.really> - 2013-07-04 18:23 -0500
      Re: [OT] Good Qt Book Paul Rubin <no.email@nospam.invalid> - 2013-07-04 17:36 -0700
      Re: [OT] Good Qt Book info@quantum-leaps.com - 2013-07-09 07:33 -0700
        Re: [OT] Good Qt Book Tim Wescott <tim@seemywebsite.really> - 2013-07-09 11:35 -0500
          Re: [OT] Good Qt Book Les Cargill <lcargill99@comcast.com> - 2013-07-09 12:29 -0500
  Re: [OT] Good Qt Book Ulf Samuelsson <ulf_samuelsson@invalid.telia.com> - 2013-09-02 18:24 +0200

csiph-web