* Made helper test methods static

* Refactoring to hide details of FlexboxLayout creation behind helper methods

This PR fixes the incorrect alignment where:
- justifyContent is set to either or space_between or space_around
- Views whose visibitilies are gone are included in a flex line

Also use the number of item count, which the number of gone items are filtered
where appropriate.

Fixes #162

This PR fixes the case where:
  - layout_width is set to wrap_content for the FlexboxLayout
  - End (or start) margin is set to a child
  - The child which the has the end (start) margin has the largest width in the
    same flex line (or only a single child exists)
  - The child has a positive layout_flexGrow (or layout_flexShrink) attribute set

If these conditions were met, the width of the FlexboxLayout didn't take the bottom
margin on the child into account.

Fixes #154

- AlignItems (or AlignSelf) is set to center
- Margin is set to only one side. E.g. Only right when flexDirection is column

- flex direction is set to row (or row_reverse)
- FlexboxLayout has a TextView (or other views that expand vertically if
  not enough space is left horizontally)
- TextView's layout_width is set to 0dp, layout_height is set to wrap_content and
  layout_flexGrow is set to positive

In the situation above, the initial height of the TextView is calculated
as bigger than the actual height because at first the width is set to 0dp,
so the TextView is trying to expand vertically, but actually the height
needs to be measured again with the expanded width (by setting the
layout_flexGrow attribute)

to simplify the test code.

Remove dummy flex lines from the result of `FlexLayout#getFlexLines`.

Change-Id: Ieb5f9bf3d3f32faf090e91ec9015bd1dc10ba46f

Change-Id: I83c493fc2aea18a2d6f90b2fdac7631c975d35ab

Change-Id: I16f54400a5f690f58cf77bc4819af9868e193efb

Change-Id: I834cf9a233ef7a2807c673a67f360c50069b96c3

is large enough to be judged a line wrapping is required.

Change-Id: I2526d00fe53fccfbab5959a10f33d11dfa5f62fa

Change-Id: Idb5aca9981678da486eef5215f58704123e3fa4e

Fixes #70.
Including changes:
- Update the build tools version.
- Take the parent padding value into account when determining the cross size.

Change-Id: If922c5985ab4113ca45adaefcc973887dbe68169

To judge the line wrapping, the padding value from the parent and the margin
of the child being processed were missing.
This PR adds those values when judging if a new flex line is required.

This fixes the edge case where the child's width is WRAP_CONTENT and some
of the contents along the main axis would be truncated if parent's padding
is added (if this is the case, remeasure the child with accumulated width
taken into account to avoid some of the contents to be truncated).
Because accumulated width is not taken into account in the first
measurement of each child (because FlexboxLayout has the concept of wrapping,
at the first measurement of each child, we want the child to be big as it
wants even if there is not enough left over space)

Change-Id: I949fe6b549b5f7c10255ad5fcf6d05fb9a58eeec

Change-Id: Ie950147e6920a9c5c9abd35baa282da5817f9f3a

Change-Id: I1b1950ba952a6c2ad22bffe426e2a6ebcb84abb6

imposed by the minWidth/minHeight or maxWidth/maxHeight attributes.
The size constraints were checked only the main axis direction.
This PR adds the check for the cross axis direction.

Change-Id: I8463b9d0f59a629c1c0fed2de7dda37fcae2055c

masked by ViewCompat.MEASURED_SIZE_MASK since the view size can't be beyond
that value and otherwise Android Studio warns in the MeasureSpec.makeMeasureSpec
if there is a possibility an argument is passed beyond the value is passed.

Change-Id: I4eb552c57d4f25a2ed3063c2e572385b74539adf

to reduce the frequency of GC.

Change-Id: If96c13d4931d4416eff74cb0c945553e648db49e

Change-Id: I07aaacce206264fb62de59792f6e998fe3abb0ae

Change-Id: I6951cb986e096276255374e5962084353471a2ee

https://github.com/google/flexbox-layout/pull/34

Change-Id: I0fdeff297e66a5310fe692175b0db737f10b12c6

This allows you to specify a minimum size your view is allowed to
shrink to. #1

Where views are removed at the tail of the existing views and in the
middle of the existing views.

middle of the existing views.

(avoid reordering the views in every onMeasure method even if any order
attributres haven't changed from the last measurement)

Instead, this PR changes the behavior to reorder the views if a new view
is added or order attributes of any children has changed from the last
measurement.

Change-Id: Ied25bdbcb0da93a96445e4225eac7fee6b93cff9