Why does Android’s Bundle API accept ArrayLists rather than Lists
I’m new to Android and while going through a tutorial on saving Activity
state to a Bundle, I noticed that instead of accepting the more generic List
interface, Bundle
‘s put methods are expecting ArrayLists
.
Why does Android’s Bundle API accept ArrayLists rather than Lists
I’m new to Android and while going through a tutorial on saving Activity
state to a Bundle, I noticed that instead of accepting the more generic List
interface, Bundle
‘s put methods are expecting ArrayLists
.
Why does Android’s Bundle API accept ArrayLists rather than Lists
I’m new to Android and while going through a tutorial on saving Activity
state to a Bundle, I noticed that instead of accepting the more generic List
interface, Bundle
‘s put methods are expecting ArrayLists
.
Why does Android’s Bundle API accept ArrayLists rather than Lists
I’m new to Android and while going through a tutorial on saving Activity
state to a Bundle, I noticed that instead of accepting the more generic List
interface, Bundle
‘s put methods are expecting ArrayLists
.
Why does Android’s Bundle API accept ArrayLists rather than Lists
I’m new to Android and while going through a tutorial on saving Activity
state to a Bundle, I noticed that instead of accepting the more generic List
interface, Bundle
‘s put methods are expecting ArrayLists
.
Can you help me understand this design pattern made by Java expert?
I inherited the project from a very experienced Java developer. The project is Android app and the guy who coded is is very experienced in coding regular Java apps. He introduced some file structures that I haven’t come across before (I haven’t coded Java apps outside Android area). I can follow the code with no problem and I actually have finished a few add-ons so far, but now I would like to know more of why he used such approach since it may help me myself write a better code. On the other hand, if his approach is not suitable for Android apps, I would like to know that as well so I don’t use such structures.
Can you help me understand this design pattern made by Java expert?
I inherited the project from a very experienced Java developer. The project is Android app and the guy who coded is is very experienced in coding regular Java apps. He introduced some file structures that I haven’t come across before (I haven’t coded Java apps outside Android area). I can follow the code with no problem and I actually have finished a few add-ons so far, but now I would like to know more of why he used such approach since it may help me myself write a better code. On the other hand, if his approach is not suitable for Android apps, I would like to know that as well so I don’t use such structures.
Can you help me understand this design pattern made by Java expert?
I inherited the project from a very experienced Java developer. The project is Android app and the guy who coded is is very experienced in coding regular Java apps. He introduced some file structures that I haven’t come across before (I haven’t coded Java apps outside Android area). I can follow the code with no problem and I actually have finished a few add-ons so far, but now I would like to know more of why he used such approach since it may help me myself write a better code. On the other hand, if his approach is not suitable for Android apps, I would like to know that as well so I don’t use such structures.
Can you help me understand this design pattern made by Java expert?
I inherited the project from a very experienced Java developer. The project is Android app and the guy who coded is is very experienced in coding regular Java apps. He introduced some file structures that I haven’t come across before (I haven’t coded Java apps outside Android area). I can follow the code with no problem and I actually have finished a few add-ons so far, but now I would like to know more of why he used such approach since it may help me myself write a better code. On the other hand, if his approach is not suitable for Android apps, I would like to know that as well so I don’t use such structures.
Can you help me understand this design pattern made by Java expert?
I inherited the project from a very experienced Java developer. The project is Android app and the guy who coded is is very experienced in coding regular Java apps. He introduced some file structures that I haven’t come across before (I haven’t coded Java apps outside Android area). I can follow the code with no problem and I actually have finished a few add-ons so far, but now I would like to know more of why he used such approach since it may help me myself write a better code. On the other hand, if his approach is not suitable for Android apps, I would like to know that as well so I don’t use such structures.