dadaphl

lets start with > - left k. - prev block > - right k. - next block > L. k - last block for now > L. k - last...

yea you are right, maybe for now we can keep it simple and only have a key for prev/next navigation.

tx types are actually different that in the mockups. lets think about reusability (aepp-components)

``` ➜ functions git:(master) ✗ pwd /home/philipp/.local/share/omf/pkg/vi-mode/functions ➜ functions git:(master) ✗ ls -la vi-mode-impl.py lrwxrwxrwx 1 philipp philipp 18 1. Okt 12:38 vi-mode-impl.py -> ../vi-mode-impl.py ``` temporary fix

Basic version online. [https://aeternity.github.io/aepp-aexistence](https://aeternity.github.io/aepp-aexistence) feel free to write requests/suggestions into the issue board at [https://github.com/aeternity/aepp-aexistence](https://github.com/aeternity/aepp-aexistence)

One example that lead me to create this issue is that I can't use the latest version of the `ae-address` component in the blockchain explorer. `ae-address` has a strong opinion...

ok, then lets move forward with this approach. shall we adjust all components?

Can you give us the gist of your references please. I don't find the time to read all this things. | Placeholder Avatars In general we should be aware that...

I think `ae-address` should by default still look like the previous implementation. This new representation should be a specific `layout` or `type`.