BobStore/res/values/colors.xml

<?xml version="1.0" encoding="utf-8"?>
<resources>
    <color name="signed">#ffcccccc</color>
    <color name="unsigned">#ffCC0000</color>
    <color name="unverified">#ff999999</color>
</resources>
WIP: implementing context and action bar menus for repo management. SwitchCompat will return a Switch or a ToggleButton depending on the platform (doesn't matter, both are CompoundButtons) and this will be added to the repo_item view programatically. I'm using some pretty specific listeners to communicate between the details fragment and the repo list activity. I've also split the functionality (e.g. for deleting) between the repo list and the details view. In the future, when we have content providers for repos, it will be easier to take care of everything from the details screen, and automatically notify the repo list of changes. Refactored update service. Now has a static update method that can be called which will setup the required intent to begin the update. It also deals with progress listeners and dialogs for the user, so all of this is moved out of FDroid. This was so that RepoDetailsFragment can now invoke the same functionality. 2013-04-13 10:06:55 +10:00			`<?xml version="1.0" encoding="utf-8"?>`
			`<resources>`
			`<color name="signed">#ffcccccc</color>`
			`<color name="unsigned">#ffCC0000</color>`
"unverified" repo state for repos w/ fingerprints but not yet pubkeys If a repo was configured with a fingerprint, but it has not yet updated and gotten the pubkey from the index.jar, then it will be in an "unverified" state, i.e. the signing key fingerprint is stored, but it has not yet been used to check against the pubkey in the index.jar 2014-04-25 23:57:42 -04:00			`<color name="unverified">#ff999999</color>`
WIP: implementing context and action bar menus for repo management. SwitchCompat will return a Switch or a ToggleButton depending on the platform (doesn't matter, both are CompoundButtons) and this will be added to the repo_item view programatically. I'm using some pretty specific listeners to communicate between the details fragment and the repo list activity. I've also split the functionality (e.g. for deleting) between the repo list and the details view. In the future, when we have content providers for repos, it will be easier to take care of everything from the details screen, and automatically notify the repo list of changes. Refactored update service. Now has a static update method that can be called which will setup the required intent to begin the update. It also deals with progress listeners and dialogs for the user, so all of this is moved out of FDroid. This was so that RepoDetailsFragment can now invoke the same functionality. 2013-04-13 10:06:55 +10:00			`</resources>`