Organizing components
Last updated
Last updated
In exercise 1 you had to distribute the calculator numbers in columns. To make the design of the calculator clearer, let’s add the distribution of the numbers in a table. I have added a couple of new texts to simplify the later development.
Column 1 | Column 2 | Column 3 |
7 | 8 | 9 |
4 | 5 | 6 |
1 | 2 | 3 |
0 | . | EXP |
This table has three columns. If the numbers are grouped into columns (as requested in the exercise) the result would be the one shown in the next image.
Source code:
Unless you are programming a design calculator, the screen capture is different from the initial table. The columns are correct but they are distributed one underneath the other, not in parallel as they should. To distribute the numbers in a row you have to use the Row layout.
The Row layout works just like a Column element with a difference: the components are distributed in a row. The structure for this layout is as follows:
If the table is defined using only rows, all numbers would be distributed in a single row. To solve this problem we need to separate the table into rows and columns. The rows will contain the numbers horizontally, in four rows in total. The next step is to distribute the four rows in a column.
The source code is similar to the previous case. You just have to change the way in which the components are organized.
In this way the components are distributed as wanted. By separating the definition of rows and columns it is possible to have in one row 3 components and in another row, only one. If all rows in the table have the same number of elements you can use the Grid layout, which simplifies the QML code and gives us more flexibility.
This layout can be used if all rows and columns have the same number of components. The structure that follows is as shown:
The most important parameter is the number of columns. The layout distributes the components automatically using the number of columns as a limit. If you enter an extra component, it automatically adds a row and adds that component in the first column.
When defining a layout you can add a series of parameters that modify its behavior. In this case, only the number of columns is defined. As you can see in the code, it’s not defined how the components are distributed.
The label is a component that allows to display information to the user. The calculator that is being developed must allow the user to enter numbers and the operations to be performed with. To do this you have to use another component: the button.
A button has an associated text that tells the user the function it performs. When the user clicks or taps it, an action is generated that allows to execute an associated code. The button structure is a bit more complex than the label structure. We will learn it gradually.
Based on the code that shows the labels in a grid, we need to make several changes:
Replace the labels with buttons. To do this, it is enough to change the Label text by the object Button.
Modify the anchor of the grid so that it is aligned at the bottom of the screen.
Add two new columns to the table with the buttons shown in the image.
Source code:
At this point, the application is starting to look like a calculator. There are two changes that would greatly improve its appearance though. The first is the colour of the buttons. The calculators have dark buttons and depending on the function, that colour varies. The second change is the size of the buttons. Do not forget that the calculator must work on a real device and normally the user fingers take up more space than the mouse pointer.
Ubuntu Touch has a series of colours defined in its palette. If they are used in the design of the user interface, the application will look integrated into the system. To define the background colour of a button, the colour property is used.
You have to change the background colour of all buttons. The numbers should be dark gray. The operations a light gray and the buttons DEL and AC, reddish color. To complete the exercise you have to change the background color. It doesn’t matter if it doesn’t match the one on the screenshot.
Source code:
The user interface of the calculator can be used on a computer. In a real device the buttons are too small. An important detail is that the interface has to adapt to the characteristics of each device. It is not the same to have a vertical mobile screen than having it horizontal.
For now, we will use a vertical screen in mind to design the app. The buttons have two properties that allow you to define their vertical and horizontal sizes. The text of the button doesn’t automatically adapt to the size of the button so it will have to be adapted too. The button would have the following structure:
Repeat the same structure on all buttons. To make it easier to adjust the size of the buttons, we will define two variables. The variables are defined before the view (Page) and have the following structure:
They are defined with the word 'property' to indicate that are a variable. 'Real' defines a number with decimals. Remember that the dimensions must be expressed in the form of GridUnits.
You need to adjust the size of the text and the dimensions of all buttons on the calculator. The result must be similar to the following:
Source code:
This chapter ends with this example. The next step is to add a label at the top of the screen to show the operations and their result.
Larrea Mikel: revision of the chapter in Spanish.
Cesar Herrera: revision of the English translation.
Joan CiberSheep: revision of the English translation.
