Hi Content is truly useful and informative. Just 1 request as this is regarding dependencies/plugins, Can you create 1 video regarding the build.gradle files (ie App & Project) entailing, What points needs to be consider whilst including dependencies ? Also what is the significance of certain blocks such as repositories, dependencies, plugins, ... at facade level ? Thanks :)
I also face these same issue , then one of my friend told that hilt doc in android document is not updated , then I changed the dependencies as per official hilt documentation .
in theory this looks good but it's just not ready. it slows down builds and it's incompatible with compose bom versioning style (which is supposed to be the standard for compose, and compose is supposed to be the standard for android). not to mention that context actions in android studio aren't consistent: ie you cant easily migrate any dependency from android your build.gradle.kts to your libs.versions.toml file because context actions only work for some dependencies not all. 2/10 would not recommend. I'm currently in the process of migrating back to normal gradle.kts style because my foolish self didn't think to test it out on a demo project
I honestly hate how many sub dirs and how far over and how much space the sidebar/project bar takes. It makes everything look so unclean. So many files, dirs and imports just to get something running. Coming from, Go, Node, Deno, Kotlin/jvm world looks like a hot mess.
Visually speaking, Just use the option to flatten middle packages then. Or just use other ide features to open files cmd e double shift etc. Packages are great and allow scooping of things. And if you are manually writing out packages and imports you are doing things very wrong.
![[DRAGON BALL LEGENDS REVEALS ＆ STUFF] LEGENDS FESTIVAL 2024 Special Edition Part 1](http://i.ytimg.com/vi/mV5bGIswTtQ/mqdefault.jpg)
![[#2024MAMA] G-DRAGON - 무제(Untitled, 2014)+POWER+HOME SWEET HOME+뱅뱅뱅+FANTASTIC BABY | Mnet 241123 방송](http://i.ytimg.com/vi/Ox29z5Nf1Uk/mqdefault.jpg)
Helpful. Thanks Stevdza-San. Need more and more videos.
simply the best !
Been surching exactly this 👌🏾👌🏾👌🏾
Thank you so much for the good explanation
Hi
Content is truly useful and informative.
Just 1 request as this is regarding dependencies/plugins, Can you create 1 video regarding the build.gradle files (ie App & Project) entailing, What points needs to be consider whilst including dependencies ?
Also what is the significance of certain blocks such as repositories, dependencies, plugins, ... at facade level ?
Thanks :)
lol "I'm using forward slash" AS just generated everything for you 😄
so does that means we don't need buildSrc anymore?
Yes
Amazing video Stefan! thank you :)
My pleasure! :)
Thanks for all ur videos are really have a good explanation.
Thanks Man I was hoping for these sort of contents for a long time
Nice video like always. "-"is a hyphen or a dash (I have heard you say forward slash several times.)
thanks a bunch that is a great explanation
how to manage app versions using version catalogue. like app version and min sdk version and all
Is there a plugin in the Android studio to assist in applying plugin and dependency?
Amazing video ❤💥
thanks for this great content ❤ , and the beta version for android suggests u to converting it to file u create
I could not make hilt work, even if used proper dependencies. Maybe make a video on setting up hilt dep injection? Thanks, good video ❤❤
I also face these same issue , then one of my friend told that hilt doc in android document is not updated , then I changed the dependencies as per official hilt documentation .
here is what I get
- Problem: In version catalog libs, you can only call the 'from' method a single time.
Great topics thanks
Can u show how to add hilt/ dagger dependency injection into gradel file
Thank you very much😊
Sir, how to exclude transitive dependency front version catalog file?
I am using android studio latest version. And now its showing warning in toml file for dependecy upgrades. 😀
Sir, nice video like always. Please make one on how to use jvm toolchain in gradle build for Android Studio. Thanks
Excellent.
wish it works with java sdk as well; instead of it hidden behind menu and also in gradle
please make a full android development course
in theory this looks good but it's just not ready. it slows down builds and it's incompatible with compose bom versioning style (which is supposed to be the standard for compose, and compose is supposed to be the standard for android). not to mention that context actions in android studio aren't consistent: ie you cant easily migrate any dependency from android your build.gradle.kts to your libs.versions.toml file because context actions only work for some dependencies not all.
2/10 would not recommend. I'm currently in the process of migrating back to normal gradle.kts style because my foolish self didn't think to test it out on a demo project
Prefer the refreshversions Gradle plugin for this.
Do you like flutter?
thanks
I honestly hate how many sub dirs and how far over and how much space the sidebar/project bar takes. It makes everything look so unclean. So many files, dirs and imports just to get something running. Coming from, Go, Node, Deno, Kotlin/jvm world looks like a hot mess.
Visually speaking, Just use the option to flatten middle packages then. Or just use other ide features to open files cmd e double shift etc.
Packages are great and allow scooping of things.
And if you are manually writing out packages and imports you are doing things very wrong.
Ios compose multi-platform
tnx, What IDE are you using?
android studio...
Android studio giraffe
@@mohamedasraf4175 If it recently came out, it's very good!!
This is the new Android Studio UI.
@@Dibyendu.Mexactly. For those who are interested it can be turned on in settings
please from next video make the outro song longer 😐
gradle -> wrapper -> gradle-wrapper.properites . update to 8.1.1 to remove "@Suppress("DSL_SCOPE_VIOLATION")"