Add fragments instead of replacing them about cicerone

[java1developer]

fragmentTransaction.add() example: show progress as transparent fragment

[terrakok]

https://github.com/terrakok/Cicerone/releases/tag/v5.1.0

[inwady]

I need to use library which requires #add instead of #replace. I added crutches to change logic for fragmentTransaction.add() because things such as checkAndStartActivity, localStackCopy are private.

[terrakok]

Hi! Thanks for proposal)
Cicerone is pragmatic library. Replace fragment is more frequently operation than add. I don't wont that library contains much solutions for all cases.
But navigator API is easy for extends)

What do you think?

[azurh]

@terrakok

Thanks for your response.

The navigator API is indeed easy to extend (like setupFragmentTransactionAnimation()), but unfortunately not in terms of altering the FragmentTransaction parameters like choosing between replace or add, except making local copies of SupportFragmentNavigator and SupportAppNavigator, which I have done, but it's a hacky solution IMHO.

I would be happy to issue a PR which will tackle this feature, but I understand that you don't want to bloat the simplicity of Cicerone.

Do you have an advice on how to persist the fragment UI and data, in a way that the Fragment instance would't be cleared (and the data wouldn't be downloaded again) — when going back, while still using FragmentTransaction#replace()?

[terrakok]

When you replaced fragment, it didn't destroyed , only views were cleared . FragmentManager saved fragment instance

[terrakok]

Progress is not screen for navigation chain! 😱

[terrakok]

#101