## 4 Results
### PWCT2 Performance  
Table 10 presents performance results related to the PWCT2 environment, showcasing various visual source files and their corresponding metrics. These files represent games and utilities such as StopWatch, Snake, Matching, Sokoban, Escape, Tessera, FlappyBird3000, and others. Each sample is evaluated based on several criteria: file storage in kilobytes (KB), the number of visual components, steps involved, generated lines of code (LOC), loading time (LT) in milliseconds required to display the visual representation, and code generation time (CGT) in milliseconds. The data demonstrate a range of sample complexities, with file storage sizes varying from 41 KB to over 1000 KB, and visual components ranging from 40 to 1269. The number of steps and lines of code also vary significantly, highlighting the diverse nature of these visual source files. Loading and code generation times provide insights into the performance efficiency of PWCT2 across different applications. The measurements are done using a Victus Laptop [13 th Gen Intel(R) Core(TM) i7-13700H, Windows 11, PWCT 2.0]. In Figure 24, we present the relationship between the number of steps and the required storage. The figure is a stacked bar chart comparing the storage (in KB) and steps for various applications or games developed using PWCT2. The x-axis lists the names of the applications/games, while the y-axis represents the values for storage and steps. The blue segments of the bars represent storage, and the orange segments represent the number of steps in the visual source file. \begin{table}
\begin{tabular}{c c c c c c c c} \hline \hline
**ID** & **File** &
\begin{tabular}{c} **Storage** \\ **(KB)** \\ \end{tabular} & **Components** & **Steps** & **LOC** & **LT (ms)** & **CGT (ms)** \\ \hline
1 & StopWatch & 41 & 40 & 74 & 54 & 73 & 3 \\
2 & Snake & 138 & 149 & 234 & 185 & 199 & 9 \\
3 & Matching & 218 & 215 & 330 & 275 & 287 & 13 \\
4 & Sokoban & 217 & 235 & 330 & 269 & 269 & 13 \\
5 & Escape & 250 & 277 & 401 & 329 & 330 & 14 \\
6 & Tessera & 268 & 269 & 418 & 337 & 370 & 17 \\
7 & FlappyBird3000 & 260 & 263 & 429 & 341 & 358 & 17 \\
8 & Pairs & 283 & 287 & 432 & 362 & 374 & 17 \\
9 & Cards & 298 & 305 & 457 & 399 & 363 & 15 \\
10 & SquaresPuzzle & 299 & 327 & 513 & 378 & 429 & 20 \\
11 & StarsFighter & 321 & 329 & 530 & 423 & 449 & 21 \\
12 & KnightTour & 347 & 386 & 549 & 465 & 448 & 21 \\
13 & Tetris & 351 & 402 & 586 & 483 & 459 & 20 \\
14 & Game2048 & 371 & 356 & 588 & 461 & 499 & 22 \\
15 & Othello & 427 & 422 & 653 & 536 & 562 & 25 \\
16 & DiscreteFourierTransform & 787 & 538 & 677 & 603 & 784 & 22 \\
17 & MagicBalls & 438 & 510 & 700 & 602 & 567 & 24 \\
18 & Minesweeper & 449 & 509 & 701 & 611 & 559 & 24 \\
19 & SuperMan & 465 & 480 & 757 & 607 & 622 & 30 \\
20 & Laser & 707 & 825 & 1139 & 955 & 918 & 39 \\
21 & GameOfLife & 773 & 870 & 1253 & 1066 & 1068 & 43 \\
22 & Checkers & 845 & 968 & 1307 & 1128 & 1077 & 43 \\
23 & GoGame & 946 & 1089 & 1453 & 1271 & 1166 & 47 \\
24 & GetQuotesHistory & 1021 & 1269 & 1555 & 1407 & 1228 & 51 \\
25 & Chess & 1012 & 1166 & 1560 & 1340 & 1270 & 52 \\ \hline \hline \end{tabular}
\end{table} 
Table 10: Measuring performance of PWCT2. In Figure 25, we present the relationship between the number of visual components and the generated source code, showing that using visual components increases the abstraction level. In Figure 26, we demonstrate the relationship between both the loading time/code generation time and the step count in the visual source file. We notice from Figure 26 that the loading time increases significantly as the file size and complexity grow, with a noticeable spike around the 600 ms mark, indicating that more complex files require more time to load. The orange line represents the code generation time, which remains relatively low throughout the different samples, with only minor fluctuations. The code generation time is more critical for developers because they may  
Figure 24: The relationship between the number of steps and the required storage.