[F/OS] - Dynamic Components Extension (for every component) 2.2.2

example …

You can drag the image unities from the unities part, extension are better, but I would recommend the Kodular image unities.

1 Like

U should use vertical scroll handler extension and first load only 5 items and use a block when bottom reached from vertical scroll handeler and on bottom reach load next 5 items and continue this

i am trying now

Yeah and for images use this guide

1 Like

A component to load images asynchronously.

image

3 Likes

Yes, replace your set.Image Picture blocks with Image Utilities block.

1 Like

:heart: :heart:
i am trying now

2 Likes

correct ?

3 Likes

Yes, if the id is correct.

working it but
loding time 16 Seconds
The user will be annoyed in 5 seconds.
please check
listview (1).apk (6.4 MB)

2 Likes

You have 100 lists, and you have 100 image per list, am I right?
That’s mean you have 10,000 images to load.
This will take so long.
It all depends on your internet

no b…ro…the…r ,
fast list show time in 16 seconds .
and 100 number list show time 30 second

i need,
1 number list show time 5 second,
and 100 number list show time 50 second no problem

Use this technique

3 Likes

:heart: :heart: :heart: :heart:
i am trying

2 Likes

Just made an test app that creates a lot of Button components with a loop and calculates the execution time with Clock.

Test 1

Platform: Companion / Kodular
Measured with: inbuilt Clock component
Created: “Button” component with default properties

Component Count Created in (as seconds) Created in (as milliseconds)
100 0 sec 535 ms
200 1 sec 1387 ms
500 3 secs 3718 ms
1000 6 secs 6992 ms
2000 12 secs 12748 ms
5000 36 secs 36925 ms
10000 73 secs 73849 ms

Test 2

Platform: Exported App / Kodular
Measured with: inbuilt Clock component
Created: “Button” component with default properties

Component Count Created in (as seconds) Created in (as milliseconds)
100 0 sec 593 ms
200 1 sec 1079 ms
500 2 secs 2427 ms
1000 6 secs 6023 ms
2000 12 secs 12009 ms
5000 25 secs 25092 ms
10000 64 secs 64520 ms

Note
Of course, the current running apps, available memory at the moment, device type etc can affect the execution time. It is just an amateur benchmark.

15 Likes

Clock component has a serious delay. So the actual time might be much shorter.

4 Likes