________________________________________ De : Pharo-dev [[email protected]] de la part de Sean P. DeNigris [[email protected]] Envoyé : jeudi 1 mai 2014 20:31 À : [email protected] Objet : Re: [Pharo-dev] [ANN] Pharo3 Dark Theme is available
EstebanLM wrote >> About a morphic redesign... > I suppose best scenario is all community joining efforts to achieve the > goal, but for that we first need to discuss/agree on a design. Yes!!! IMHO our Morphic implementation's ocmplexity is the biggest thing holding back our creative spirit. It seems that many other things have been cleared out of our way and now is the time to make this happen. I think you hit the nail right on the head: 1) all interested parties join forces - there have been too many experimental cleanups and re-implementations that are interesting but ultimately unused/unusable, and 2) start with a solid design. Morphic's power is incredible and it would be great to have that available when you need it, with all the more-business-friendly UI objects built on top. Some good places I've found ideas and insights are ARK, Self, Lively Kernel, KScript, and Cuis. Note on the design: I wouldn't hesitate to have some of the business-friendly objects slightly on the side of the overall design: we don't need the full complexity and power of Morphic for many business objects... Doru's work with Glamour may be a good benchmark of how simple business looking code may be. However, I would dream of merging Roassal(2) and Morphic. Use Roassal DSLs and infrastructure to make Morphic simpler, and build fully integrated GUIs (code exploration tools, or even a system browser) where some of the widgets are Roassal(s). This was my dream when I started my browser: have a full screen representation of the code inside my image, as an interactive background to my Pharo, and editors floating there and there to edit the code, run it, explore it, debug it, etc... I settled for less :) Thierry
