Skip to content

Week 1

Jump to bottom
Tino Pyssysalo edited this page Jun 17, 2018 · 42 revisions

Week 1 - Qt essentials (18,5h)

!NB: Page numbers refer to the Qt Essentials Edition Slide Set!

This page contains all of the suggested topics of interest for the course week.
Each topic title will link to the related page (in this Wiki) on which the course material for said topic is being worked on.
The topic title also includes the suggested priority (0 = high, 1 = medium, 2 = low) and suggested amount of work the student will use on each topic (this may also be seen as a relative amount of hours/time spent on topics compared to other topics of the week).
On this page under each topic is also included the learning objectives planned as well as relevant material and links which may be of use for writing material and working on exercises related to each topic.

1.00 Creating and debugging Qt projects (P0 | 0,5h)

Objective: Being able to build, debug and run a trivial Qt project

1.01 QString, QStringLiteral, Value Types (P0 | 2h)

Objective: Basic String manipulation

1.02 Item Containers (P2 | 2h)

Objective: Adding, iterating, manipulating data in some containers

1.03 QObject - Subclassing (P0 | 2h)

Objective: Custom QObjects with properties, enums

1.04 Parent-Child relationship (P0 | 0,5h)

Objective: Qt memory management

1.05 Object communicating: Signals & Slots (P0 | 1h)

Objective:

1.06 Object communicating: Queued Connections (P2 | 1h)

Objective: Different to direct connections

1.07 Object communicating: Event Handlers (P1 | 1h)

Objective:

1.08 Object communicating: Custom Events (P2 | 1,5h)

Objective: Synthetic events and event handling

1.09 Smart Pointers - QPointer, QScopedPointer (P1 | 1h)

Objective:

1.10 Shared Pointers (P2 | 2h)

Objective: Inter-Thread memory management

1.11 Streaming (P2 | 2h)

Objective: Meta-Object System, File handling

1.12 Implicitly Shared Custom Type (P2 | 2h)

Objective: Qt value type memory management

Exercise for Part 1 - Directory Browser

Complete the implementation of a trivial directory browser. You are provided with a simple browser QML UI and your task is to complete the implementation. Comment in the lines in the UI, when you add the required functionality. The UI shows a directory name and number of file entries and a list of all entries. If the gird at the top is clicked, the application should sort the files to descending or ascending order, depending on the current order. Clicking on the file will show the files in that folder or open a text editor, if the file is a text file.

  • Derive QObject to implement the requested functionality. Instantiate and expose your object to QML in main.cpp lines 13 and 14.
  • When a program is started, read at least file names and sizes of a directory, e.g. home, into a container. Note that the container must be a string list, so concatenate the name and size to a single string.

The QML UI expects the following API from your QObject sub-class.

  • There must be two properties: dirName of type String and filesInDir of type int. The values should correspond the real values of the current directory.
  • Provide the slot functions to be called from the UI.
  • model() returns the container.
  • fileContent() returns the content of a text file as String.
  • sort() will sort entries in ascending or descending order.
  • entryChanged(QString) is called from the UI. You should check, whether the entry is a directory or a file. In the former case, you should read new entries from the new directory and in the latter case, you should read content of the file and use fileContent() to return the content to the UI.

The UI is heavily based on signals.

  • dirNameChanged() indicates the directory name has changed, i.e. the user has clicked on the directory name on the UI.
  • Similarly, filesInDirChanged() indicates that the filesInDir value has changed.
  • fileContentChanged() is similar, indicating the user has clicked on the file name in the UI and new data has been read from the file.
  • dataChanged() notifies the container content has changed.
  • entryClicked(QString) signal is emitted from the UI. You should handle this by checking the type of the entry and by reading either a directory content to the container or file content to the String, used in the UI.

footy foot foot

Clone this wiki locally