dsc-2019-q2.md

layout: wip
title: GUI UX coding (3 months)
author: dsc
date: 17 April, 2019
amount: 282
milestones:
  - name: 1st month
    funds: 33% (94 XMR)
    done: 22 August 2019
    status: finished
  - name: 2nd month
    funds: 33% (94 XMR)
    done:
    status: unfinished
  - name: 3rd month
    funds: 33% (94 XMR)
    done:
    status: unfinished
payouts:
  - date: 22 August 2019
    amount: 94 XMR
  - date:
    amount:
  - date:
    amount:

What

32 hours a week for 3 months. My last proposal was the first where I was able to dedicate fulltime attention to Monero. Thus, past 3 months has seen substantial improvements to the GUI. For example, all points from this issue have been resolved or at least improved upon.

Who

I'm dsc, familiar with Monero GUI internals and contributed to the GUI codebase since fall 2017.

My contributions/experience:

• https://github.com/monero-project/monero-gui/commits?author=xmrdsc
• https://github.com/xmrdsc/py-levin/commits?author=xmrdsc (autonode.xmr.pm)
• https://github.com/wownero/wownero-funding-system/commits?author=xmrdsc
• https://github.com/wownero/Wownero-Light-Wallet/commits?author=xmrdsc
• https://github.com/monero-ecosystem/qml-xmr/commits?author=xmrdsc
• https://github.com/monero-ecosystem/moneriote-python/commits?author=xmrdsc (moneroworld)
• Free VPS Hosting for XMR i2p workgroup, Noncense Research Lab and a Gitea backup git instance.
• The fan-favourite & glorious IRC bot xmr-pr - making everyones life more managable

Report on the previous 3 months

• Introduced white theme
• New wizards, both code and design rewritten from scratch
• Simple mode: automatic remote node finder (autonode.xmr.pm)
• IPC (monero:// and moneroseed:// uri handler)
• Introduced font-awesome + .svg for higher quality icons
• New transaction history page
• Wrote a 'GUI development guidelines' document (not released yet :-P)

In addition I 'cleaned up' QML components and reviewed/rewrote existing QML/js logic. Good QML components lead to a more stable/clean UX. This is time consuming, as QML is not intuitive or easy to work with (compared to, say, HTML + CSS). These efforts are a balance between "needing to clean up the codebase before we can continue" versus "delivering tangible results the community benefits from".