Re: [sword-devel] Question about GerHfa2002 and locked modules in general

2019-03-30 Thread Tobias Klein

Thanks, Karl! I appreciate your help on this!

Best regards,
Tobias

On 29.03.19 18:20, Karl Kleinpaste wrote:

On 3/29/19 7:16 PM, Tobias Klein wrote:
I thought it may be convenient for the user to be informed about this 
*before* installing a corresponding module.
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.


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. mod.mgr 
shows the lock symbol both before and after install.


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.


___
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

Re: [sword-devel] Question about GerHfa2002 and locked modules in general

2019-03-29 Thread Karl Kleinpaste

On 3/29/19 7:16 PM, Tobias Klein wrote:
I thought it may be convenient for the user to be informed about this 
*before* installing a corresponding module.
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.


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. mod.mgr shows the 
lock symbol both before and after install.


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.
___
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

Re: [sword-devel] Question about GerHfa2002 and locked modules in general

2019-03-29 Thread Tobias Klein
Ok, thanks. I thought it may be convenient for the user to be informed 
about this *before* installing a corresponding module.


Is there a way to automatically acquire and check the .conf file without 
installing the corresponding module first?


Best regards,
Tobias

On 29.03.19 08:39, Karl Kleinpaste wrote:

On 3/29/19 10:59 AM, Tobias Klein wrote:
It would be nice if the user could see that piece of information 
before installing a module that requires an unlock key.

http://karl.kleinpaste.org/.../mod-mgr-w-lock.png
Xiphos' mod.mgr provides this with a "locked" column indicator, by 
looking in .conf for CipherKey. Any frontend mod.mgr could do this.


___
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

Re: [sword-devel] Question about GerHfa2002 and locked modules in general

2019-03-29 Thread Karl Kleinpaste

On 3/29/19 10:59 AM, Tobias Klein wrote:
It would be nice if the user could see that piece of information 
before installing a module that requires an unlock key.

http://karl.kleinpaste.org/.../mod-mgr-w-lock.png
Xiphos' mod.mgr provides this with a "locked" column indicator, by 
looking in .conf for CipherKey. Any frontend mod.mgr could do this.
___
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

Re: [sword-devel] Question about GerHfa2002 and locked modules in general

2019-03-29 Thread David Haslam
I replied with a PocketSword screenshot, but the image was bigger than the 50k 
threshold.

Would the list moderator please accept my earlier reply. Thanks.

David

Sent from ProtonMail Mobile

On Fri, Mar 29, 2019 at 15:09, Peter Von Kaehne  wrote:

> There is not other than by testing against existence of a key in the conf file
>
> Peter
>
>> Gesendet: Freitag, 29. März 2019 um 14:59 Uhr
>> Von: "Tobias Klein" 
>> An: "SWORD Developers' Collaboration Forum" 
>> Betreff: [sword-devel] Question about GerHfa2002 and locked modules in 
>> general
>>
>> Hi,
>>
>> I stumbled across GerHfa2002 and found that it's a locked module.
>> http://www.crosswire.org/sword/modules/ModInfo.jsp?modName=GerHfa2002
>>
>> Is it possible through the API of InstallMgr or SWModule to detect
>> whether a module is locked or not?
>>
>> It would be nice if the user could see that piece of information before
>> installing a module that requires an unlock key.
>> I didn't find any way to get that information automatically.
>>
>> Best regards,
>> Tobias
>>
>>
>> ___
>> 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

Re: [sword-devel] Question about GerHfa2002 and locked modules in general

2019-03-29 Thread Peter Von Kaehne
There is not other than by testing against existence of a key in the conf file

Peter

> Gesendet: Freitag, 29. März 2019 um 14:59 Uhr
> Von: "Tobias Klein" 
> An: "SWORD Developers' Collaboration Forum" 
> Betreff: [sword-devel] Question about GerHfa2002 and locked modules in general
>
> Hi,
> 
> I stumbled across GerHfa2002 and found that it's a locked module. 
> http://www.crosswire.org/sword/modules/ModInfo.jsp?modName=GerHfa2002
> 
> Is it possible through the API of InstallMgr or SWModule to detect 
> whether a module is locked or not?
> 
> It would be nice if the user could see that piece of information before 
> installing a module that requires an unlock key.
> I didn't find any way to get that information automatically.
> 
> Best regards,
> Tobias
> 
> 
> ___
> 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] Question about GerHfa2002 and locked modules in general

2019-03-29 Thread Tobias Klein

Hi,

I stumbled across GerHfa2002 and found that it's a locked module. 
http://www.crosswire.org/sword/modules/ModInfo.jsp?modName=GerHfa2002


Is it possible through the API of InstallMgr or SWModule to detect 
whether a module is locked or not?


It would be nice if the user could see that piece of information before 
installing a module that requires an unlock key.

I didn't find any way to get that information automatically.

Best regards,
Tobias


___
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