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.<br><a href="http://code.google.com/p/bpbible/source/browse/trunk/fontchoice.py#166">http://code.google.com/p/bpbible/source/browse/trunk/fontchoice.py#166</a><br>
<br>God Bless,<br>Ben<br>-------------------------------------------------------------------------------------------<br>Multitudes, multitudes,<br> in the valley of decision!<br>For the day of the LORD is near<br> in the valley of decision.<br>
<br>Giôên 3:14 (ESV)<br><br>
<br><br><div class="gmail_quote">On Mon, Nov 23, 2009 at 11:45 AM, Troy A. Griffitts <span dir="ltr"><<a href="mailto:scribe@crosswire.org">scribe@crosswire.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Well, how DO WE, or how SHOULD WE?<br>
<br>
Currently the code at:<br>
<br>
<a href="http://crosswire.org/svn/biblecs/trunk/apps/InstallMgr/" target="_blank">http://crosswire.org/svn/biblecs/trunk/apps/InstallMgr/</a><br>
<br>
in cipherfrm.cpp does this:<br>
<br>
mod->setKey("Ipet 2:12");<br>
tmpBuf = mod->StripText();<br>
mod->setKey("gen 1:10");<br>
tmpBuf += "\r\n\r\n";<br>
tmpBuf += mod->StripText();<br>
Memo1->Text = tmpBuf.c_str();<br>
<br>
Maybe we should just:<br>
<br>
for (module == TOP; !module.Error() && !module.getEntrySize(); module++);<br>
<div><div></div><div class="h5"><br>
<br>
<br>
<br>
DM Smith wrote:<br>
> I'm curious as to how you select the excerpt? Do you spin across the<br>
> possible keys until you find one w/ content? For example, consider a<br>
> Greek text that's a fragment of a Pauline epistle. Or just the book of<br>
> John in translation of a new lang.<br>
><br>
> In Him, DM<br>
><br>
><br>
><br>
> On Nov 22, 2009, at 1:05 PM, "Troy A. Griffitts" <<a href="mailto:scribe@crosswire.org">scribe@crosswire.org</a>><br>
> wrote:<br>
><br>
>> Sorry for the typos.<br>
>><br>
>> I also wanted to say, if an example of how to change the .conf file to<br>
>> add the user supplied CipherKey is desired, I can supply a concise code<br>
>> snippet.<br>
>><br>
>> As far as user flow specifically for entering a key...<br>
>> In BibleCS, we show an excerpt from the module, with an edit box for the<br>
>> user to type their unlock code, with a [Try] button next to it. The try<br>
>> button sets the unlock code in the module and re-retrieves the excerpt.<br>
>> If the unlock code is correct, the user will see the unencrypted module<br>
>> excerpt, and they can proceed to hit an [Accept] button to continue.<br>
>> But again, obviously each frontend will creatively design their own<br>
>> mechanisms. I would just like to be sure we have _some_ easy way on<br>
>> each frontend for our users to know where to obtain and then enter these<br>
>> unlock codes.<br>
>><br>
>> -Troy.<br>
>><br>
>><br>
>><br>
>> Troy A. Griffitts wrote:<br>
>>> With the recent influx of interest from publisher to make material<br>
>>> available for our software, I'd like to propose a new .conf entry, and<br>
>>> encourage frontend developers to polish their facilities for users to<br>
>>> supply unlock keys for a locked modules.<br>
>>><br>
>>> The .conf entry I'd like to propose for all locked modules is:<br>
>>><br>
>>> UnlockURL=<br>
>>><br>
>>><br>
>>> This would be a URL where to begin the unlock process: Purchase form,<br>
>>> CCAT user agreement form, whatever.<br>
>>><br>
>>><br>
>>> Thus the flow in a frontend installer might be to show locked modules<br>
>>> differently with a special lock icon next to each modules available for<br>
>>> install, when the module is selected for install, a popup box explaining<br>
>>> that a key is needed, and for obtaining the key to please visit the<br>
>>> following URL..., possibly even prompting at this time for the unlock<br>
>>> key. Obviously each frontend with be creative, as usual, but I believe<br>
>>> this is a missing, critical piece we need to supply to frontends, for<br>
>>> them to build a smooth flow for the user.<br>
>>><br>
>>><br>
>>> -Troy.<br>
>>><br>
>>> _______________________________________________<br>
>>> bt-devel mailing list<br>
>>> <a href="mailto:bt-devel@crosswire.org">bt-devel@crosswire.org</a><br>
>>> <a href="http://www.crosswire.org/mailman/listinfo/bt-devel" target="_blank">http://www.crosswire.org/mailman/listinfo/bt-devel</a><br>
>><br>
>><br>
>> _______________________________________________<br>
>> sword-devel mailing list: <a href="mailto:sword-devel@crosswire.org">sword-devel@crosswire.org</a><br>
>> <a href="http://www.crosswire.org/mailman/listinfo/sword-devel" target="_blank">http://www.crosswire.org/mailman/listinfo/sword-devel</a><br>
>> Instructions to unsubscribe/change your settings at above page<br>
><br>
> _______________________________________________<br>
> sword-devel mailing list: <a href="mailto:sword-devel@crosswire.org">sword-devel@crosswire.org</a><br>
> <a href="http://www.crosswire.org/mailman/listinfo/sword-devel" target="_blank">http://www.crosswire.org/mailman/listinfo/sword-devel</a><br>
> Instructions to unsubscribe/change your settings at above page<br>
<br>
<br>
_______________________________________________<br>
sword-devel mailing list: <a href="mailto:sword-devel@crosswire.org">sword-devel@crosswire.org</a><br>
<a href="http://www.crosswire.org/mailman/listinfo/sword-devel" target="_blank">http://www.crosswire.org/mailman/listinfo/sword-devel</a><br>
Instructions to unsubscribe/change your settings at above page<br>
</div></div></blockquote></div><br>