<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Thanks, Karl! I appreciate your help on this!<br>
</p>
<p>Best regards,<br>
Tobias<br>
</p>
<div class="moz-cite-prefix">On 29.03.19 18:20, Karl Kleinpaste
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:94c406f3-6426-244e-e016-c1c6fa594917@kleinpaste.org">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<div class="moz-cite-prefix">On 3/29/19 7:16 PM, Tobias Klein
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:d85c8593-afbc-c1f6-5069-1fb6be554c22@tklein.info"> I
thought it may be convenient for the user to be informed about
this *before* installing a corresponding module.</blockquote>
<font face="FreeSerif">Of course. That's what Xiphos' mod.mgr
does, or any other UI's equivalent. It's just a matter of
whether it examines what's available and makes that info
available.<br>
<br>
The *.conf held by the repo (mods.tar.gz) are acquired when the
mod.mgr is opened. Each is checked for CipherKey and the
mod.mgr's offer of what's available to install is marked
appropriately. The user decides what he wants, checks boxes as
needed, and installs.</font> mod.mgr shows the lock symbol both
before and after install.<br>
<br>
There is a tooltip attached to the column heading: "The lock icon
means this module is encrypted, and requires that you purchase an
unlock key from the content owner." So the user is properly
warned.<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
sword-devel mailing list: <a class="moz-txt-link-abbreviated" href="mailto:sword-devel@crosswire.org">sword-devel@crosswire.org</a>
<a class="moz-txt-link-freetext" href="http://www.crosswire.org/mailman/listinfo/sword-devel">http://www.crosswire.org/mailman/listinfo/sword-devel</a>
Instructions to unsubscribe/change your settings at above page</pre>
</blockquote>
</body>
</html>