Best way to learn Qt

[vermarajeev]

Hi guys,

I have got an opportunity to give training on Qt. Lets discuss on agenda's, topics to be covered and some qt assignments (with resources) which can help me and others(who wants to give training) to produce the best results. This will even help me to make my basics strong.

Please see that the assignments given is in order...First basics, then intermediate then complex.

Thanks guys

[wysota]

Learn or teach?

[vermarajeev]

Learn or teach?

Both When I teach others I too is learning something. Basically the training is for industry level where you teach freshers about Qt who are newbie(Who have never used Qt before).

Thanks

[wysota]

It depends on the audience then. If they have experience with other toolkits (like MFC), it might be good to compare the two and to show differences. That might give you a good starting point.

[vermarajeev]

It depends on the audience then. If they have experience with other toolkits (like MFC), it might be good to compare the two and to show differences. That might give you a good starting point.

Yes, the audience can be experienced( like MFC ) and fresh engineers ( newly passed out from colleges and finished there training on basics).
That is true I can compare Qt and other toolkits and have a good impact. I thought to go like this.

The training in basically on qt4 and is for a duration of 10-15 days or max 20.
1) Introduction to Qt
2) Advantages of using Qt over other toolkits
3) Disadvantages of using Qt over other toolkits
4) Compare Qt with other toolkits
5) Transition from Qt1.x.x to Qt4.x.x
6) 'Hello world' Example using Qt
7) Talk on QtDesigner
8) How to use QtDesigner
9) Differences between using QtDesigner and Hand Coding
10) Discussion on qmake and project files
11) Widgets with sample examples
12) Other widgets //pick some common widgets from QtAssistance and discuss

NOTE: After each session one assignment should be given on topics discussed. If the session is for 2 hours, the above topics should be distributed accordingly

These are some of the things in my mind right now.

Waiting!!!! for improvements.....

[wysota]

My hints:
- forget about Qt1-Qt3, go for Qt4 right away, engineers don't care about obsolete technology
- merge items 2, 3 and 4 into one
- ad. 9 - could you explain? What differences? There are no differences, you do exactly the same thing, only once automated and the other time not
- make them write as much code as possible themselves
- be sure you are well prepared, especially for answering unexpected questions

[jpn]

Qt is a large subject to talk about. Anyway, here are some topics (in arbitrary order) one could speak about:

• a widget tour
• object model
• signals and slots
• events (and filters)
• assistant, designer, linguist
• qmake, moc, uic, rcc
• model/view
• graphics view
• internalization
• resources
• containers
• painting
• styles (and style sheets)
• networking
• multithreading
• xml
• sql
• plugins
• the rest I forgot

The list is almost endless. The choice is yours. Just don't forget to emphasize the usage of Qt Assistant through the training course.

[vermarajeev]

I agree with wysota's suggestions about giving more assignments. But what assignments????

I have one idea. Here it goes.

Break a project into smaller modules (just like assignments), depending on the session give one assignment(based on project decided). Continue this process till entire project gets completed. Finally integrate...

Is this a good idea?????

If yes-->
We'll discuss on project and how it can be broken into assignment.

If No-->
Some more ideas....

Thanks

[wysota]

But what assignments????

A classic idea is to divide the attendants into two groups and tell one group to implement a simple application using MFC and the other to implement the same application using Qt. Based on the fact that they already know MFC, it should take the MFC group less time to complete the task. But you'll notice this is not the case - it will take approximately the same amount of time for both groups and it won't matter that one of the group has to learn to handle Qt and the other already knows how to deal with MFC. Just make sure you choose the application correctly and that you tell them how to use Assistant before they start

Break a project into smaller modules (just like assignments), depending on the session give one assignment(based on project decided). Continue this process till entire project gets completed. Finally integrate...

Is this a good idea?????

I don't think so. You'll have marauders that will be slowing you down - such an application requires to complete one task before starting the next. It's better to have them implement a bunch of small (one session) apps instead.

[vermarajeev]

A classic idea is to divide the attendants into two groups and tell one group to implement a simple application using MFC and the other to implement the same application using Qt. Based on the fact that they already know MFC, it should take the MFC group less time to complete the task. But you'll notice this is not the case - it will take approximately the same amount of time for both groups and it won't matter that one of the group has to learn to handle Qt and the other already knows how to deal with MFC. Just make sure you choose the application correctly and that you tell them how to use Assistant before they start .

As I already told the attendants can be either experienced in other toolkits or just newbie(recently passed out). I dont know how many knows MFC. What if 1 knows MFC and remaining are just newbie????

The idea is really classic one. The idea works for people who knows MFCs in one half and other half without it. I think it should be a portable idea. It should execute on both platforms(experienced in other toolkits or just newbie).

What do you say wysota?????

[wysota]

What if 1 knows MFC and remaining are just newbie????

Then there is no reason to teach them Qt if they don't know any other toolkit and want to switch environments (switch from what?).