Skip to content

Releases: ncapdevi/FragNav

3.3.0

Choose a tag to compare

@ncapdevi ncapdevi released this 25 Jun 01:06
dd33783

#208
ADDED: FragNavTransactionOptions.allowReordering(reorder: Boolean)

3.2.0

Choose a tag to compare

@ncapdevi ncapdevi released this 18 Mar 15:43
8abf3ad

#204

  • Trigger transaction listener when restoring tab from bundle #201
  • Update AndroidX dependencies

3.1.0

Choose a tag to compare

@ncapdevi ncapdevi released this 26 Dec 17:13
372414a
  • Ability to clear a stack other than the one you are currently on #172
  • Migrate to AndroidX #161
  • Fix pop animation #176
  • General improvements and tests added

3.0.0

Choose a tag to compare

@ncapdevi ncapdevi released this 19 Nov 18:49
996aecd

Major release.
The library has been transitioned to Kotlin.

The builder has been entirely removed. This allows for creating a Non-Nullable val object of the FragNavController, as the only things required for initializing the controller are the Container (this should never change) and the fragmentManager (ditto). Everything else can be set as pleased and will be correctly initialized using the initialize function. The secondary benefit to this is that if you are using a single Activity, and need to change the tab structure, you can set things on the fly and just call the initialize function when needed.

Please refer to the sample app for suggested best practices, and I will be updating the readme as well as taking feedback over the next couple weeks.

3.0.0-RC

3.0.0-RC Pre-release
Pre-release

Choose a tag to compare

@ncapdevi ncapdevi released this 22 Apr 03:00
07bae82

This is a pre-release in order to get some in field testing. Since this is a major re-write, I want to give a week or two of usage, bug fixing, feedback before going live with a production ready release.

This is a Major point release, meaning it has breaking changes.

The library has been completed transitioned over to Kotlin, but with the intention of having it as easy to use as possible on either Java or Kotlin. That being said, some heavy underlying changes were made in order to optimize things for Kotlin (without making any sacrifices on the Java end)

The builder has been entirely removed. This allows for creating a Non-Nullable val object of the FragNavController, as the only things required for initializing the controller are the Container (this should never change) and the fragmentManager (ditto). Everything else can be set as pleased and will be correctly initialized using the initialize function. The secondary benefit to this is that if you are using a single Activity, and need to change the tab structure, you can set things on the fly and just call the initialize function when needed.

Please refer to the sample app for suggested best practices, and I will be updating the readme as well as taking feedback over the next couple weeks.

2.4.0

Choose a tag to compare

@ncapdevi ncapdevi released this 21 Nov 23:49
ca143e9
  • removed executePendingTransactions from being called after every commit, and instead made the function public and open for the consumer to decide when it is needed
  • added 3 navigation strategies via #98 Thanks @mateherber !

2.3.0

Choose a tag to compare

@ncapdevi ncapdevi released this 16 Nov 17:58
  • Modified how public Fragment getCurrentFrag() works. There were previously situations where a fragment had been transacted, and thus was on the stack, but the function was still returning the previous function. This should no longer be the case.
  • Made void initialize(@TabIndex int index) a public function. This can be useful if you want to clear all the stacks and start over.

2.2.3

Choose a tag to compare

@ncapdevi ncapdevi released this 09 Oct 18:52
  • updated build tools, support libraries
  • reduced dependencies #91

2.2.2

Choose a tag to compare

@ncapdevi ncapdevi released this 19 Sep 03:26
  • Fixed restoring from stateLoss by making sure the defaultTransactionOptions aren't used #88

2.2.1

Choose a tag to compare

@ncapdevi ncapdevi released this 09 Sep 01:01
  • added boolean isStateSaved() function to check if the FragmentManager is in a saved state. This is useful to know before hand so you can decide to allowStateLoss