Skip to Content
Last modified by BoYang Xie on 2025/07/09 11:46
From version 55.1
edited by Edwin Chen
on 2024/10/09 10:25
Change comment: There is no comment for this version
To version 119.1
edited by Dilisi S
on 2024/12/22 15:26
Change comment: Uploaded new attachment "squalreline-trial.png", version {1}

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Edwin
1 +XWiki.pradeeka
Content
... ... @@ -1,9 +1,14 @@
1 -
1 +(% style="text-align:center" %)
2 2  [[image:image-20240915231842-1.png]]
3 3  
4 4  
5 +
6 +
7 +
8 +
9 +
5 5  (% _mstvisible="1" %)
6 -(% _msthash="315238" _msttexthash="18964465" _mstvisible="3" %)**Table of Contents：**
11 +(% _msthash="315238" _msttexthash="18964465" _mstvisible="3" %)**Table of Contents:**
7 7  
8 8  {{toc/}}
9 9  
... ... @@ -16,19 +16,20 @@
16 16  
17 17  = 1.  Introduction =
18 18  
19 -== 1.1  What is LTS5 LoRa HMI touch screen ==
24 +== 1.1  What is the LTS5 LoRa HMI Touch Screen? ==
20 20  
21 -LTS5 is a (% style="color:blue" %)LoRa / LoRaWAN HMI Touch Screen(%%) designed for display purpose of IoT project. It have a 5.0" HMI touch screen, and support WiFi, Bluetooch, LoRa wireless protocol.
22 22  
23 -LTS5 is an Open Source software project. The MCU is ESP32 and Dragino LA66 LoRa module. There are lots of development source for ESP32 which can greatly reduce the development time.
27 +The LTS5 is a (% style="color:blue" %)**LoRa / LoRaWAN HMI Touch Screen**(%%) designed for displaying information in IoT projects. It features a **5.0-inch HMI touch screen** and supports **Wi-Fi**, **Bluetooth**, and **LoRa** wireless protocols.
24 24  
25 -The HMI touch screen of LTS5 supports drap & drop design. Developer can use SquareLine to easily customize the display UI for different application.
29 +The LTS5 is an open-source software project powered by an **ESP32 MCU** and a **Dragino LA66 LoRa** module. The extensive development resources available for ESP32 can significantly reduce development time.
26 26  
27 -LTS5 use LA66 LoRa module, this module can be program to support private LoRa protocol or LoRaWAN protocol.
31 +The LTS5's HMI touch screen supports **drag-and-drop** design, allowing developers to use SquareLine to easily customize the display UI for various applications.
28 28  
33 +The LA66 LoRa module can be programmed to support either private LoRa protocols or the LoRaWAN protocol.
29 29  
30 30  == 1.2  Features ==
31 31  
37 +
32 32  * ESP32-WROOM MCU: 8MB RAM & 16MB ROM
33 33  * Dragino LA66 LoRa Module
34 34  * Support Private LoRa protocol or LoRaWAN protocol
... ... @@ -41,8 +41,9 @@
41 41  * 5V DC power
42 42  * IP Rating: IP52
43 43  
44 -== 1.3  Specification ==
50 +== 1.3  Specifications ==
45 45  
52 +
46 46  **LoRa**:
47 47  
48 48  * Frequency Range: 870 MHz ~~ 960 MHz
... ... @@ -76,15 +76,18 @@
76 76  
77 77  == 1.4  Power Consumption ==
78 78  
86 +
79 79  * External 5V DC power adapter
80 80  
81 81  == 1.5  Storage & Operation Temperature ==
82 82  
91 +
83 83  * Operation Temperature: -20 ~~ 70°C  (No Dew)
84 84  * Storage Temperature: -30 ~~ 70°C  (No Dew)
85 85  
86 86  == 1.6  Applications ==
87 87  
97 +
88 88  * Smart Buildings & Home Automation
89 89  * Logistics and Supply Chain Management
90 90  * Smart Metering
... ... @@ -96,14 +96,26 @@
96 96  
97 97  == 2.1  About this demo ==
98 98  
99 -In this Getting Started Example, we will show how to design a simple Display UI and upload it to LTS5. This UI has  a button , when user click the button. The Web UI will jump to a new page.
100 100  
110 +This getting started example demonstrates how to design and deploy a simple display UI for the LTS5 device. The example includes:
111 +
112 +* Creating a basic UI with a single button.
113 +* Implementing functionality to navigate the Web UI to a new page when the button is clicked.
114 +* Uploading the UI to the LTS5 device.
115 +
116 +
117 +By completing this demo, you will gain foundational knowledge for customizing the LTS5 interface and building more advanced IoT applications.
118 +
119 +
101 101  == 2.2  Install Software Running Environment ==
102 102  
103 -The ESP MCU can be developed using ESP-IDF, Arduino, or MicroPython. For this project, we utilize ESP-IDF for compilation and Visual Studio Code (VSCode) for editing.
104 104  
123 +The **ESP MCU** supports development using **ESP-IDF**, **Arduino**, or **MicroPython**. For this project, we use **ESP-IDF** for compilation and **Visual Studio Code (VS Code)** as the development environment.
124 +
125 +
105 105  === 2.2.1 Install VSCode and ESP-IDF extension ===
106 106  
128 +
107 107  Firstly, download and install VSCode for your computer's operating system from the official website: [[Download Visual Studio Code - Mac, Linux, Windows>>url:https://code.visualstudio.com/download]].
108 108  
109 109  Next, you need to install the ESP-IDF extension within VSCode. The detailed operation steps are illustrated in image 1.
... ... @@ -114,17 +114,20 @@
114 114  
115 115  Links for reference: [[Install ESP32 ESP-IDF on Windows and Integrate with VS code (esp32tutorials.com)>>url:https://esp32tutorials.com/install-esp32-esp-idf-windows-integrate-vs-code/#:~~:text=In%20this%20tutorial,%20we%20will%20show%20you%20how%20to%20install]]
116 116  
139 +
117 117  === 2.2.2 Install SquareLine Studio ===
118 118  
142 +
119 119  The version we are utilizing for this software is 1.4.2. You can download it from the official link: [[SquareLine Studio - Download the current version of SquareLine Studio>>url:https://squareline.io/downloads#lastRelease]].
120 120  
121 121  Please note that this software necessitates the registration of a license prior to usage, and various licenses come with distinct limitations. For instance, the free version imposes restrictions such as a limit of 1 component, 150 widgets, and 10 screens. However, for first-time downloads, you are granted unrestricted access for a period of 30 days without the need for immediate registration.
122 122  
147 +
123 123  == 2.3 Simple usage of SquareLine Studio and export UI code ==
124 124  
150 +
125 125  After launching and logging in to this software, create a project as shown in the following image 2. The version of LVGL is 8.3.11.
126 126  
127 -
128 128  [[image:image-20240928103357-2.png||height="680" width="708"]]
129 129  
130 130   image 2 create a SquareLine project
... ... @@ -141,7 +141,7 @@
141 141  
142 142  Now we can start to use this software. Here are some usage information for this software.
143 143  
144 -**1.add widget**
169 +**~1. add widget**
145 145  
146 146  To add a widget, you should click a widget you want to add at the area entitled “Widgets”. In image , demonstrate a add process of label, button, and image 5.
147 147  
... ... @@ -149,7 +149,7 @@
149 149  
150 150   image 5 add widgets
151 151  
152 -**2.modify widget**
177 +**2. modify widget**
153 153  
154 154  The area for modifying widgets is called "Inspector". There are four parts in the "Inspector" tab. We use three of them more frequently, excluding "COMPONENT". The second part is aimed at adjusting the layout, size, position, alignment, flags, and states, etc. of widgets. The name of the second part indicates the type of widget it is representing, and in image 6, it is "BUTTON".
155 155  
... ... @@ -171,7 +171,7 @@
171 171  
172 172   image 8 add event for button
173 173  
174 -**3.change label widget content**
199 +**3. change label widget content**
175 175  
176 176  Modify the content in text as shown in image 9, the text content of label widget will be changed accordingly.
177 177  
... ... @@ -179,7 +179,7 @@
179 179  
180 180   image 9 modify text content of label widget
181 181  
182 -**4.Add image into project**
207 +**4. Add image into project**
183 183  
184 184  To use the image widget, you should first add an image to your project. The image format must be PNG, and its resolution should not exceed 800x480 pixels. There are two ways to add an image file. One way is to move your image into the folder "…/squareline project/assets/", as shown in image 10. The other way is to click the "ADD FILE INTO ASSETS" button, then select an image from your computer to import. After adding, you can see the image in the "assets" area in SquareLine Studio, as demonstrated in image 11.
185 185  
... ... @@ -191,7 +191,7 @@
191 191  
192 192   image 11 use image widget in SquareLine Studio
193 193  
194 -**5.The relationship between widgets**
219 +**5. The relationship between widgets**
195 195  
196 196  There are two common relationships between widgets: one is parallel, the other is parent-child. The parallel relationship means that widgets' relative position is based on a collective object of reference. In parent-child relationship, the parts of the child object that are outside the boundaries of the parent object are not visible by default. Therefore, we need to adjust the position of the child object so that it falls within the range of the parent object, allowing it to be seen as illustrated in image 13.
197 197  
... ... @@ -203,7 +203,7 @@
203 203  
204 204   image 13 move label1 to make label1 widget be a child of button1 widget(2)
205 205  
206 -**6.Preview the final effect**
231 +**6. Preview the final effect**
207 207  
208 208  An advantage of this kind of software is that you can edit the UI with quick previews. In other words, it provides a way of combining graphical programming with simulation immediately.
209 209  
... ... @@ -216,6 +216,7 @@
216 216  
217 217  == 2.4 Integrate UI Code to ESP-IDF Project ==
218 218  
244 +
219 219  To achieve the integrating, we first need to export the UI code, then make some modifications, and finally relocate the UI code to a specific position within the project.
220 220  
221 221  [[image:1727229798126-306.png]]
... ... @@ -246,12 +246,16 @@
246 246  
247 247   image 20 add "ui_init()"
248 248  
275 +
249 249  == 2.5 Brief introduction of hello world project ==
250 250  
278 +
251 251  The project consists of two screens. The first screen displays the company's logo, the project name, and a button to navigate to the next screen. The second screen presents some information about this HMI screen product through an image and includes a button to return to the previous screen.
252 252  
281 +
253 253  == 2.6 Test Result ==
254 254  
284 +
255 255  By pressing the button lying bottom right, the screen can switch to another as expected. This indicates that the UI file has been successfully integrated into the project and is now effective.
256 256  
257 257  [[image:1727488067077-684.png||height="402" width="574"]]
... ... @@ -262,15 +262,253 @@
262 262  
263 263   image 22 screen2
264 264  
295 +
265 265  = 3. Example Project 1: LoRa Central Display =
266 266  
267 267  [[image:image-20240916101737-1.png||height="468" width="683"]]
268 268  
269 269  
270 -
271 271  = 4. Example Project 2: LoRaWAN RS485 Alarm =
272 272  
303 += 5.  The way to add a new panel to project =
273 273  
305 +**~1. Design a panel in SquareLine Studio, using image 5.1 below as a reference.**
306 +
307 +[[image:image-20241121113445-1.png||height="584" width="934"]]
308 +
309 + image 5.1 a panel about water_leak
310 +
311 +**2. Export the ui file.** You need  to adjust the export path first, then click "Export->Export UI Files". This step had been introduced before. Then you can get the ui files as shown in image 5.2.
312 +
313 +[[image:image-20241121141120-4.png||height="383" width="795"]]
314 +
315 + image 5.2 ui files exported
316 +
317 +**3. Delete or rename some file.** Here are the steps:
318 +
319 + Step1 Delete the 'components' directory.
320 + Step2 Delete 'filelist.txt'.
321 + Step3 Delete 'ui_helpers.c' and 'ui_helpers.h'.
322 + Step4 Rename 'ui_ScreenMain.c' in the 'screens' directory to 'ui_water_leak_style.c'.
323 + Step5 Rename the 'screens' directory to 'styles'.
324 +
325 +[[image:image-20241121151934-10.png||height="303" width="792"]]
326 +
327 + image 5.3 rest file (1)
328 +
329 +[[image:image-20241121142925-7.png||height="141" width="793"]]
330 +
331 + image 5.4 rest file (2)
332 +
333 +**4. Open this project in vscode.**
334 +
335 +5. Add file include path about water_leak in extra_lib/CMakeLists.txt as shown in image 5.5, 5.6, and its format is similar to the tem_hum or door.
336 +
337 +[[image:image-20241121181957-17.png||height="438" width="516"]]
338 +
339 + image 5.5 extra_lib/CMakeLists.txt before add
340 +
341 +[[image:image-20241121182239-18.png||height="520" width="518"]]
342 +
343 + image 5.6 extra_lib/CMakeLists.txt after add
344 +
345 +**6. Modify header file include in fonts and images directory.** Open the fonts/ui_font_Font12.c file, as shown in image 5.7, then modify the '#include "../ui.h"' to '#include "../ui_water_leak.h"', the image 5.8 is the modified image. Other font file need to be modified in same way.
346 +
347 +[[image:image-20241121171629-11.png]]
348 +
349 + image 5.7 before-modified font file
350 +
351 +[[image:image-20241121171901-12.png]]
352 +
353 + image 5.8 modified font file
354 +
355 +Open the images/ui_img_battery_empty_png.c file, as shown in image 5.9, then modify the '#include "../ui.h"' to '#include "../ui_water_leak.h"', the image 5.10 is the modified image. Other image file need to be modified in same way.
356 +
357 +[[image:image-20241121172714-13.png]]
358 +
359 + image 5.9 before-modified image file
360 +
361 +[[image:image-20241121172908-14.png]]
362 +
363 + image 5.10 modified image file
364 +
365 +**7. Modify the ui_water_leak/CMakeLists.txt.** Open this file, and modify it from image 5.11 to image 5.12.
366 +
367 +[[image:image-20241121180030-15.png]]
368 +
369 + image 5.11 ui_water_leak/CMakeLists.txt before modification
370 +
371 +[[image:image-20241121180517-16.png]]
372 +
373 + image 5.12 ui_water_leak/CMakeLists.txt after modification
374 +
375 +**8. Modify ui_water_leak.h file.** The image 5.13, 5.14 show the code before modification, and the image 5.15, 5.16 show the code after modification.
376 +
377 +[[image:image-20241122094200-23.png]]
378 +
379 + image 5.13 ui_water_leak.h (1) before modification
380 +
381 +[[image:image-20241122094320-24.png||height="852" width="554"]]
382 +
383 + image 5.14 ui_water_leak.h (2) before modification
384 +
385 +[[image:image-20241122094600-25.png||height="1078" width="554"]]
386 +
387 + image 5.15 ui_water_leak.h (1) after modification
388 +
389 +[[image:image-20241122094719-26.png||height="941" width="583"]]
390 +
391 + image 5.16 ui_water_leak.h (2) before modification
392 +
393 +**9. Modify ui_water_leak.c file.** The image 5.17, 5.18, 5.19 show the code before modification, and the image 5.20, 5.21, 5.22 show the code after modification.
394 +
395 +_ui_flag_modify( ((lv_obj_t *)(e->user_data)), LV_OBJ_FLAG_HIDDEN, _UI_MODIFY_FLAG_TOGGLE);  This code replaces 4 lines of code in ui_water_leak.c, so it is pasted here for convenience.
396 +
397 +[[image:image-20241122102929-27.png||height="619" width="426"]]
398 +
399 + image 5.17 ui_water_leak.c (1) before modification
400 +
401 +[[image:image-20241122112838-30.png||height="551" width="628"]]
402 +
403 + image 5.18 ui_water_leak.c (2) before modification
404 +
405 +[[image:image-20241122110815-29.png||height="725" width="712"]]
406 +
407 + image 5.19 ui_water_leak.c (3) before modification
408 +
409 +[[image:image-20241122113158-31.png||height="872" width="677"]]
410 +
411 + image 5.20 ui_water_leak.c (1) after modification
412 +
413 +[[image:image-20241122113259-33.png||height="874" width="724"]]
414 +
415 + image 5.21 ui_water_leak.c (2) after modification
416 +
417 +[[image:image-20241122113359-34.png||height="804" width="746"]]
418 +
419 + image 5.22 ui_water_leak.c (3) after modification
420 +
421 +**10. Modify ui_water_leak_events.h file.** The image 5.23 show the code before modification, and the image 5.24 show the code after modification.
422 +
423 +[[image:image-20241122134113-35.png||height="380" width="421"]]
424 +
425 + image 5.23 ui_water_leak_events_.h before modification
426 +
427 +[[image:image-20241122134420-37.png||height="201" width="283"]]
428 +
429 +image 5.24 ui_water_leak_events_.h after modification
430 +
431 +**11. Modify ui_water_leak_events.c file.** The image 5.25 show the code before modification, and the image 5.26 show the code after modification.
432 +
433 +Step1. '#include "ui.h"'~-~->'#include "ui_water_leak.h"'
434 +
435 +Step2. add code  below in delete_object() function definition.
436 +
437 + panel_all * panel = find_upper_by_SensorPanel(&arr,((lv_obj_t *)(e->user_data~)~)~);
438 +
439 + size_t index = panel->panel_obj_index;
440 +
441 + deleteElement(&arr, index);
442 +
443 +[[image:image-20241122135023-38.png||height="358" width="372"]]
444 +
445 + image 5.25 ui_water_leak_events_.c before modification
446 +
447 +[[image:image-20241122135258-39.png||height="403" width="559"]]
448 +
449 + image 5.26 ui_water_leak_events_.c after modification
450 +
451 +**12. Modify ui_water_leak_style.c file.**
452 +
453 +Step1. '#include "../ui.h"'~-~->#include '"../ui_water_leak.h"'
454 +
455 + add '#include "../../sort.h"'
456 +
457 + add '#include "ui.h"'
458 +
459 +[[image:image-20241122141536-41.png||height="361" width="612"]]
460 +
461 + image 5.27 ui_water_leak_style.c (1) before modification
462 +
463 +[[image:image-20241122142129-42.png||height="386" width="613"]]
464 +
465 + image 5.28 ui_water_leak_style.c (1) after modification
466 +
467 +Step2. modify 'void ui_ScreenMain_screen_init(void)'~-~->'panel_with_type create_water_leak(uint8_t index)'
468 +
469 + delete code as shown in image 5.29
470 +
471 +[[image:image-20241122145620-44.png||height="757" width="671"]]
472 +
473 + image 5.29 ui_water_leak_style.c (2)
474 +
475 +Step3. The image 5.30, 5.31 show the change.
476 +
477 +[[image:image-20241122152026-45.png||height="277" width="828"]]
478 +
479 + image 5.30 ui_water_leak_style.c (3) before modification
480 +
481 +[[image:image-20241122152542-46.png||height="293" width="830"]]
482 +
483 + image 5.31 ui_water_leak_style.c (3) after modification
484 +
485 +Step4. Copy partly the code in ui_water_leak.c, paste at extra_lib/sort.h(The process is shown in image 5.32, 5.33).
486 +
487 +[[image:image-20241122153958-47.png]]
488 +
489 + image 5.32 ui_water_leak_style.c (4)
490 +
491 +[[image:image-20241122154755-49.png||height="864" width="513"]]
492 +
493 + image 5.33 ui_water_leak_style.c (4)
494 +
495 +Step5. Delete event function in code which was just pasted in extra_lib/sort.h(The process is shown in image 5.34).
496 +
497 +[[image:image-20241122155650-50.png||height="922" width="513"]]
498 +
499 + image 5.34 ui_water_leak_style.c (5)
500 +
501 +Step6. Add some lines of code in extra_lib/sort.h as shown in image 5.35.
502 +
503 +[[image:image-20241122161934-51.png]]
504 +
505 + image 5.35
506 +
507 +Step7. Add a line of code in extra_lib/sort.h as shown in image 5.36.
508 +
509 +[[image:image-20241122162852-53.png||height="330" width="529"]]
510 +
511 + image 5.37
512 +
513 +Step8. Add some code in ui_water_leak_style.c as shown in image 5.38 from line534 to line 576 in detail.
514 +
515 +panel_with_type union_sensor;
516 +
517 +union_sensor.panel_type = WATER_LEAK_TYPE;
518 +
519 +......
520 +
521 +lv_obj_set_x(union_sensor.panel_union.door.ui_PanelSensorDoor, x_by_index(index));
522 +
523 +lv_obj_set_y(union_sensor.panel_union.door.ui_PanelSensorDoor, y_by_index(index));
524 +
525 +return union_sensor;
526 +
527 +[[image:image-20241122171211-54.png||height="635" width="792"]]
528 +
529 + image 5.38
530 +
531 +**13. Modify sort.c file.**
532 +
533 +Add a line of code ~-~-'#include "ui_water_leak.h"' as shown in image 5.39 line 16.
534 +
535 +[[image:image-20241122173718-56.png||height="378" width="579"]]
536 +
537 + image 5.39 sort.c (1)
538 +
539 +There are still some changes need to be done in sort.c, and omit here for the moment.
540 +
541 +
274 274  = 6. FAQ =
275 275  
276 276  == 6.1 ==
... ... @@ -280,11 +280,13 @@
280 280  
281 281  == 7.1  Part Number ==
282 282  
551 +
283 283  Part Number: (% style="color:#4472c4" %)LTS5
284 284  
285 285  
286 286  == 7.2  Packing Info ==
287 287  
557 +
288 288  **Package Includes**:
289 289  
290 290  * LTS5 HMI Touch Screen
... ... @@ -293,11 +293,13 @@
293 293  
294 294  = 8. Support =
295 295  
566 +
296 296  * Support is provided Monday to Friday, from 09:00 to 18:00 GMT+8. Due to different timezones we cannot offer live support. However, your questions will be answered as soon as possible in the before-mentioned schedule.
297 297  * Provide as much information as possible regarding your enquiry (product models, accurately describe your problem and steps to replicate it etc) and send a mail to [[support@dragino.com>>url:file:///D:/市场资料/说明书/LoRa/LT系列/support@dragino.com]].
298 298  
299 299  = 9.  Reference material =
300 300  
572 +
301 301  * Datasheet
302 302  * Source Code
303 303  * Mechinical
image-20241121113445-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +250.0 KB
Content
image-20241121120222-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +44.8 KB
Content
image-20241121120830-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +42.6 KB
Content
image-20241121141120-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +41.7 KB
Content
image-20241121141315-5.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +29.4 KB
Content
image-20241121141329-6.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +29.4 KB
Content
image-20241121142925-7.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +14.8 KB
Content
image-20241121145915-8.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +61.0 KB
Content
image-20241121150911-9.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +73.0 KB
Content
image-20241121151934-10.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +32.9 KB
Content
image-20241121171629-11.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +16.9 KB
Content
image-20241121171901-12.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +17.2 KB
Content
image-20241121172714-13.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +26.4 KB
Content
image-20241121172908-14.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +27.1 KB
Content
image-20241121180030-15.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +27.7 KB
Content
image-20241121180517-16.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +26.5 KB
Content
image-20241121181957-17.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +59.3 KB
Content
image-20241121182239-18.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +71.3 KB
Content
image-20241122092239-19.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +270.9 KB
Content
image-20241122092655-20.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +251.6 KB
Content
image-20241122093445-21.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +128.9 KB
Content
image-20241122093601-22.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +120.0 KB
Content
image-20241122094200-23.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +289.2 KB
Content
image-20241122094320-24.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +182.4 KB
Content
image-20241122094600-25.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +136.0 KB
Content
image-20241122094719-26.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +129.5 KB
Content
image-20241122102929-27.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +219.9 KB
Content
image-20241122104344-28.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +257.1 KB
Content
image-20241122110815-29.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +246.1 KB
Content
image-20241122112838-30.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +263.9 KB
Content
image-20241122113158-31.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +133.7 KB
Content
image-20241122113252-32.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +152.3 KB
Content
image-20241122113259-33.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +152.3 KB
Content
image-20241122113359-34.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +126.5 KB
Content
image-20241122134113-35.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +69.3 KB
Content
image-20241122134412-36.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +14.9 KB
Content
image-20241122134420-37.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +14.9 KB
Content
image-20241122135023-38.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +28.7 KB
Content
image-20241122135258-39.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +40.3 KB
Content
image-20241122141526-40.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +78.8 KB
Content
image-20241122141536-41.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +78.8 KB
Content
image-20241122142129-42.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +85.1 KB
Content
image-20241122143105-43.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +60.2 KB
Content
image-20241122145620-44.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +394.0 KB
Content
image-20241122152026-45.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +201.6 KB
Content
image-20241122152542-46.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +95.3 KB
Content
image-20241122153958-47.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +241.1 KB
Content
image-20241122154745-48.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +135.7 KB
Content
image-20241122154755-49.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +135.7 KB
Content
image-20241122155650-50.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +104.4 KB
Content
image-20241122161934-51.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +230.3 KB
Content
image-20241122162612-52.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +58.7 KB
Content
image-20241122162852-53.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +125.5 KB
Content
image-20241122171211-54.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +173.3 KB
Content
image-20241122173706-55.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +37.6 KB
Content
image-20241122173718-56.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +37.6 KB
Content
squalreline-trial.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +60.4 KB
Content
squareline.io_downloads.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +1.5 MB
Content