1.0.0-beta17.3

This release includes several minor changes.

Features

• All builder methods have new annotations (like @IntRange or @StyleRes) to simplify their usage.

Bug fixes

• Fixed a bug in the closing implementation which was introduced in beta17 due to the LIFO (instead FILO) list.

1.0.0-beta17

This release includes several major internal changes which should simplify the usage and the ability to extend it's implementation.

Features

• All builder have a interface now. Each interface is representing all possible methods that can be used in the public API. This should prevent misusing methods and simplify the readability.
• Removed onCheck(HitogoController, ButtonParams) and onCreate(HitogoController, ButtonParams) from the Button lifecycle. Those methods should not be needed. onCheck(ButtonParams) and onCreate(ButtonParams) is still available to use.
• The ViewAlert fallback solution is using the activity root view to determine if it includes possible alert container if the fragment container are not accessible.

Bug fixes

• The ViewAlert fallback solution was using the wrong default layout container id.

1.0.0-beta16

This release includes several changes within the internal systems and some minor changes to the public API.

Features

• Simplified usage of HitogoParamsHolder object within the internal systems. Each new builder should override onProvideData. This is not required anymore, but needed if the builder's values should be send to the requested alert.
• Changed the logic behind the showNext implementation, especially the part for the priority. Goal was to reduce possible performance issues due to the implementation.
• Removed some methods from the AlertBuilder which could confuse debugging public API usage. The effected methods are closeOthers() and dismissByLayoutClick()
• Removed onCheck(HitogoController, AlertParams) from the alert lifecycle.
• Added more javadoc to different methods.

Bugfixes

• Using the showNext() would show the newest invisible alert instead of the oldest invisible alert. Due to this fix the internal alert list has been changed to a LIFO-based list.

1.0.0-beta15.1

This release contains several breaking API changes and a few bug fixes.

Features

• Alerts can have a priority. The lower the priority value, the higher it's importance to the system. A new alert which is about to be displayed to the system, is closing the alert which has a lower importance to the system (higher priority value). The new alert will only be displayed if no other alert with the same or lower priority have been found. You can use setPriority(int) to make use of this new feature. If closing a prioritized alert, you can use showNext() (HitogoController) to display the next "important" alert.
• The onClick listener includes two new parameter which will break your code. These two new parameter are Alert and Object. Alert is the current alert object which used this button listener. Object is the optional parameter which can be attached to the button listener using setButtonListener(ButtonListener, T) or setButtonListener(ButtonListener, T, boolean) . T stands for the type of your optional parameter. The onClick will use the same T for it's implementation. If no value given, it will use Object.
• Several methods and fields have changed their visibility and declaration to simplify unit testing and the possibility to extend the library with your own classes.
• showNext inside the HitogoController is requiring a Alert object instead of AlertType.
• Added several provider methods to the HitogoParamsHolder.
• Start working on javadoc documentation.

Bugfixes

• showNext (HitogoController): Was trying to show already visible alerts.
• Closing the underlying activity or fragment was resulting in closing all types of alerts. This has been changed to only close dialogs to prevent context leaking.

1.0.0-beta14

This is a minor release which includes some public API changes and code optimizations.

Features

• Changed setVisibilityListener to addVisibilityListener to allow multiple observer for one alert.
• Tweaking source code to allow Units Tests. (More changes will be done in the future to include prepared mocks for each and every class and it's dependencies.)

1.0.0-beta13.1

This is another minor releases including one new feature.

Features

• Methods which are requiring strings (like title or text) can use string resources.

1.0.0-beta12.9

This is another minor release including several optimizations.

Features

• The VisibilityListener can be extended by include a generics, like ViewAlert. This should make the usage much easier for the different methods, like onShow.

Example:

alertBuilder.setVisibilityListener(new VisibilityListener<ViewAlert>() {
@Override
public void onShow(ViewAlert object) {
    Log.i(Activity.class.getName(), "Showing Alert");
}

1.0.0-beta12.8

This is a bugfix release including some code optimizations.

Bugfixes

• Fixed potential NPE if button api (for dialogs) is wrongly used

1.0.0-beta12.2_beta12.7

This release includes several smaller bug fix releases.

Features

• HitogoController has the method provideIsDebugState to determine the debug state for lib exceptions.
• Removed forViewAction() >> without parameter.
• Added forCloseAction to the ButtonBuilder which can be used for buttons which are closing the alert.

Bugfixes

• Added missing HTML converter for dialog elements.
• Fixed button not visible if the click view is null.
• Fixed asDimissable for dialog.
• Fixed potential crash if state provider is returning null.

1.0.0-beta12.1

This is a bugfix release including some code optimizations.

Behavior changes

• Clicking buttons using the ButtonListener is now resulting in closing the alert (default behavior). Before that, the alert would still be visible after clicking. Usual expectation is that the user has interacted with the alert and therefore it (the alert) has fulfilled it's duty (informing the user)

Bugfixes

• Fixed a potential class cast exception for button class