To keep your documentation DRY, Karel suggested the usage of acsciidoc
include in this ML thread .
We tried with Erik* some experiment, it's in this gist .
I think it's aneat feature and we could use it in different way:
1) reuse some cookbook documentation page (if in asciidoc format)
2) embed source code snippet in our documentation to make sure our doc is
always up to date with latest code
Just wanted to check with you if you like the idea bacause it will involve
some documentation format changes (part of your web site revamp). Note: we
could use code snippet include (option2) without option 1).
Good morning peeps, on the last week me and @passos spent most part of the time reading/testing/deleting and struggling with the best approach to provide offline authentication, encrypted cache and friends on AeroGear.
This is our initial draft https://github.com/aerogear/aerogear.org/pull/247 planned to be released with AG Security 1.4.0 if we survive to the global warming.
Feedback is welcome.
aerogear-crypto latest version v0.2, requires iOS 7 and later and aerogear-ios has a dependency for. Currently, for aerogear-ios updating to iOS 7 is scheduled fro the 1.5 frame so it makes sense for the upcoming 1.4 release of the aerogear-ios library to leave the dependency for crypto in 0.1
Internally, the crypto functionality used by aerogear-ios (symmetric encryption) hasn’t been changed in the 0.2 which was focused more on asymmetric and digital signatures, so staying in 0.1 makes sense (for now).
Hello iOS folks
I’ve started looking at sync part, I’ve created a separate repo . For now, this lib is dependant on iOS-core. does is worth having it separate for folks that what to use core without sync?
Same question applies for encrypted store. Right no encrypted store are part of iOS-core. do we want to separate it for people who want core without encrypted store ?
what about people who all it all, encrypted store+sync, we’ll have to manage correctly transitive dependencies.