Please enable JavaScript.

Coggle requires JavaScript to display documents.

FRAGMENTS (each fragment (lifetime (begins when it’s bound to its parent…

- - - - onCreate(Bundle): to do initial creation of the fragment
      - onStart():makes the fragment visible to the user
      - onPause: fragment is no longer interacting with the user
      - onStop:no longer visible to the user
      - onAttach(Activity) : called once the fragment is associated with its activity. Gets a reference to the Activity object which can be used as Context.
      - onCreateView(LayoutInflater, ViewGroup, Bundle): creates and returns the view hierarchy associated with the fragment
      - onActivityCreated(Bundle): tells the fragment that its activity has completed its own Activity.onCreate. Use this method to access/modify UI elements.
      - onResume(): makes the fragment interacting with the user
      - onDestroyView: no longer accessible. allows the fragment to clean up resources associated with its View.
      - onDestroy:fragment is not used. to do final cleanup of the fragment's state.==> it still exists as a java object attached to the Activity
      - onDettach: Fragment is not tied to the Activity and does not have a View hierarchy. called immediately prior to the fragment no longer being associated with its activity.
      - onSaveInstanceState() : to save information inside a Bundle object. used when a Fragment is paused or stopped.
- - - - 1- create a new Fragment Class that extent Fragment class
      - 2- create Another XML layout file for the fragment
      - method
        
        getFragmentManager(): maintains references to all fragments inside the Activity
        
        findFragmentById(): get reference to a particular Fragment using ID
        
        findFragmentByTag(): get reference to a particular Fragment using tag
        
        FragmentTransactions: Changes to the UI in terms of adding,
        Removing and replacing Fragments
        
        FragmentManager
        
        1- create FragmentManager object hold getFragmentManager();
        
        2-create FragmentTransaction obj to begin the transaction of the previous manager using beginTransaction()
        
        3- use fragment trasaction object to add (need to know instance and the container) tag is optional
        
        4- commit(); the transaction (This points to the Activity ViewGroupin which the fragment should be placed, specified by resource ID)
        
        3- For remove(fragmentObject): need to know reference using findFragmentById or findFragmentByTag then pass the fragment instance to the remove
        
        3- replace
        
        1: Create new fragment and create FragementTransactionfrom Manager
        
        2: Replace need to know container ID containing the Fragment to be replaced and the Fragment with which to replace and then add the transaction to the back stack (so can navigate back)
        
        3: Commit the transaction
        
        addToBackStack()
        
        If you do not call it Fragment is destroyed and it is not possible to navigate back.
        
        if you do call it Fragment is stopped and it is possible to resume it when the user navigates back..
        
        popBackStack(): simulate a Back from the user.
        
        ID vs Tag
        
        ID
        
        with acticity
        
        you have added your Fragment to the Activity layout in XML, you can use the Fragment’s resource identifier
        
        with transaction
        
        should specify the resource identifier of the container View to which you added the Fragment you want to find
        
        Tag
        
        with transaction
        
        search for the Fragment using the tag you specified in the Fragment Transaction
      - 3- set the layout xml file to fragment
      - 4- add layout that will host the fragment
      - 5- write the code to add fragment to the Activity in the Activity
        
        FragmentManager
        
        FragmentTransaction
        
        Transaction is: set of changes to the Activity
        
        can be saved to allow a user to navigate backward by clicks on the “Back”button.
        
        steps
        
        ACQUIRE : an instance of the FRAGMENT MANAGER
        
        CREATE: new Fragment and Transaction
        
        SAVE to backStackand COMMITلازم يطبق الكوميت ولا ماراح يبدا لترانزاكشن
        
        Activity Stack: the logical stacking of Activities that are no longer visible —which allow users to navigate back to previous screens using the back button