Explore >> Select a destination
|
You are here 
|
jonathanbayless.com | ||
| | | | |
ryanharter.com
|
|
| | | | | I've been using ant to build my Android projects for as long as I can remember. There are many reasons for this, like build consistency and workstation agnosticism, but you can read this article if you want to check that out. Ant is a good tool, but never offered the flexibility that I would have liked in a project. That's where Gradle steps in. After seeing all of the power of the new Gradle build system, I knew I had to convert Hashnote to Gradle. | |
| | | | |
inthecheesefactory.com
|
|
| | | | | Android Studio 1.3's stageis closed to the stable release. Newfeatures are keep coming including full NDK support. And it seems like some major change isalsobeing waited for it | |
| | | | |
wittchen.io
|
|
| | | | | Introduction Some time ago, Ive written an article about Test coverage report for Android application. It got some interest (many comments below article and many visits according to Google Analytics), so I decided to refresh this topic. Previously, Ive written instrumentation unit tests, which needed to be executed on a real device or an emulator. Its a good approach when you want to test functionalities strongly connected with the device. E. | |
| | | | |
wittchen.io
|
|
| | | When we work with Activities in Android, defining different layouts for different screen orientations is easy. The only thing we need to do, is to create two *.xml files with the same name for layouts in two separate directories (res/layout/ and res/layout-land/). In Fragments its not that easy. In such case, we need to perform additional operations in order to achieve our goal. Fragment in Android is not re-inflated on configuration change, but we can recreate layout and repopulate view manually. | ||
