This is similar-ish to the old theme - it doesn't do so well with grey menu option drop-downs from the overflow list... http://developer.android.com/design/style/color.html
This is a follow on to issue #36, which allowed Agit to remember repos located in non-default locations. The file browsing is provided by OI File Manager, which the use is prompted to install if it's not already present.
Also using a 'fragment' for the first time- the repo list fragment.
These are the '1-navigation-refresh.png' files from Android_Design_Icons_20120229. http://developer.android.com/design/downloads/index.html
The 'No implementations match configuration.' errors that occur look like this issue: JakeWharton/ActionBarSherlock#377 ...but the 'ActionBarSherlockRobolectric' approach in that thread led to NPEs in this case :( Note that a separate approach ( https://github.com/passy/absshadow-sample ) to combining ABS and Robolectric has already been implemented in Agit's project with a509087. TEST PASSES: Ubuntu laptop Apache Maven 3.0.4 (r1232337; 2012-01-17 08:44:56+0000) Maven home: /home/roberto/tools/maven/current Java version: 1.7.0_03, vendor: Oracle Corporation Java home: /usr/lib/jvm/java-7-openjdk-amd64/jre Default locale: en_GB, platform encoding: UTF-8 OS name: "linux", version: "3.2.0-24-generic", arch: "amd64", family: "unix" TESTS FAIL: Ubuntu CI server Apache Maven 3.0.4 (r1232337; 2012-01-17 08:44:56+0000) Maven home: /var/lib/jenkins/tools/Maven/ja_Maven_3.0.4 Java version: 1.7.0_147-icedtea, vendor: Oracle Corporation Java home: /usr/lib/jvm/java-7-openjdk-i386/jre Default locale: en_GB, platform encoding: UTF-8 OS name: "linux", version: "220.127.116.11-kvm-i386-20111128-dirty", arch: "i386", family: "unix"
see here for related info: http://stackoverflow.com/questions/6491266/android-seekbar-clipped-thumb
…obolectric The awful guice repository-scope problems are avoided by passing the repo down as a parameter - so the TagViewer is no longer blank. The robolectric test has been dying horribly on some systems, seemly due to bytecode problems, and it didn't give any indication of failure when the TagViewer regressed - so an integration test is replacing the robolectric one.
Also provides action bar link upwards from the commit viewer- if you've specified a branch, the link will head back up to the branch commit-list view, rather than directly to the repo page.
fake clicking on a button in an actionbar is bit dubious
Unfortunately this means removing the big friendly Clone button on the dashboard, as it's rather bigger than the regular actionbar... need to add some kind of welcome
Caused by: java.lang.InstantiationException at sun.reflect.InstantiationExceptionConstructorAccessorImpl.newInstance(InstantiationExceptionConstructorAccessorImpl.java:48) at java.lang.reflect.Constructor.newInstance(Constructor.java:525) at com.xtremelabs.robolectric.bytecode.RobolectricInternals.newInstanceOf(RobolectricInternals.java:30) at com.xtremelabs.robolectric.Robolectric.newInstanceOf(Robolectric.java:59) at com.xtremelabs.robolectric.shadows.ShadowApplication.getSystemService(ShadowApplication.java:151) $ mvn -X Apache Maven 3.0.4 (r1232337; 2012-01-17 08:44:56+0000) Maven home: /home/roberto/tools/maven/current Java version: 1.7.0_03, vendor: Oracle Corporation Java home: /usr/lib/jvm/java-7-openjdk-amd64/jre Default locale: en_GB, platform encoding: UTF-8 OS name: "linux", version: "3.2.0-24-generic", arch: "amd64", family: "unix"
Establishing the clone-url is always going to be the user's first priority, so don't distract them with other fields until they've made headway on that task. This tweak is only enabled on Honeycomb and above, ie where the gentle LayoutTransition animation is available. The change is too distracting if it occurs instantly without animated fade-in.
Although some of the Android docutmentino indicates otherwise, the Android Market won't let you publish an APK with a lower versionCode than previously published for that product. So unfortunately, we can't use the nice 'versionCodeUpdateFromVersion' flag from android-maven-plugin v3. Reverts some of commit 3b80319.
I think it's better to default to https rather than ssh clone urls for this case because SSH access requires the user to have an SSH key installed - even if it's a public repo. also normalise formatting of AndroidManifest
Unfortunately it's necessary to manually add various methods used by the integration tests - as they're only supplied by the implementation APK, and proguard needs to know not to throw them away so they're available when the integration tests run.
Legibility greatly improved, appropriate colours are used to match ordinary notifications: * ICS - the new Notification.Builder and the default notification layout are used. The layout is abused slightly, with the 'info' textview being updated (tho the id for this textview is hidden) to serve as the progress text field. * Honeycomb and below - differences in colour between different versions of Android are handled by using the StatusBarNotificationStyles class, which is based off http://stackoverflow.com/a/7320604/438886 The AndroidManifest target sdk update to '13' (ie Honeycomb) is necessary to get the nice Holo-styling on the progress bar. Targeting ICS will have to wait until ABS support is in: "Applications targeting  or a later release will get these new changes in behavior: For devices without a dedicated menu key, the software compatibility menu key will not be shown even on phones. By targeting Ice Cream Sandwich or later, your UI must always have its own menu UI affordance if needed, on both tablets and phones. The ActionBar will take care of this for you."
Notification.Builder uses android.R.id.title & android.R.id.progress in it's layouts.
This has been a long time coming - the proguard-handling changed with the release of 3.0.0, and we've been stuck on an alpha-release ever since... finally made it on to the modern version! The exclusions are unfortunately necessary to avoid Dalvik verifier errors as it freaks out over differently proguard-ed versions of the same class.