BobStore/F-Droid/res/values/ids.xml

<?xml version="1.0" encoding="utf-8"?>
<resources>
  <item type="id" name="categorySpinner" />
  <item type="id" name="appDetailsSummaryHeader" />
</resources>
Gives category Spinner an ID Without an ID, the default save/restore state mechanism doesn't work, so (for example) if you rotate the screen on ICS, the current category switches back to the default. 2012-09-16 10:08:30 +01:00			`<?xml version="1.0" encoding="utf-8"?>`
			`<resources>`
			`<item type="id" name="categorySpinner" />`
Rotation of app details with fragments implemented. 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 2014-06-03 08:26:14 +09:30			`<item type="id" name="appDetailsSummaryHeader" />`
Gives category Spinner an ID Without an ID, the default save/restore state mechanism doesn't work, so (for example) if you rotate the screen on ICS, the current category switches back to the default. 2012-09-16 10:08:30 +01:00			`</resources>`