I´d like to use this issue to discuss what could, should and will happen with the PlayStore Entries like mentioned in #736 and #763.

The decision is: Updating the old app or releasing a new one.

To update the old app we'd need access to the signing-keystore and to the google play developer console. This option would be the easiest for the users, but we need the permission from GitHub (as discussed in #771).

When releasing a new app, we would have to find a new name for the developer/pubisher and maybe even a new name for the whole app (for the last point see #771).

Even if we don´t get access to the keystore and playStore developer console and are forced to use the second option it'd be great to publish one last update for the old app replacing the actual app with a hint about the new app

Hi, i'm developing GitSkarios, and of part of it i uses Retrofit.

I see that you are trying to use retrofit in gforkhub api.

I will provide you to my GithubSDK: https://github.com/gitskarios/GithubAndroidSdk

Feel free to look at it, use it or make me pull requests or open issue!

It would be cool if we could have native android notifications (either push or some custom polling interval) which would mirror github notifications.

Yes, I get them via email, but I refuse to check my email on my phone. Interesting things actually happen on github, so it would be nice to have notifications of them :-)

On android 4.4.4 on a samsung galaxy note 4, issues are not visible from the issue dashboard or from a repository view when clicking on a specific issue.

@fadils @Meisolsson @hzsweers @mustafa01ali

Hi guys, I've been on vacations for a few weeks now, so I haven't been able to contribute (I'll get back to it soon), but I've been following the development process and running the latest master on my phone, and I haven't updated the ForkHub app because I've found too many bugs and inconsistencies.

I know the development is going really fast and it's impossible to add no bugs, but we could minimize them. So please test harder the PRs before merging, I'll help with this as soon as I can.

I've also noticed that the git history is quite messy and it's hard for me to revise the commits. Please try to rebase your branches before merging.

We'll have a really awesome app in next to no time, thank you all for your contributions.

The following need to be done before we can get a 0.1.0 release out. @fadils @Meisolsson let me know if you think of anything else:

• [x] Release keystore and play store account. First release will be an open beta
• [x] Crash reporting tool (Bugsnag has a free open source tier)
• [x] Remove GitHub logos from the app for legal reasons
• [x] Log out button
• [x] New icon
• [x] Welcome pager that (briefly) explains this app's existence, transition this directly into the web auth
• [x] Update copyright

I added a log out feature in the navigation drawer to make it easy for users to access. Through shared preferences I save and keep track of the user's activity state (either logged in or out) to make sure that the log out process gets validated when the user leaves the app and launches it again later.

This should set the foundation to really allow developers to start digging in to implementing material design.

• Removes ActionBarSherlock and the RoboSherlock library supporting it
• Adds AppCompat and wrapper classes for ActionBarActivity that provide what RoboSherlock provided for ABS
  • This still uses RoboGuice 2.0. 3.0 would be nice, as it has 1st party support for these wrapper classes.
  • This also requires setting minSDK to 11, which in turn means we can really bump it up to 15. 15 still covers 90+% of all Android users, and almost certainly close to 100% of the tech savvy ones that use the Github app.
• Set basic color palette (you guys can change this to whatever you like, I just went with a safe option of the grey primaryColor, darker version for primaryColorDark, and the blue for accentColor
• Use AppCompat's new searchview UI (including using its new icon, which allows us to remove the old one)
• Improved .gitignore (my IDE kept wanting to commit IntelliJ files...)
• Removed unnecessary declarations from AndroidManifest

The actionbar cuts over the tab pager a little, but I don't think that's a new bug having seen it in the store version prior to this.

You guys should update your current actionbar items to fully-white versions of their new Material alternatives. They're available for free come google here, or I can add them in this pull request as well if you want.

This addresses #658

Screenshots album: http://imgur.com/a/x76xf

Couple screen records of the new UI:

• https://www.dropbox.com/s/7yoh831834u7nlm/device-2015-01-04-180254.mp4?dl=0
• https://www.dropbox.com/s/68oy4v2lo1dv29c/device-2015-01-04-180455.mp4?dl=0

https://github.com/JamesDunne/rest0-api/blob/master/REST0.APIService/APIHttpAsyncHandler.cs

The viewer does it show the entire file. It does 5 fetches and stops around line 1,100.

As discussed in #661. The current spinner navigation isn't really intuitive, and switching to a navigation drawer would be a good step forward. ActionBar's list navigation is deprecated now, so a switch would need to happen sooner or later anyway. This would also make the navigation more readily able to accept new areas to navigate to (settings, profile, etc.)

There's a couple good mockups in #368, I'll try to mock up a more material version tonight.

The current version on Google Play is 1.9.0 updated on Feb 20 2014. This version has syntax highlighting problems in the source editor, where some files like .c and .hpp cannot be highlighted. I see that the committing history of file /app/assets/source-editor.js shows the CodeMirror has been upgraded:

Update CodeMirror to v4.8.0 jonan authored on Dec 2, 2014 fadils committed on Dec 14, 2014

I have tried to run the app through Android Studio and the problem is gone. Maybe the app on Google Play should be updated. Thanks.

gradle caching. Shared caches can reduce the number of tasks you need to execute by reusing outputs already generated elsewhere. This can significantly decrease build times. We can enable this feature by setting org.gradle.caching=true.

===================== If there are any inappropriate modifications in this PR, please give me a reply and I will change them.

Description

In the profile README (the secret feature) the .png images are not resizing according to the screen size.

Versions and device

Version->1.18.0 Downloaded from the Play Store? -> YES On Android 10 Model of phone -> Realme 6i (RMX2002)

Steps to Reproduce

1. Visit this profile on the mobile app.
2. I designed the badges in figma (in .png format) and added it to the README file.
3. And after committing to the repo I checked the README in the mobile app and that's all. The images didn't resize according to the screen size.
4. I tried changing the width and height of the images but no result.

Actual behaviour

The images under the skills section didn't resize.

Expected behaviour

The images were supposed to appear as it appeared on the website (when opened from the phone)

Description

In the profile README (the secret feature) the .png images are not resizing according to the screen size.

Versions and device

Version->1.18.0 Downloaded from the Play Store? -> YES On Android 10 Model of phone -> Realme 6i (RMX2002)

Steps to Reproduce

1. Visit this profile on the mobile app.
2. I designed the badges in figma (in .png format) and added it to the README file.
3. And after committing to the repo I checked the README in the mobile app and that's all. The images didn't resize according to the screen size.
4. I tried changing the width and height of the images but no result.

Actual behaviour

The images under the skills section didn't resize.

Expected behaviour

The images were supposed to appear as it appeared on the website (when opened from the phone)