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

[mihacker41 (mi hacker)]

@Zia_Choudhary

And its very odd to load 100 lists at once
Please load list items one by one… Or 5 by 5 instead of loading all the items at once

example …

[WatermelonIce (Bryan)]

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

[themaayur (Mayur Berad)]

@mihacker41

example

Load items as user Scrolls

[image] RaspyMagentaQuokka (1).aia (372.3 KB) Or the Youtube Listview Refer

[Zia_Choudhary (Zia Ur Rahman)]

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

[mihacker41 (mi hacker)]

@Zia_Choudhary

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

[Zia_Choudhary (Zia Ur Rahman)]

Yeah and for images use this guide

5 Different Listviews using Dynamic component Extension | Guide

So Welcome, Everyone today in this guide I will show how to make different listviews using @yusufcihan 's Dynamic Component Extension. It is fully Customisable According to your needs. So Let’s Begin 1. Simple ListView (Icon, Title & Action Button) • Layout [image] • Inputs [image] Icon : Url Title : String Material_Icon_Name : String For Material Icon Name Click Here • Blocks [blocks] • Schema { "name": "Simple ListView", "metadata-version": 1, "author": "Maayur (rewritten by…

[yusufcihan]

@mihacker41

What is that?

A component to load images asynchronously.

[mihacker41 (mi hacker)]

[mihacker41 (mi hacker)]

@yusufcihan

A component to load images asynchronously.

[yusufcihan]

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

[mihacker41 (mi hacker)]

@yusufcihan

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

i am trying now

[mihacker41 (mi hacker)]

@yusufcihan

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

correct ?

[WatermelonIce (Bryan)]

Yes, if the id is correct.

[mihacker41 (mi hacker)]

@yusufcihan

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

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

[WatermelonIce (Bryan)]

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

[mihacker41 (mi hacker)]

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

[WatermelonIce (Bryan)]

Use this technique

How to use clock to load items in a listview/custom listview?

From last 2 months, I have been trying to achieve it and finally I got it right. It is very useful if you have huge data in your list. Well, I am making this guide because I feel many Koders are still stuck in between the process of achieving it. Extensions and components I used: i) Dynamic Components by @yusufcihan ii) Vertical Scroll Handler by ColinTree iii) Clock component(built in) How to do it: i) Initialize the blocks: You have to initialize five variables, i.e. fi…

[mihacker41 (mi hacker)]

@WatermelonIce

Use this technique

i am trying

[yusufcihan]

@mihacker41

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

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.

[WatermelonIce (Bryan)]

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