|
@raphlinus | |||||
|
Very theoretical but of likely of interest to people building native UI frameworks: Towards a unified theory of reactive UI raphlinus.github.io/ui/druid/2019/…
|
||||||
|
||||||
|
|
Rémy Rakić
@lqd
|
23. stu |
|
maybe @asajeffrey would have academic cites which could be useful here ? at the very least their own FRP work in Agda could provide some interesting theoretical background
— as could Phil Freeman's work on comonadic UIs, seen on blog.functorial.com & speakerdeck.com/paf31/the-futu… ?
|
||
|
|
||
|
Alan Jeffrey
@asajeffrey
|
23. stu |
|
The paper describing the UI work in Agda is asaj.org/papers/padl13.…, which is a bit of a brain dump, but does describe the implementation strategy.
|
||
|
|
||
|
Andrius Bentkus
@andriusbentkus
|
23. stu |
|
Please record your talk you are going to make about druid! You are documenting something that is impossible to read in literature.
|
||
|
|
||
|
Raph Levien
@raphlinus
|
23. stu |
|
This will definitely happen. Thanks for your interest!
|
||
|
|
||
|
NewoGame
@NewoGame
|
23. stu |
|
UI frameworks try to unify 2 disparate things. UI should be 2 systems. Firstly 1. A state machine. 2. Code that checks for conditions, interacts with the state machine, then renders output. If you put code into the state you end up with OOP.
|
||
|
|
||
|
corvus frugilegus
@glaebhoerl
|
23. stu |
|
Although I think these are more focused on the app state and user input half of things, they may be interesting:
github.com/divipp/lensref
github.com/divipp/frp_agda
|
||
|
|
||
|
六面镜子
@6Mirrors
|
16. pro |
|
Nice abstraction of the UI problem! Is there any progress on the theory?
|
||
|
|
||