With the recent influx of interest from publisher to make material
available for our software, I'd like to propose a new .conf entry, and
encourage frontend developers to polish their facilities for users to
supply unlock keys for a locked modules.
The .conf entry I'd like to propose for all
Sorry for the typos.
I also wanted to say, if an example of how to change the .conf file to
add the user supplied CipherKey is desired, I can supply a concise code
snippet.
As far as user flow specifically for entering a key...
In BibleCS, we show an excerpt from the module, with an edit box for
I'm curious as to how you select the excerpt? Do you spin across the
possible keys until you find one w/ content? For example, consider a
Greek text that's a fragment of a Pauline epistle. Or just the book of
John in translation of a new lang.
In Him, DM
On Nov 22, 2009, at 1:05 PM,
Well, how DO WE, or how SHOULD WE?
Currently the code at:
http://crosswire.org/svn/biblecs/trunk/apps/InstallMgr/
in cipherfrm.cpp does this:
mod-setKey(Ipet 2:12);
tmpBuf = mod-StripText();
mod-setKey(gen 1:10);
tmpBuf += \r\n\r\n;
The way I do this in BPBible for the font dialog is to display the current
key if it is there, otherwise look forward and back until a key is found.
http://code.google.com/p/bpbible/source/browse/trunk/fontchoice.py#166
God Bless,
Ben
On Nov 22, 2009, at 7:45 PM, Troy A. Griffitts wrote:
Well, how DO WE, or how SHOULD WE?
I guess both. I still don't like the implementation in JSword and want good
advice. Our implementation will always accept a good key and sometimes reject a
bad key. It does not engage the user to confirm
