b82be525b9
This was a bit more complex than all the other views, because it supports rotation, and different views for when it is rotated. The end result is that the way in which the views were constructed needed to be completely redone. In the process, I also moved the layout of the app summary to a Relative Layout. This adds more flexibility, and is also the suggested layout for complex views (as apposed to nested linear layouts). I believe this is due to the performance of relative vs linear layotus. It was aprticularly hard to figure out what was going on when rotating an Activity which had a list fragment that had another fragment as a header. I don't think fragments were designed to work like this, but I believe it is all working as expected now. Conflicts: src/org/fdroid/fdroid/Preferences.java
17 lines
564 B
XML
17 lines
564 B
XML
<?xml version="1.0" encoding="utf-8"?>
|
|
<RelativeLayout
|
|
xmlns:android="http://schemas.android.com/apk/res/android"
|
|
xmlns:tools="http://schemas.android.com/tools"
|
|
android:layout_width="fill_parent"
|
|
android:layout_height="fill_parent"
|
|
android:padding="5dp">
|
|
|
|
<fragment
|
|
android:id="@+id/fragment_app_list"
|
|
android:layout_width="fill_parent"
|
|
android:layout_height="wrap_content"
|
|
android:name="org.fdroid.fdroid.AppDetails$AppDetailsListFragment"
|
|
tools:layout="@android:layout/list_content"/>
|
|
|
|
</RelativeLayout>
|