Kodular Improvement Suggestions

[asalisbury (Andrew S)]

Guys, kodular is great you have done a great job, if you could consider making some small changes, developers (or people who use it a lot) lives would be much easier.

1. Allow folders in the initial main screen to put projects into them.
2. Take off the type in name before deleting a file (recently added), its very time consuming and not needed.
3. Add folders in backpack, so we can give names to methods/functions and allow it to be smaller and more concise.
4. Allow direct copy and paste of blocks between all screens.
5. Allow renaming of screen1 to any name we choose.
6. Allow renaming of projects.
7. Allow overwriting projects with the same name, this is important when we update them.

Great work, keep it up.

[Diego (Diego Barreiro Pérez)]

@asalisbury

Allow folders in the initial main screen to put projects into them.

@Vishwas?

---

@asalisbury

Take off the type in name before deleting a file (recently added), its very time consuming and not needed.

If you knew the number of users that asked us to recover deleted screens you wouldn’t say so

---

@asalisbury

Add folders in backpack, so we can give names to methods/functions and allow it to be smaller and more concise.

I think that should come from MIT

---

@asalisbury

Allow direct copy and paste of blocks between all screens.

Use the backpack, it’s the same (more or less)

---

@asalisbury

Allow renaming of screen1 to any name we choose.

Why? It’s not needed, it doesn’t have to show Screen1 anywhere
And it cannot be renamed, as it will break lots of things in compiled apps

---

@asalisbury

Allow renaming of projects.

Already possible in Kodular Eagle…

---

@asalisbury

Allow overwriting projects with the same name, this is important when we update them.

To avoid issues, like the ones of accidentally deleting, it won’t be possible
You have to manually delete it and upload again

[asalisbury (Andrew S)]

Thanks my friend.

[Vishwas (Vishwas Adiga)]

Hi @asalisbury

Allow folders in the initial main screen to put projects into them.

I’m not sure if this can be implemented, but we’ll take a look at what can be done.
Thanks for your support!

[asalisbury (Andrew S)]

Thanks for you time. It would be very useful and clean especially when we have many files.

[auranet (Auceli Neto)]

Allow components to be moved up or down just by dragging their name in the component list. Currently this can only be done by dragging objects within the design.

[Point (Tomer)]

Hey, I just wanted to tell you that the latest update was amazing,
And I wanted to help and give you ideas for the following update:
Suggestions for the next update:

1. It is possible to change something for all components - it can help if you want to change the font or the size of the text to all buttons or labels in the application,
2. It is possible to move the components through All components (as in thunkable) - this can help to make the application more comfortable,
3. It is possible to move the drawer of the components in the block editor to 0 - so that it is more convenient and more space to edit the blocks
4. Bug fix if RTL works then all buttons become shorter (look at the picture)

(Even if my device is in English and RTL is active, they will see the problem)
You can check it out for yourself: RTL.aia (1 .1 ק״ב)
RTL.apk (4 .1 מ״ב)
It would have been good if you could turn the RTL off and on From the blocks, but apparently it’s not possible

5. Add a component in control: a component that will allow a certain time to wait until the next operation

[yusufcihan]

Add a component in control: a component that will allow a certain time to wait until the next operation

Why is a wait procedure generally a bad idea?

source by Taifun (Pura Vida Apps)

[alireza66 (علیرضا)]

Also if it was possible to group components it would be great. Like instead of turning ON visibility of 10 buttons separately, you group them all and make blocks for that certain group name.

[Vishwas (Vishwas Adiga)]

You can always use procedures for such actions

Simply create a procedure that takes a parameter which can be true or false.
In the procedure definition, set the visibility of all the components you wish to set to the parameter’s value.

procedure visibilitySetter (x) {
set button1.visible to x
set label1.visible to x
}

You can call it like this:
procedure visibilitySetter(true)

[alireza66 (علیرضا)]

thank you very much. i have no idea how i missed such possibility

[Peter (Moderator)]

The official language of the forum is English. Please translate your post.

[Kleyber_Derick]

I don’t agree when you say that Eagle is heavy and slow… Unless only in your machine, because for me it’s faster than Draco. Anyway, you must understand that every update has some problems and problems exist to be solved. That’s what staff is doing right now.

[asalisbury (Andrew S)]

Dears, there seems to a bug with backpack, ive been using it a lot this week and it has an issue with the zoom, it opens so big that you can read the blocks and i have to zoom to 33% to close it then zoom back to open again then zoom again to see the blocks. It also takes about 10- 30 seconds to open, im assuming depends on demand…on sunday it was 30secs to open after click.

I have a super fast internet and laptop.

Hope this helps

[cashytmofficial (cashytm app)]

Please make a native ads for facebook it has more earning otherthan banner ads. i like kodular for make facebook rewards ads now please give one more surprise