Preparing for v2.0.0 using the passwordmaker-je-lib
Initial testing commit for v2.0.0.  This version just verifies that I can hash, read/write the rdf xml files and use a gradle build
Renaming the package from my test package while I was developing.
Making this the markdown flavor for github
Adding an actual README.  Still a bit of work to do on it, but it will work for now
Adding the execute bit on this so that a user can just execute this script after cloning it
Adding more hooks up to the password maker library
Added the ability to show the database of profiles
- Also moved AccountManager into passwordmaker-je-lib as I think it would be useful in other places, and its faster to unit test there
- Made build system do an auto versioning for the android display version.  Based on the git tags.
Modified the proguard rules so that it doesn't obfuscate
Intellij keeps modifying my build file behind my back.  Adding back in the mavenLocal() directive.
Adding favorites into the mix
- Also improved the ActivityBar so that it doesn't need a menu for phones around the size of a nexus 4 and larger.  Probably smaller too, but if it overflow it should create a menu for the actions.
- Added some sample favorites for development is easy
- Made favorites use this autocomplete thing, that does a 'matching substring' filter
- Favorites are now swipe to delete.
Reorganized the filling of the fields .
Adding ability to modify patterns for profiles.
Got part of the import/export feature ready.  However, it seems to be failing to load it all.  Maybe I should use the resulting XML as a unit test for the pwm library.
Adding the ability to add patterns, autocomplete urls from accounts, modify the account url field.
Allow the user to just convert the incompatible algos to the closest match, with a warning that states this may produce different results.  Also now list the algos that were ignored, if the checkbox was not checked.
Allow using custom character sets.
Only show verification code if number of characters is greater than 8.  This is an intermediate fix until I figure out how to do a timer correctly.  I like the idea that the chrome version does a 600 MS delay as well.
Add toast to declared that the password is copied to the clipboard.
Save inputs for some length of time, after user requested to save the inputs.  This though stores the user password in plain text, but nothing really that I can do about it, unless android gave me some shared secret that I could use at runtime, otherwise I would either have to hardcode the key used to encrypt, or write a key to disk, which if the user can get the encrypted password on disk, they can get the key on disk too.