There are basically 3 types of screens regardless of the scope of applications, usage areas, and user types. These are; Listing where the registered data is shown, form for new record entry, and display/display screen used for detailed display of recorded content.
There are basically 3 types of screens regardless of the scope of applications, usage areas, and user types. These are; Listing where the registered data is shown, form for new record entry, and display/display screen used for detailed display of recorded content.
These screens are a reference in almost every sense for other screens to be made. For example, when we consider a user list screen, it will be enough to select only the data source and data to be displayed from a very similar, even the same screen. Similar operations are valid for form and display screens.
We start screen design with the Row element. This most basic container element allows new elements to be added to the interface and takes up space horizontally from end to end within its parent structure. The parent element of a row can be a screen or a column element within another row element.
Alignment and padding properties can also be done for the column element, which will affect the elements within it.
For container-based sizing, you can use the panel element.
For the most part, elements can be sized with both padding and width and height.
Properties and styling properties vary based on the selected element. While there are some common areas, it mostly depends on the properties needed for the element's usage.
Before starting the interface design, prepare a sketch of what kind of screen you want to design, even with a pen and paper. This way, the first screen idea that comes to your mind will not fly away while trying new styling options in screen design.
Use the row element nested as needed, you can use the horizontal stack element to add side-by-side or vertically stacked elements. To mention an important point, the panel element can dynamically get the background color or image from the data.
Another important point is the input elements you will add especially on form screens. For example, an email element must be added in the field to receive an e-mail address. In other similar elements, the entries made by the end user are checked and warn the user to enter correct information with verification errors. In the email element, the. and @ characters are checked in the text entered as standard. And the user is prevented from unintentionally entering incorrect information.
To give another example from the same element, if we consider that it is used in a mobile application, the keyboard in the English language is displayed during the input of the email element, regardless of the end user's device or keyboard language selection.
Listing, Form, and Display screens are frequently used in almost every application. It is important to start with one of these screens that is comprehensive. This will allow you to set the size of the screen or elements such as tables and fonts more precisely. By duplicating screens of the same type, you can quickly prepare other screens.
You can group screens according to the main menus they are connected to.
You can edit but not delete all the styles that come by default when you create an application. These styles will especially help you to edit both the elements added to the screens and the new elements to be added.
You should be careful when editing screens with data connections. Even if you delete a numeric input element and then insert a new numeric input in the same column, your application will cause errors because the element IDs do not match. For comprehensive edits, make your edits by duplicating from the relevant screen.
There are basically 3 types of screens regardless of the scope of applications, usage areas, and user types. These are; Listing where the registered data is shown, form for new record entry, and display/display screen used for detailed display of recorded content.
There are basically 3 types of screens regardless of the scope of applications, usage areas, and user types. These are; Listing where the registered data is shown, form for new record entry, and display/display screen used for detailed display of recorded content.
These screens are a reference in almost every sense for other screens to be made. For example, when we consider a user list screen, it will be enough to select only the data source and data to be displayed from a very similar, even the same screen. Similar operations are valid for form and display screens.
We start screen design with the Row element. This most basic container element allows new elements to be added to the interface and takes up space horizontally from end to end within its parent structure. The parent element of a row can be a screen or a column element within another row element.
Alignment and padding properties can also be done for the column element, which will affect the elements within it.
For container-based sizing, you can use the panel element.
For the most part, elements can be sized with both padding and width and height.
Properties and styling properties vary based on the selected element. While there are some common areas, it mostly depends on the properties needed for the element's usage.
Before starting the interface design, prepare a sketch of what kind of screen you want to design, even with a pen and paper. This way, the first screen idea that comes to your mind will not fly away while trying new styling options in screen design.
Use the row element nested as needed, you can use the horizontal stack element to add side-by-side or vertically stacked elements. To mention an important point, the panel element can dynamically get the background color or image from the data.
Another important point is the input elements you will add especially on form screens. For example, an email element must be added in the field to receive an e-mail address. In other similar elements, the entries made by the end user are checked and warn the user to enter correct information with verification errors. In the email element, the. and @ characters are checked in the text entered as standard. And the user is prevented from unintentionally entering incorrect information.
To give another example from the same element, if we consider that it is used in a mobile application, the keyboard in the English language is displayed during the input of the email element, regardless of the end user's device or keyboard language selection.
Listing, Form, and Display screens are frequently used in almost every application. It is important to start with one of these screens that is comprehensive. This will allow you to set the size of the screen or elements such as tables and fonts more precisely. By duplicating screens of the same type, you can quickly prepare other screens.
You can group screens according to the main menus they are connected to.
You can edit but not delete all the styles that come by default when you create an application. These styles will especially help you to edit both the elements added to the screens and the new elements to be added.
You should be careful when editing screens with data connections. Even if you delete a numeric input element and then insert a new numeric input in the same column, your application will cause errors because the element IDs do not match. For comprehensive edits, make your edits by duplicating from the relevant screen.
