Maybe a bit out of case, but I see mostly naming convention like `UserListFragment`, `UserDetailsFra...

# android

[Alin B.]

Maybe a bit out of case, but I see mostly naming convention like UserListFragment, UserDetailsFragment, UserListAdapter, UserListViewModel. Now if I have all these open in Android studio I find it a lot harder to find which one is adapter, which is ModelView. Why not go with FragmentUserList, AdapterUserList, ViewModelUserList?

[louiscad]

Then you open another ViewModel, another Adapter, another Fragment, and you have trouble finding which one is which…

[Alin B.]

hmmm... now this is a good point

[Alin B.]

So I guess I'd better go with the way I see in projects, the NameFragment, NameAdapter and so on

[Alin B.]

Thank you for your input.

[Alin B.]

In java I used the package name pojo to store the data classes, for kotlin could it be poko?

[louiscad]

You can also just search a class by typing the PascalCase initials like PC, or PasC to quickly find what you're looking for. I used to code without tabs at all and was quite fine with that.

[louiscad]

What do you call the "package name pojo", and what do you call "to store the data classes"?

[Alin B.]

I will try, thank you. I am figthing to do the switch to kotlin and I want to do things the right way.

In my project structure there is a package mypackage.com.pojo where I store classes like class User, class Product and so on. POJO = Plain old java object

[louiscad]

Oh, I usually call the subpackage model (as long as it's not part of a library, in which case I pick the package name more thoughtfully)

[Alin B.]

Thank you very much for you help and time!

[Alin B.]

I am trying to figure out kotlin, jetpack and MVVM

[louiscad]

@Alin B. Maybe the sample of an Android Library I am migrating to AndroidX can help you: https://github.com/LouisCAD/Splitties/tree/androidx-refactor

[Alin B.]

Wow, that looks like quite a project

[louiscad]

Better understood in your IDE

[Alin B.]

I started to take a look at https://github.com/googlesamples/android-sunflower

[louiscad]

This can serve as a playground projet where you try things

[louiscad]

Android-Sunflower: Good starting point too 👌

[Alin B.]

I did undertand how room works, room entities, the repository and ViewModel but I need to see how to properly continue with ViewModel->Fragment or activity and data binding according to MVVM pattern

[Alin B.]

I believe that I need data binding so the Fragment uses the ViewModel data but probably also get the events from fragment (like onClick) back to ViewModel to handle it there

[louiscad]

You either use ViewModel data from a Fragment/Activity and edit the Views accordingly, or you can use databinding, or you can use a custom class that your Fragment/Activity instantiates

[Alin B.]

I see that DataBinding is recommended as it avoids using findviewbyid and updating manually

[Alin B.]

I'll see how LiveData and Observable gets mixed in VIewModel... these are new concepts for me so I need to digest them very well

[louiscad]

You can see in the project I linked there are other ways of avoiding findViewById(…) 😉

[Alin B.]

Are you using MVVM?

[louiscad]

Sort of, when it makes sense. I avoid having too much logic in Activities, I use ViewModels, top level functions and #coroutines

[Alin B.]

Thank you very much for all your help and links! Time to get to study.