Source link: https://github.com/sweggersen/NonTouchRecyclerView

Deprecated - NonTouchRecyclerView

See TVGrid for the new and improved project

Licence

Copyright 2015 Sam Mathias Weggersen  Licensed under the Apache License, Version 2.0 (the "License");
 you may not use this file except in compliance with the License. You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0  Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.

Source link: https://github.com/sweggersen/NonTouchRecyclerView

Resources

OverlappingImageView

Simple custom ImageView for android giving you a simple way to enable overlapping of two images one over the other.

Image Views

OkHttp-Stats is an android library built on top of OkHttp3, which is responsible for intercepting all the network calls and for calculating network stats such as the average network speed of the user.

This is more of an analytical tool which can be used to track the success and error response logs.

Can be plugged in to any app which uses okhttp in their networking stack.

Networking

ProtoBuffer Demo

Example app to use Protobuf in Android using Square's Wire library.

Protocol Buffer

Ristretto

Espresso's consistency makes it really easy to learn.

Want to match a view with a specific id? Use withId(R.id.some_id). Need to match with a piece of text? Use withText(R.id.some_text) or withText("some text). Awesome, consistent and it's very clear what it is you are doing.

However...

After a few hours writing test code you'll find your code being a little bit too verbose. Not anymore.

Why should you need to explicitly specify that you are matching with some text if you are passing in some text as a parameter? Some for the view id, you can already see that it is a view id.

Ristretto allows you to write the same test code as you already write, but less verbose.

Testing

SpanEZ

Complete abstraction from the Spannable API. Forget about all the boiler plate code and all the Object what nonsense that you have to deal with when working with Spannable.

Eliminate setSpan calls by using all the provided methods trough the StyleEZ interface.
Chain multiple spans with a fluent style
By using both the ContentEZ and StyleEZ interface it removes unnecessary methods from the autocomplete form, and thus it removes clutter.
Allows different ways of adding content (String, String Resource and Formatted String)
By default it does INCLUSIVE_INCLUSIVE to all the spans
After calling any of the inclusive/exclusive methods, all the next methods will be using that flag until apply is called or another flag is used
You can create your own locator by extending the Locator interface