Coordinating activities

When one activity starts another, they both experience lifecycle transitions. The first activity pauses and stops (though, it won't stop if it's still visible in the background), while the other activity is created. In case these activities share data saved to disc or elsewhere, it's important to understand that the first activity is not completely stopped before the second one is created. Rather, the process of starting the second one overlaps with the process of stopping the first one.

The order of lifecycle callbacks is well defined, particularly when the two activities are in the same process and one is starting the other. Here's the order of operations that occur when Activity A starts Acivity B:

1. Activity A's onPause() method executes.
2. Activity B's onCreate(), onStart(), and onResume() methods execute in sequence. (Activity B now has user focus.)
3. Then, if Activity A is no longer visible on screen, its onStop() method executes.

This predictable sequence of lifecycle callbacks allows you to manage the transition of information from one activity to another. For example, if you must write to a database when the first activity stops so that the following activity can read it, then you should write to the database during onPause() instead of duringonStop().

Kishthi ki vyatha

Toofan me kaha dum tha Kishthi duboye ... wo tho kinare ko manjoor na tha... tho kya hua Kishthi naa dubi .. use kinara bhi tho naa nasib hua...

Tough fight

Every passing day.. I am breaking... still I will give a tough fight doesn't matter if I end up at loosing side. .

The day...

24th August was the day.....  hmmmm

GitHub Setup

Welcome to Git (version 1.7.10-preview20120409)


Run 'git help git' to display the help index.
Run 'git help <command>' to display help for specific commands.

Rishi@RISHI-PC /D/GitHub_SRC (master)
$ git init
Reinitialized existing Git repository in d:/GitHub_SRC/.git/

Rishi@RISHI-PC /D/GitHub_SRC (master)
$ git config --global user.name "amriteshmadhur"

Rishi@RISHI-PC /D/GitHub_SRC (master)
$ git config --global user.email "amritesh_m@xyz.com"

Rishi@RISHI-PC /D/GitHub_SRC (master)
$ git clone https://github.com/XYZ/ XYZ _AndroidAgent.git
Cloning into ' XYZ _AndroidAgent'...
Username for 'https://github.com':
Password for 'https://amriteshmadhur@github.com':
remote: Counting objects: 742, done.
remote: Compressing objects: 100% (515/515), done.
remote: Total 742 (delta 422), reused 414 (delta 96)Receiving objects:  98% (728
R
Receiving objects: 100% (742/742), 1017.70 KiB | 195 KiB/s, done.
Resolving deltas: 100% (422/422), done.


Rishi@RISHI-PC /D/GitHub_SRC (master)
$ git branch

Rishi@RISHI-PC /D/GitHub_SRC (master)
$ git branch -a

Rishi@RISHI-PC /D/GitHub_SRC (master)
$ git branch PBM-New-AndroidAgent
fatal: Not a valid object name: 'master'.

Rishi@RISHI-PC /D/GitHub_SRC (master)
$ cd PBM_AndroidAgent/

Rishi@RISHI-PC /D/GitHub_SRC/PBM_AndroidAgent (master)
$ git branch
* master


Rishi@RISHI-PC /D/GitHub_SRC/PBM_AndroidAgent (master)
$ git fetch
Username for 'https://github.com':
Password for 'https://amriteshmadhur@github.com':

Rishi@RISHI-PC /D/GitHub_SRC/PBM_AndroidAgent (master)
$ git che
checkout      cherry        cherry-pick

Rishi@RISHI-PC /D/GitHub_SRC/PBM_AndroidAgent (master)
$ git checkout --track -b PBM-New-AndroidAgent origin/PBM-
origin/PBM-Android-TestAgent   origin/PBM-New-AndroidAgent

Rishi@RISHI-PC /D/GitHub_SRC/PBM_AndroidAgent (master)
$ git checkout --track -b PBM-New-AndroidAgent origin/PBM-New-AndroidAgent
Branch PBM-New-AndroidAgent set up to track remote branch PBM-New-AndroidAgent f
rom origin.
Switched to a new branch 'PBM-New-AndroidAgent'

Rishi@RISHI-PC /D/GitHub_SRC/PBM_AndroidAgent (PBM-New-AndroidAgent)
$ git clone
You must specify a repository to clone.

usage: git clone [options] [--] <repo> [<dir>]

    -v, --verbose         be more verbose
    -q, --quiet           be more quiet
    --progress            force progress reporting
    -n, --no-checkout     don't create a checkout
    --bare                create a bare repository
    --mirror              create a mirror repository (implies bare)
    -l, --local           to clone from a local repository
    --no-hardlinks        don't use local hardlinks, always copy
    -s, --shared          setup as shared repository
    --recursive           initialize submodules in the clone
    --recurse-submodules  initialize submodules in the clone
    --template <template-directory>
                          directory from which templates will be used
    --reference <repo>    reference repository
    -o, --origin <name>   use <name> instead of 'origin' to track upstream
    -b, --branch <branch>
                          checkout <branch> instead of the remote's HEAD
    -u, --upload-pack <path>
                          path to git-upload-pack on the remote
    --depth <depth>       create a shallow clone of that depth
    --single-branch       clone only one branch, HEAD or --branch
    --separate-git-dir <gitdir>
                          separate git dir from working tree
    -c, --config <key=value>
                          set config inside the new repository


Rishi@RISHI-PC /D/GitHub_SRC/PBM_AndroidAgent (PBM-New-AndroidAgent)
$ git branch
* PBM-New-AndroidAgent
  master

Rishi@RISHI-PC /D/GitHub_SRC/PBM_AndroidAgent (PBM-New-AndroidAgent)
$ git pull
Username for 'https://github.com':
Password for 'https://amriteshmadhur@github.com':
Already up-to-date.

Rishi@RISHI-PC /D/GitHub_SRC/PBM_AndroidAgent (PBM-New-AndroidAgent)
$

Word ends where truth begins ....
The purpose of words is to create silence.

Journey

Journey which started two years back has now taken a shape..... I m lovin it.
I don know who is guiding me but I thanks to almighty and him for showing me the path..
just waiting for the next stage how it would be ....

Om Namah Shivay