On Sat, Apr 28, 2018 at 11:41 PM, Offray Vladimir Luna Cárdenas < [email protected]> wrote:
I would say that using trees to setup themes is cumbersome (and preferences > and to enable/disable plugins). > Right. That's why we now have the theme .leo files in leo/themes. So now we have only one required setting: @string theme-name = <name of theme file, w/o .leo> All the old machinery must remain so that people can won't have to change their myLeoSettings.leo files. This thread reminds me of > ... > the Smalltalk culture of fighting actively against incidental complexity > (see [3], for example). Of course this is not easy, but any discussion and > action in this line should be visible and supported. > [1] https://news.ycombinator.com/item?id=3291085 > [2] http://www.vpri.org/pdf/tr2011004_steps11.pdf > [3] http://cuis-smalltalk.org/ > I couldn't agree more. There is a lot more to Leo than there was 25+ years ago, yet Leo's look and feel remain almost completely unchanged. On the programming side, I continue to discourage any changes to Leo's API. Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
