1.0.0-beta12

This release has no breaking public API changes and optimizes the lib source code.

Features

• All alert types accept a close button now. The close buttons will always close the alert if it is clicked (except for dialog-based buttons which are always closing the alert). This button uses the method asDismissible(Button).

Bugfixes

• Fixed potential IndexOutOfBoundsException if the button API was wrongly used.

1.0.0-beta11

This release includes a few breaking changes and optimizes the builder API.

Features

• Changed addVisibilityListener() to setVisibilityListener().
• Changed internal addCloseButton() to setCloseButton().
• Added some methods for closeOthers(), asDismissible() and withAnimations() to include a boolean to determine the state for this method. Like closeOthers() and closeOthers(boolean closeOthers). closeOthers() is using the default value 'true'.
• Removed withoutAnimations(), ignoreLayoutClick() and allowOthers().
• Changed consumeLayoutClick() to dismissByClick().
• Changed listenWith() to setButtonListener().

1.0.0-beta10

This release marks another major release including several bug fixes and new features.

Features

• Added two new close function types to the HitogoController: closeByState and closeByAlert. closeByAlert is using the hashcode to determine the relevant alerts.
• Added new system inside HitogoController that will manage the visibility of alerts. Usually each alert is triggered by a source. Each source has a reason to show this alert. Therefore it makes sense to close the alert if the reason has changed. There are different use cases that one alert has been triggered by multiple sources (like network error). Showing an alert for each network error (if it has the same alert content) is rather inefficient and could annoy the users. Starting with beta10, the system is keeping track of the amount of sources connected to one alert and prevents showing duplicate alerts. The system is also only hiding the alert if no other sources are attached to it. Of course this won't change the behavior that the user could close the alert manually.
• Made addCloseButton protected to avoid misusing the api. addCloseButton is only used internally if the dismissible state requires a close button (for example for view alerts).
• Revamped the hashcode for alerts/buttons. It is now using different parameter from the alert/button to create it's hashcode.
• closeOthers (ViewAlertBuilder) is now default false. This parameter can be changed via allowOthers/closeOthers and is responsible whether to close all alerts of the same AlertType if this alert is in the process in getting visible. The typical expectation is that new alerts won't close already visible alerts (of the same type).
• Button (and close button) has the ability to show html based text.

Bugfixes

• Fixed a crash inside PopupBuilder that would have been caused by the exit transition object not correctly being checked.

1.0.0-beta9.2

This release is another bugfix-only release.

Bugfixes

• Ensured that the controller system blocks new alerts whose tag is already visible by a different alert.

1.0.0-beta9.1

This release is focusing only on some bug fixes.

Bug fixes

• The ViewAlertImpl was missing the fallback functions. The fallback functions are in place if the given container was not found. This is the following order of the different fallback systems: defined container >> default layout container >> default overlay container >> activity content view layer

1.0.0-beta9

This release includes some breaking changes. Due to the type of those breaking changes, this release has been published shortly after beta8.

Features

• Renamed all factory methods (asPopup, asView, asDialog, asButton) to match their new target classes.

1.0.0-beta8

This release includes some major changes to the library to simplify the usage and to add some new features!

Features

• Renamed almost all classes of the library - last time I will do such huge changes, promise! :) The relevant classes which will break (and which you are probably using in most cases):

1. old: HitogoView >> new: ViewAlert
2. old: HitogoDialog >> new: DialogAlert
3. old: HitogoPopup >> new: PopupAlert
4. old: HitogoButton >> new: Button

• Each area has it's own interface now. The interfaces have the goal to simplify the usage of a specific area (like Popup) and to only allow to interact with the relevant methods that are actual usable with this builder/object. On top of that, unit tests should be much easier to create using the interfaces. The actual implementation for each area can be recognized by the "...Impl"-ending (like PopupAlertImpl).
• Expanded the popup builder to include more methods (anchor via tag, elevation, simple popup method, popup animation style, touch listener, gravity)
• Renamed setDimensions to setSize inside PopupAlertBuilder
• Added new parameter key system. This system is based on several abstract classes which are used by the parameter system to save the builder values with the correct keys. This system should only ensure that the communication between the parameter holder class and builder is fluently.
• Renamed controlledBy to setController
• Moved HitogoAnimation to the hitogo.core package

Bugfixes

• All show-methods are using the post-method provide by the android.View to ensure that the alert is only created and shown if the root view has been created and is visible to the user. That means: showDelayed is the time after the root view has been created.

1.0.0-beta7

This release includes several new features. There have been some changes to the public API, so your code will (eventually) break after updating to this version!

Features

• Hitogo supports popups now!
• Revamped the show/close system for alerts resulting into much cleaner handling. The internal system has switched to a FILO stack that will memorize all active alerts of one controller.
• Added new show method, called 'showLater', which will only add the alert to a stack list, but not show the alert itself. This is useful if you want to initialise several alerts, which are connected to a specific order, but only show one at the time. Especially for popups, that implementation should be useful. To show the next alert, simply call the new method 'showNext'. That method will display the next invisible alert inside the stack.
• Renamed withState >> setState for cleaner public API usage.
• You can now set a layout resource for each alert alone without setting it's state. That should be useful if this specific alert is not bound to any state.
• Added shouldOverrideDebugMode to the HitogoController to allow devs to define their own debug mode for alerts. Be careful using that for production builds!

1.0.0-beta6

This release includes some important bug fixes which were caused by the recent versions. Those versions broke some behavior. The next releases will focus on extending the core and fixing more bugs.

Note: beta-5 was a minor bug fix release which I used to test some configurations. You can ignore this update. :)

Bug fixes

• Reverted some changes from the other bug fix releases.

1.0.0-beta4

Another bugfix release.

Bug fixes

• Fixed a bug which caused to show no animations to show when the alert got no specific animation class via builder. The provideDefaultAnimatior inside HitogoController was not correctly setting the animation state.
• Reverted project to java-7 due to several bugs caused by Gradle.