# 280 SDK Screen Design

The **280 ST/QT-SDK** supports two paths for Screen Design:
1. Qt-Creator
1. ST TouchGFX

Both graphical user interface (GUI) design tools are supported by the **280 SDK**, but each requires a specific SDK variant:
1. Qt Creator → 280 Qt-SDK
1. TouchGFX → 280 ST-SDK

Both Graphical User Interface (GUI) Design Tools are supported by the **280 SDK**, though 2 separate 280 SDK version are used, Qt-Creator must be used for the **280 Qt-SDK**, while TouchGFX must use **280 ST-SDK**.

## Available Resources

1. [TouchGFX Tutorial](https://support.touchgfx.com/academy/category/tutorials).
1. [Qt Academy](https://www.qt.io/academy) (focus on Qt for MCU).

## Code Generation and Integration

Both GUI tools auto-generate C/C++ source code from the graphical design. This generated code integrates with:

1. The corresponding Graphics Engine
1. Other components of the 280 SDK


![SDK Screen Configuration](/content/images/SDK_ScreenConfiguration.png)

## Data Binding and Business Logic

To display data on the screen, GUI design tools fetch information directly from the Data Layer, which abstracts the data source.

Key points:

1. Data fetching, formatting, and business logic are implemented either within the GUI tool or in designated sections of the auto-generated C/C++ files.
1. The Data Layer provides Get/Set interfaces for accessing required data.
1. This includes not only data values but also button states and signals for icons or tell-tales.

## Applying GUI Updates
To make GUI design changes effective:

1. Rebuild the SDK project using STM32CubeIDE.
1. Reprogram the target unit with the updated firmware.