nice video.....short and to the point..i am sure if this video is anyone's first video from your channel , they will subscribe for sure...this kind of video what make me check your channel everyday..
I was wondering the same thing. I understand the usefulness of sealed classes, but I don't see the purpose using them here. It'd be simpler to just use an enum class.
Maybe I don't understand something. But why didn’t the designer of jetpack compose assign sizes, for example in percentages or in other units that adjust to screen sizes like in html stuff? Or, for example, there are no breakpoints feature implemented for different screen sizes in which we could completely change the location and size of the elements?
Really good. However I miss why is necessary to have two variables of WindowType: one for width and another one for height. Is there any particular reason?
Question: Previously we used to have dimes.xml file for various screen sizes. But in Compose everyone seems to be using hardcoded values. For example 12.dp or X.dp and Y.sp. How does this will affect different screen sizes?
Here's the link to the doc page regarding the dp values. I didn't see anything about TV screen sizes though developer.android.com/guide/topics/large-screens/support-different-screen-sizes#window_size_classes
Felt some issues with the values oh height and width, I have a samsung M31 phone , in landscape mode it switched from compact to expanded instead of medium, I checked the width in landscape which showed as 859 dp . Which should not be the case. Plz help
I think I am missing something. The rememberWindowInfo Composable is not really remembered in this case right? Does this mean scrolled lists will not retain their scroll position?
My exact thought, don't get the why this works, because initially the class is initialized with the start configuration, and then upon rotating does it create another instance of that class with the changes ?? does a recomposition happen upon screen rotation ??
Nice man! I actually understood this (just learning Jetpack and Kotlin both now) too. Although I'll be interested in clicking an item in the left list and loading a detail composable on the right, as opposed to on a smaller screen clicking a list item and then going to a whole new composable for the detail display. Hopefully that shouldn't be too bad. Have a question on your WindowInfo/WindowType support classes: I've noticed that the return type in your "sealed" class is "ClassName()" with parentheses, but the return type in the "data" class is just "ClassName." This was also true in the Jetpack MVVM Notes app that I followed along to. What's the reason for the difference in those? Very much appreciate your awesome videos on Jetpack.
@@OEThe11 Haven't even gotten close to that point yet. I want to finish the app first, then try supporting bigger screen sizes. But I'm having a hell of a time with it. I know it's old and crapped on, but old Java/Sqlite is so much easier than Jetpack/Room. I'm actually considering starting over, keeping Kotlin/Jetpack, just architecting it a little more simply. I'm only maybe half done with rewriting the app and it's got at least double the files/classes as my old Java app in its final state and is way more complicated.
@@clamum9648 That's very interesting that you say that. I started with SQLite/Room by originally crating apps with Java and XML files. I find Jetpack pretty straightforward. There's a bit of a learning curve, but once you have that down, it makes all the sense in the world. I was wondering about different screen sizes for JC and now have my answer for it lol.
@@OEThe11 Yeah I actually prefer Jetpack but I don't care for Room at all. My database is insanely simple and I've constantly gotten stuck on doing what should be easy. Right now it's having a problem returning a column from a table that's a part of a join. I dunno why there's an issue cause I join to other tables and return those columns fine. That and just my architecture of the app is way over complicated. I tried implementing a Clean Architecture approach, to learn something new and because it may be useful in the future in my professional job, but it's way overkill for this little simple app and just over complicates things. But yeah I like Kotlin and Jetpack in general otherwise. I guess my main complaint is Room. All the tutorials I see are total crap and way too simple to be much use.
@@clamum9648 There's another database option called Realm. It's a NoSQL type of database and has the ability to store info on a cloud that you can use with other devices simultaneously. You should check it out.
Thanks Philipp
Very good solution and clear example! Thanks a lot for the excellent video!
This man is truly the best creator
nice video.....short and to the point..i am sure if this video is anyone's first video from your channel , they will subscribe for sure...this kind of video what make me check your channel everyday..
Is there a reason WindowType is a sealed class instead of an enum?
I was wondering the same thing. I understand the usefulness of sealed classes, but I don't see the purpose using them here. It'd be simpler to just use an enum class.
Maybe I don't understand something. But why didn’t the designer of jetpack compose assign sizes, for example in percentages or in other units that adjust to screen sizes like in html stuff? Or, for example, there are no breakpoints feature implemented for different screen sizes in which we could completely change the location and size of the elements?
Why it called "remember"? It run on every recomposition
Good tutorial. Thanks
Really good. However I miss why is necessary to have two variables of WindowType: one for width and another one for height. Is there any particular reason?
In case you'd like more fine grained control over when it should change
Great Bro. Good luck
I just started learning compose and was about to google this, lol.
Great tutorial 👍
Great video once more.
Very good job, I hope you to show us your keyboard shortcuts in next videos
Question:
Previously we used to have dimes.xml file for various screen sizes. But in Compose everyone seems to be using hardcoded values. For example 12.dp or X.dp and Y.sp.
How does this will affect different screen sizes?
we still use dimens. He is just not using it for some reason
Gracias amigo!!
what about the size of the icons,images and fonts etc ??? with xml we have used sdp lib what now ???
Hi, Please make tutorial to move point/Offset randomly across the canvas continuously without user input. Same like bouncing ball
Hi Phillip, could you do a video on Dagger scopes? Thank you!
Can someone post a link to the doc page where those dp values are present? I need to check on the ones regarding TV. Thanks in advnce!
Here's the link to the doc page regarding the dp values. I didn't see anything about TV screen sizes though
developer.android.com/guide/topics/large-screens/support-different-screen-sizes#window_size_classes
thanks for this
very cool thank you bro
Felt some issues with the values oh height and width, I have a samsung M31 phone , in landscape mode it switched from compact to expanded instead of medium, I checked the width in landscape which showed as 859 dp . Which should not be the case. Plz help
is threre any library that offers bootstrape css like code pattern?
Nice work, do u have it in Java mode by any chance pls, Thank you.?
I think I am missing something. The rememberWindowInfo Composable is not really remembered in this case right? Does this mean scrolled lists will not retain their scroll position?
My exact thought, don't get the why this works, because initially the class is initialized with the start configuration, and then upon rotating does it create another instance of that class with the changes ?? does a recomposition happen upon screen rotation ??
Nice man! I actually understood this (just learning Jetpack and Kotlin both now) too. Although I'll be interested in clicking an item in the left list and loading a detail composable on the right, as opposed to on a smaller screen clicking a list item and then going to a whole new composable for the detail display. Hopefully that shouldn't be too bad.
Have a question on your WindowInfo/WindowType support classes: I've noticed that the return type in your "sealed" class is "ClassName()" with parentheses, but the return type in the "data" class is just "ClassName." This was also true in the Jetpack MVVM Notes app that I followed along to. What's the reason for the difference in those?
Very much appreciate your awesome videos on Jetpack.
I'm literally about to do the same thing. Where you able to do it as of yet?
@@OEThe11 Haven't even gotten close to that point yet. I want to finish the app first, then try supporting bigger screen sizes.
But I'm having a hell of a time with it. I know it's old and crapped on, but old Java/Sqlite is so much easier than Jetpack/Room.
I'm actually considering starting over, keeping Kotlin/Jetpack, just architecting it a little more simply. I'm only maybe half done with rewriting the app and it's got at least double the files/classes as my old Java app in its final state and is way more complicated.
@@clamum9648 That's very interesting that you say that. I started with SQLite/Room by originally crating apps with Java and XML files. I find Jetpack pretty straightforward. There's a bit of a learning curve, but once you have that down, it makes all the sense in the world. I was wondering about different screen sizes for JC and now have my answer for it lol.
@@OEThe11 Yeah I actually prefer Jetpack but I don't care for Room at all. My database is insanely simple and I've constantly gotten stuck on doing what should be easy. Right now it's having a problem returning a column from a table that's a part of a join. I dunno why there's an issue cause I join to other tables and return those columns fine.
That and just my architecture of the app is way over complicated. I tried implementing a Clean Architecture approach, to learn something new and because it may be useful in the future in my professional job, but it's way overkill for this little simple app and just over complicates things.
But yeah I like Kotlin and Jetpack in general otherwise. I guess my main complaint is Room. All the tutorials I see are total crap and way too simple to be much use.
@@clamum9648 There's another database option called Realm. It's a NoSQL type of database and has the ability to store info on a cloud that you can use with other devices simultaneously. You should check it out.
is there any way to make a composable full-screen without changing its state?
I think.If the screen changes, the interface reorganizes, not the state changes.
But we have to divide single list into two separate list
youre the goat.
Haven't seen any video about multi module application. I'm curious about your approach and how you solve communication between modules.
He made a course about that, I highly recommend that one.
what text theme that guy use?
I just fucking love you jajaja literally
Yeah... No Grid Layout in Compose, pretty duplicated code 😒👍
better to have duplicate code over wrong abstraction - Sandi Metz 😊
I'm the first here, I think :)
Hi, Please make tutorial to move point/Offset randomly across the canvas continuously without user input. Same like bouncing ball
Thanks man
Hi, Please make tutorial to move point/Offset randomly across the canvas continuously without user input. Same like bouncing ball
Hi, Please make tutorial to move point/Offset randomly across the canvas continuously without user input. Same like bouncing ball
Hi, Please make tutorial to move point/Offset randomly across the canvas continuously without user input. Same like bouncing ball
Hi, Please make tutorial to move point/Offset randomly across the canvas continuously without user input. Same like bouncing ball
Hi, Please make tutorial to move point/Offset randomly across the canvas continuously without user input. Same like bouncing ball
Hi, Please make tutorial to move point/Offset randomly across the canvas continuously without user input. Same like bouncing ball
Hi, Please make tutorial to move point/Offset randomly across the canvas continuously without user input. Same like bouncing ball