Explore >> Select a destination
|
You are here 
|
blog.iamsuleiman.com | ||
| | | | |
ryanharter.com
|
|
| | | | | In the last post we created a basic Android project using Android Studio templates. While it's great that we have a fully functioning master/detail style app, it does look a bit bare. In this post, we'll change this by styling our list view, incorporating (sort of) real data to feed our list. We'll make a custom adapter to drive our list with custom layouts, and introduce testing into the mix to ensure that our app continues to perform as expected. | |
| | | | |
android-developers.googleblog.com
|
|
| | | | | News and insights on the Android platform, developer tools, and events. | |
| | | | |
wiresareobsolete.com
|
|
| | | | | Note: ConstraintLayout and the layout editor tools are currently in preview. The information in this post is based on the code and behavior of constraint-layout:1.0.0-alpha4. These behaviors may change as the tools approach final release. Google I/O 2016 came with an announcement of new tools and libraries designed to improve the layout experience building Android applications. Android Studio has been equipped with a constraint-based visual layout editor, coupled with the new ConstraintLayout container to interpret those constraints at runtime. | |
| | | | |
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. | ||
