|
|
As per 93b1953..d822f2c we now pass the "summary" and the "choices" (see https://docs.taler.net/design-documents/073-extended-merchant-template.html#tsref-type-TemplateAddDetails ) to the MUST logic that instantiates the template. contrib/paywall.en.must should be updated to show the summary and the choices. It should be noted that in the Paivana context there are some limitations: - We don't know the meaning of the token families, or which token families are available at the wallet - Tip probably should never be given, and it's OK to not show it - The main common possibility is that there are multiple choices for multiple currencies We should probably also already support subscriptions and discount tokens, but for those it probably is OK to *only* show the description (possibly with i18n applied) of the choice, without going into details about inputs and outputs; furthermore, because we do not know if a choice that requires any input token is actually available at the user's wallet, I suggest we do NOT show such choices by default (KISS!) and only show them after the user clicks on some "more payment options" button. Just to avoid bloating the screen with tons of choices, especially given that the wallet will *again* show / auto-apply these choices after scanning the QR code anyway. So my suggestion: first iteration, ONLY show summary (if present) and by default ONLY the choices without input tokens with price and description. If there are more choices, have "more payment options" button to expand list to also show payment options involving inputs. To proceed, I think Sebastian should do a first set of modifications to the paywall.en.must, and then we can ask Vlada to do an iteration on the design for a v2. |
|
|
partially implemented in 3a4b5f6..3240d70 still missing * split choices in "simple_choices" (without tokens) and "complex_choices" (with input tokens) in mustache context * amount string for the choice object should be converted based on merchant currency_spec before sending the list to the render engine * all static string in EN should be also mustache's template fields so the server can render based on Accept-Language |
|
|
can you add the first 2 features in the mustache template? |
|
|
this is how it looks now: 1) simple template, only one option 2) and 3) complex template, 3 options, first option doesn't have description image.png (52,900 bytes) image-2.png (57,199 bytes) image-3.png (58,058 bytes) |
- Anonymous
