README (1206B)
1 Taler assets 2 ------------ 3 4 This repository holds all the assets being used in web and mobile applications. 5 6 Assets names 7 ------------ 8 9 Names should be meaningful in a way that any client that uses the icons will know the purpose of it and can create references without ambiguity. That may lead to duplicate icons with the same content and different name (like using the same icon on different views), but it's fine. We can also start creating a placeholder for icons that we know we are going to need (with the correct name) but we don't have the content for. 10 11 * Example: 12 13 + svg 14 \__ + transactions 15 \__ README 16 \__ deposit.svg 17 \__ invoice_send.svg 18 \__ payment_pending.svg 19 \__ refresh.svg 20 \__ tip.svg 21 \__ withdrawal.svg 22 \__ invoice_payment.svg 23 \__ payment_ok.svg 24 \__ payment_refunded.svg 25 \__ refund.svg 26 \__ transfer_send.svg 27 + balance 28 \__ README 29 \__ + currency 30 \__ dolar.svg 31 \__ euro.svg 32 ... 33 + undefined 34 \__ send_24px.svg 35 ... 36 37 Folder with name "undefined" can be used for icons that some UI apps (android, ios, web) reference but have not yet agree.