<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html; charset=UTF-8" http-equiv="Content-Type"> </head> <body bgcolor="#ffffff" text="#000000"> On 9/25/2021 6:09 AM, Hilaire Fernandes via Cuis-dev wrote: <blockquote cite="mid:49000afe-0da6-363a-5d6d-1ed3997207e3@drgeo.eu" type="cite"> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> <div class="moz-cite-prefix">Le 23/09/2021 à 22:02, Juan Vuletich a écrit : </div> <blockquote type="cite" cite="mid:614CDD68.10701@jvuletich.org"> When I wrote LightWidgets and that doc, I was thinking on a regular widget kit, where you have maybe ten kinds of very generic widgets, and compose them in different ways to build UIs. <blockquote type="cite" style="color: rgb(153, 153, 153);">Nevertheless, it will be tremendously helpful to rationalize the Morph jungle when it comes to GUI building. </blockquote> I think the first distinction to make is between general, reusable widgets on one hand, and app specific morphs on the other. </blockquote> I agree with you. I am a bit in a hesitating/stalled situation: most of the DrGeo core is functioning, now I need to work on the GUI with dialogs, toolbars, panels, wizards. Could write from scratch but there is may be something more general to do, overall useful for Cuis community. But I am clueless how you design a GUI framework and it's likely a lot of work. Hilaire <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> When I'm not sure about a design, I start exploring the problem. Any hack will do, as it will teach me stuff and help me see better. Perhaps we can start with any dialog / toolber / panel or wizard. Just pick one. Tell us briefly how to use it in Pharo, and what are the DrGeo model objects it operates on. Then, let's build a first sketch: Using existing Layout, Labels, Text morphs, Label morphs, etc. Like Cuis builds all the existing tools. Now, see what is missing, etc. Then, let's think together and discuss. 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>