Age | Commit message (Collapse) | Author |
|
Right now, the answer is always "disconnected", I think it's a problem in EIP.isRunning().
I've also added some new strings, trying to minimize the number of them scattered through litterals around the code.
|
|
This fixes bug #4004: With new progress bars branch, if user switches provider the list of providers is not complete.
|
|
A nullpointer occurred, due to a progressbar view assigned when the screen
did not showed it.
|
|
|
|
If a new provider is added, it gets selected automatically hiding all
other providers, as if it had been selected clicking on it.
|
|
The progressbar is always below the first row, because only the selected
provider row remain visible.
If the user cancels the ProviderDetailFragment, all providers appear
again.
Next step: implement the same behaviour with the new provider usecase.
|
|
I've created a new adapter using code from
http://www.sherif.mobi/2012/01/listview-with-ability-to-hide-rows.html
and my own getView (moved from ProviderListFragment).
|
|
The progressbar does not show any message.
The progressbar overlaps the next provider list item. This is the next
issue to be fixed.
|
|
I've removed @id/progress_bar from Dashboard, and for login and logout
I'm using the one from the eip fragment.
|
|
|
|
Next step: prettify.
|
|
|
|
Login progress bar advances according to the srp stages.
|
|
I've renamed configuration wizard progressbar, because both had the same
name and that provoked a conflict.
|
|
|
|
It resizes the provider list, pushing it down to show the progressbar
up, and back to the original layout after the operation.
|
|
If the user presses the back button and returns to leap_android, the app
will show login or logout button remembering if s/he was authenticated
or not.
This fixes bug #3467.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
develop
|
|
If the user presses the back button and returns to leap_android, the app
will show login or logout button remembering if s/he was authenticated
or not.
This fixes bug #3467.
|
|
|
|
|
|
|
|
Copied again from http://android-developers.blogspot.de/2013/08/some-securerandom-thoughts.html
|
|
Solution copied from
http://android-developers.blogspot.de/2013/08/some-securerandom-thoughts.html
|
|
running', bugfix for bug #4477
|
|
|
|
|
|
|
|
The dialog shows only an "OK" button to dismiss it, and the reason why
the download failed.
Right now, this dialog appears if a download is not successful. If it's
too intrusive, I can remove some cases. Let's try how it feels.
|
|
I still let one method to bypass hostname verifier, otherwise dev.bm
will not work.
I've reduced downloading functions to 3: download without CA, download
with commercial CA and download with provider CA.
I only download CA cert once, when the user selects the corresponding
provider. Each time a user switch provider, the cert is downloaded
(along with other json files).
|
|
|
|
|
|
It was pointing to the master branch, which does not contain this file yet.
|
|
|
|
Next commit I'll push the Build from eclipse file.
I've also removed the tests .project file because it's not in there, and importing from Eclipse using Git import yielded in an error for the leap_androidTest project.
|
|
|
|
Instead of repeating preconditions, or composing sentences which take some things as obvious (e.g., the android client can be compiled using eclipse, but that does not mean that the run.sh script will work), I refer each step to the previous one.
|
|
|
|
|
|
Minor fixes in the other files.
|
|
Minor fixes in the other files.
|
|
If the build-native.sh script points to a different ndk-build
executable, it uses it.
If not, compile.sh looks for a build-native.sh in the $PATH and, if
present, correct the possible erroneous path in build-native (just to
avoid silly edits in that file), and compiles with it.
|