In the interest of simplifying cacheword deployment, I'm proposing to ship the core functionality as a plain jar file, then have a "helpers" library project that people could use as a library project, or just copy the classes and modify them as they see fit.
This means that cacheword.jar will only then depend on android-support-v4-jar (eliminating sqlcipher.jar, iocipher.jar, commons-codec.jar, and spongycastle as dependencies). So apps that already use cacheword will have to make the following changes: * use the "helpers" library or copy SQLCipher* classes into project * build and handle the lock/unlock notification * supply the icon for the notification How does this sound? Any concerns with this approach? .hc -- PGP fingerprint: 5E61 C878 0F86 295C E17D 8677 9F0F E587 374B BE81 _______________________________________________ Guardian-dev mailing list Post: [email protected] List info: https://lists.mayfirst.org/mailman/listinfo/guardian-dev To Unsubscribe Send email to: [email protected] Or visit: https://lists.mayfirst.org/mailman/options/guardian-dev/archive%40mail-archive.com You are subscribed as: [email protected]
