Update SkittleBuilder.java with getMainSkittle()

[leoncvlt]

I want to get the main action button so I can change its color on runtime with setBackgroundTintList(). Thought it was better to have a generic getter rather than a specialized function to change the color like specified in your TODO in case I wanted to do more with it - plus there's the same functionality on the secondary skittles ( getSkittle() )

[ghost]

I will take a look,don't worry about the travis build it completely sucks for android

[ghost]

You can set the color of the main skittle in xml,or use the overloaded constructor

I actually had a generic method to change the color but removed it to reduce the effort (forgot to remove the TODO)

Besides from changing the color, is there any other need to access the main skittle

[ghost]

the getSkittle() one was a nice catch,its actually used only internally why don't you push another commit and make it package local by removing public from that method,this needs to be done in getTextSkittle() in the same class as well

[leoncvlt]

I have several several fragments in my app with different content and accent colors, so I was looking for a way to programatically switch the color of the main skittle according to the content being currently displayed (with the secondary skittles i do getSkittle().setBackgroundTintList() and works great), that's why I was wondering about the functionality for the main one.

I could try re-creating the builder with the new color but it sounds like a bit of a overkill.

[leoncvlt]

The reason I wasn't using setSkittleColor() is that my int color was not defined as a resource in my xml (I think you do context.getResources().getColor() on all the changing colors method, right?), it was generated at runtime thus breaking the function

[ghost]

Hmm fair enough, why don't we create an overloaded generic method to handle all kinds of color resources,dynamic or otherwise in SkittleBuilder ,this is a feature that should be there any ways i guess

I actually want to discourage people from directly accessing the FloatingActionButtons, its somewhat buggy in its present state as we saw in #3 ,plus it has a really weird api it is designed for complete static use,in fact we should make all methods providing access to them package local or private

[leoncvlt]

Fair enough. I just tried with the overloaded construction method and again, doesn't seem to work for my case as I am passing a int color value which is not defined as a resource (the accent color from the fragment currently being displayed)

If you want to keep the fab access private, I'd like to have at least a few functions to customize the fabs such as setColor() which will work with non-resource values

[ghost]

Yeah i guess the api should be flexible enough to provide this functionality, cool i will create a branch to work on this one,pull requests welcome for the same

[ghost]

Check the branch 'colors' for progress,Cheers

[ghost]

Closing this request, raised #5 for the same

[ghost]

@leoncvlt check out be41a24

Highlights

• added a public setMainSkittleColor method to SkittleBuilder
• All instances of passing colors to skittlebuilder now accepts both color resource ID's and generated colors

I will set up a release soon

[ghost]

v1.0.1 with these improvements is out

dependencies{
compile 'com.rlj.library:skittles:1.0.1'
}

comment on #5 if there are still any problems
Cheers