New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Custom Refresh Times #84
Comments
It is hard coded to 15 minutes for batter-life to usability concerns. I'd like to add a dropdown to let you select. Anything less than 15 minutes is going to kill battery life. My thoughts for options, based on what Android optimizes for are: |
Ide like to cut my teeth at android dev. Maybe this is a good starting point for me to try? |
Of course! You will probably want to look at SettingsActivity as well as Notifier. Send a pull request and I'll review and merge it. |
Great thanks...first step making the ide work :-) |
@Fammy when i load up the IDE i'm seeing i need android-support-v13.jar. |
I recently removed that. You should be working off the develop branch. Let Jason Famularo On Fri, May 31, 2013 at 2:51 AM, Chris Blyth notifications@github.comwrote:
|
whoops, i'll double check and make sure i'm doing it correctly. |
@Fammy on the develop branch and had 2 issues.
but the app won't start, looks like it can't create the api on line 91 in org.tweetalib.TwitterManager Are you able to help? |
@Fammy I think i've got it, was an issue in the IDE setup. http://commonsware.com/blog/2013/05/23/do-not-manually-modify-eclipse-build-path-except-now-r22.html |
Pull request 86 sent with fix. |
I've been using IntelliJ Idea. I have no idea (pun intended) if Eclipse still works. Sorry for the confusion. I'll review this pull request shortly. |
Fix for Issue #84 - Custom Notification Timings
Good news is, that eclipse now works :-) |
It did! |
Would it be possible to include custom refresh times.
It looks like it's hard coded to 15 minutes in here:
https://github.com/chrislacy/TweetLanes/blob/master/android/client/src/com/tweetlanes/android/Notifier.java#L76
The text was updated successfully, but these errors were encountered: