taler
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Taler] ToS rendering (was: Re: Taler Android UX)


From: Torsten Grote
Subject: [Taler] ToS rendering (was: Re: Taler Android UX)
Date: Thu, 30 Apr 2020 15:50:06 -0300

On 2020-04-05 06:45, belen barros pena wrote:
>> TOS: I very much like how you show the TOS here with the 
>> progressive-disclosure section-structure. This _will_, however,
>> require the wallet to do quite a bit of extra work to _parse_ the
>> RST/markup/TXT it currently receives to turn the TOS-Text it into
>> this, but I do think it is a great idea.  But at least I would
>> estimate that this will be more work to implement than most of the
>> other changes combined ;-).
> 
> that’s fair enough. I guess I was hoping that all TOSs would have a
> similar structure, or at least a set of compulsory, common sections 
> that would be marked up somehow by the exchanges and could be used
> by the application to break down the content. I guess that’s not the
> case.

Florian made a design document about ToS rendering:

    https://docs.taler.net/design-documents/003-tos-rendering.html

The goal is to have exchanges provide their ToS in markdown format, so
we have a common format that we can render according to Belen's suggestion.

I have implemented this now in the Android Wallet. Here's a video of how
it looks like:

https://devtube.dev-wiki.de/videos/watch/083194f6-8b70-4673-8b9f-3eb0de23f1a7

Note that with the expandable sections in mind, the example ToS should
probably use less sections.

The implementation should be able to handle any markdown ToS confirming
to the specs outlined in the design document.

Kind Regards,
Torsten



reply via email to

[Prev in Thread] Current Thread [Next in Thread]