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 ------------------------------------------------------------------------------------------- Multitudes, multitudes, in the valley of decision! For the day of the LORD is near in the valley of decision. Giôên 3:14 (ESV) On Mon, Nov 23, 2009 at 11:45 AM, Troy A. Griffitts <scr...@crosswire.org>wrote: > 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"; > tmpBuf += mod->StripText(); > Memo1->Text = tmpBuf.c_str(); > > Maybe we should just: > > for (module == TOP; !module.Error() && !module.getEntrySize(); module++); > > > > > DM Smith wrote: > > 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, "Troy A. Griffitts" <scr...@crosswire.org> > > wrote: > > > >> 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 the > >> user to type their unlock code, with a [Try] button next to it. The try > >> button sets the unlock code in the module and re-retrieves the excerpt. > >> If the unlock code is correct, the user will see the unencrypted module > >> excerpt, and they can proceed to hit an [Accept] button to continue. > >> But again, obviously each frontend will creatively design their own > >> mechanisms. I would just like to be sure we have _some_ easy way on > >> each frontend for our users to know where to obtain and then enter these > >> unlock codes. > >> > >> -Troy. > >> > >> > >> > >> Troy A. Griffitts wrote: > >>> 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 locked modules is: > >>> > >>> UnlockURL= > >>> > >>> > >>> This would be a URL where to begin the unlock process: Purchase form, > >>> CCAT user agreement form, whatever. > >>> > >>> > >>> Thus the flow in a frontend installer might be to show locked modules > >>> differently with a special lock icon next to each modules available for > >>> install, when the module is selected for install, a popup box > explaining > >>> that a key is needed, and for obtaining the key to please visit the > >>> following URL..., possibly even prompting at this time for the unlock > >>> key. Obviously each frontend with be creative, as usual, but I believe > >>> this is a missing, critical piece we need to supply to frontends, for > >>> them to build a smooth flow for the user. > >>> > >>> > >>> -Troy. > >>> > >>> _______________________________________________ > >>> bt-devel mailing list > >>> bt-de...@crosswire.org > >>> http://www.crosswire.org/mailman/listinfo/bt-devel > >> > >> > >> _______________________________________________ > >> sword-devel mailing list: sword-devel@crosswire.org > >> http://www.crosswire.org/mailman/listinfo/sword-devel > >> Instructions to unsubscribe/change your settings at above page > > > > _______________________________________________ > > sword-devel mailing list: sword-devel@crosswire.org > > http://www.crosswire.org/mailman/listinfo/sword-devel > > Instructions to unsubscribe/change your settings at above page > > > _______________________________________________ > sword-devel mailing list: sword-devel@crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page >
_______________________________________________ sword-devel mailing list: sword-devel@crosswire.org http://www.crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page