Differences

This shows you the differences between two versions of the page.

--- android_learning:headfirst_android_development_notes:chapter_8 [2016/02/21 04:23] – [On Android fragment managers] mithat
+++ android_learning:headfirst_android_development_notes:chapter_8 [2016/02/21 04:24] (current) – [On Android fragment managers] mithat
@@ Line 176: / Line 176: @@
 It's awkward to need two different function names for these two very similar cases, but fine. What I think is really awful is the naming of the functions: ''getFragmentManager()'' implies a general-purpose function and ''getChildFragmentManager'' implies a manager of a child in the present context, but neither of these is case.
-I suspect the reason for this is that the AOSP developers didn't fully think through things when they introduced Fragments, and when they figured out a better architecture, they probably didn't want to break the API (which would have required people to rewrite the code in their apps). But still ...
+I suspect the reason for requiring two different functions is that the AOSP developers didn't fully think through things when they first developed Fragments, and when they figured out a better architecture, they probably didn't want to break the API (which would have required people to rewrite the code in their apps). But still ...
 //rant: off//