<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html; charset=UTF-8" http-equiv="Content-Type"> <title></title> </head> <body bgcolor="#ffffff" text="#000000"> On 9/4/2021 4:44 AM, Hilaire Fernandes via Cuis-dev wrote: <blockquote cite="mid:8cd999c2-d7b8-3bd2-a72b-726b04b202d4@drgeo.eu" type="cite"> <meta http-equiv="content-type" content="text/html; charset=UTF-8"> Hi, Cuis' Morph is great, it is clean, easy to use, beautiful. One can code sexy view with it. Nevertheless we still miss an intermediate framework in the Cuis ecosystem regarding GUI. Something between the Morph ecosystem (VectorGraphic, Layout,...) and the "honest human" programmer. In the context of the Dynabook concept, where you write Smalltalk script to glue together different parts to produce a meaningful small applications, we need this intermediate DSL GUI framework to more easily design and write such small applications. I took a brief look about some existing frameworks out there. <ul> <li>Concur . This interesting article[1] explains general concept on widget Space (Layout) and Time (Event) compositions. How it is designed the as simple as possible to compose. Some part are hard to understand because it relies on the Haskell programming language.</li> <li>Glimmer. Ruby framework for GUI[2]. Resulting code looks already too complex to my taste.</li> </ul> Regarding space composition, it will be neat to write code as: "horizontal composition" ('Morph is great:' asLabel , boolean asWidget) "vertical compositions" | ('I like Smalltalk:' asLabel , boolean asWidget) | ('Ok' asButton) This is just rough idea how simple the code should be. No idea yet about the code could be simple for Time composition (Event). Interested to read your thought, reference materials or anything useful in the reflection. Best Hilaire [1] <a moz-do-not-send="true" class="moz-txt-link-freetext" href="https://potocpav.github.io/programming/2020/05/01/designing-a-gui-framework.html?utm_source=pocket_mylist">https://potocpav.github.io/programming/2020/05/01/designing-a-gui-framework.html?utm_source=pocket_mylist</a> [2] <a moz-do-not-send="true" class="moz-txt-link-freetext" href="https://github.com/AndyObtiva/glimmer">https://github.com/AndyObtiva/glimmer</a> <pre class="moz-signature" cols="72">-- GNU Dr. Geo <a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://drgeo.eu">http://drgeo.eu</a> <a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://blog.drgeo.eu">http://blog.drgeo.eu</a></pre> </blockquote> Hi Hilaire, I haven't had time to focus on this yet, but I agree that it would be great to start moving in this direction. I guess the model would be less powerful than "full morphic" and more focused on composing widgets, right? I'll read the links you sent. It some point, we could consider recoding the Smalltalk tools, if it would result in cleaner or simpler code. Thanks, <pre class="moz-signature" cols="72">-- Juan Vuletich <a class="moz-txt-link-abbreviated" href="http://www.cuis-smalltalk.org">www.cuis-smalltalk.org</a> <a class="moz-txt-link-freetext" href="https://github.com/Cuis-Smalltalk/Cuis-Smalltalk-Dev">https://github.com/Cuis-Smalltalk/Cuis-Smalltalk-Dev</a> <a class="moz-txt-link-freetext" href="https://github.com/jvuletich">https://github.com/jvuletich</a> <a class="moz-txt-link-freetext" href="https://www.linkedin.com/in/juan-vuletich-75611b3">https://www.linkedin.com/in/juan-vuletich-75611b3</a> @JuanVuletich</pre> </body> </html>