Improve annotation & implement shared element transition

[namkazt]

1, add option closeIfEmpty to annotation @puppet
in some case that using Rigger.addFragment() ( fragment not added in stack ) and show ( without re-init fragment )
when press back button it will close current activity that maybe unwanted action. So set @Puppet(containerViewId = R.id.fragment_container, closeIfEmpty = false) will solve that problem.

require:

public boolean onInterruptBackPressed() {
    return true;
}

in Activity to interrupted back press.

test: implementation 'com.github.namkazt:FragmentRigger:3d8e43637c'

2, implement shared element transaction
Note2: shared element transaction only work with replace for now ( show and hide will add next PR if this go thought )
How to make it work :
1, create shared elements

new SharedElement[]{
        SharedElement.create(mContentView.findViewById(R.id.shared_container)),
        SharedElement.create(mContentView.findViewById(R.id.profile_image)),
};

2, pass it thought replaceFragment method ( new replace method act like startFragment but call replace and addSharedElement)

Rigger.getRigger(this).replaceFragment(fragment, R.id.fragment_container, sharedElements);

Note: on each fragment will need

@Override
    public void onCreate(@Nullable Bundle savedInstanceState) {
        super.onCreate(savedInstanceState);
        if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.LOLLIPOP) {
            setSharedElementEnterTransition(TransitionInflater.from(getContext()).inflateTransition(R.transition.basic_move));
            setSharedElementReturnTransition(TransitionInflater.from(mContext).inflateTransition(android.R.transition.explode));
        }
    }

[JingYeoh]

did you tried bondContainerView = true or stickyStack = true ?

[namkazt]

yes i was but it just not work on my case.
Example: i have main screen with 5 fragments (5 nav menu items) and i using addFragment to add it and this method do not add to stack. so when i create new fragment with startFragment and after finish i close it. it will check onBackPress because my stack = 0 so it close activity

i meant the case when you have like 5 fragments on Map ( will not change on app life cycle ) but 0 on stack and you want to keep it when you add and remove other fragment from stack without trigger close() if stack size = 0

[namkazt]

@JustKiddingBaby check show demo you will see it close application when you press back button that is something maybe user want to avoid

[JingYeoh]

@namkazt OK, i got it , thanks for the PR , i will review in weekend and merge it as soon .

[JingYeoh]

@namkazt please change the target branch to dev

[namkazt]

okey. will fix conflict when have free time.