One of the things that we’ve tossed about for a while is keeping the conf of the module pristine and storing the cipher key in another file. That other file would hold all the frontend edits for the confs. It would have the form: [NASB] CipherKey=asdf [KJV] Font=yadayadayada …
I was going to roll my own in JSword, but Troy said that this mechanism already exists in SWORD. It would be nice to standardize the location and naming of such. — DM > On Dec 17, 2014, at 9:45 AM, Karl Kleinpaste <[email protected]> wrote: > > A suggestion for all apps: When updating a locked module, keep/re-use the old > CipherKey. > > This was a suggestion from Greg during rapid updates in his NASB testing > cycle. Having to re-paste or re-type the key is a pain and should be > unnecessary. If the user has had the module a long time, he may no longer > have the key otherwise. Generally speaking, I think we can expect that a > module's updates will continue to have the same key. > > I did this for Xiphos, and then forwarded the thought to Nic who has already > added it to PS as well. It seems to me that this is a good universal > behavior for Sword apps. > _______________________________________________ > sword-devel mailing list: [email protected] > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page
_______________________________________________ sword-devel mailing list: [email protected] http://www.crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page
