On Tue, Feb 26, 2019 at 11:45 AM Offray Vladimir Luna Cárdenas wrote: > I never though that Leo would change its base language or libraries. I was just addressing the fact that without context is difficult to have a fruitful conversation on the merits of one tool/ecosystem over the other.
If you have something specific about Pharo that you would recommend I look at, I would be glad to do so. I might still write a Leonine browser for Pharo as a form of "evangelism". pharoTools.leo contains a first draft of LeoPosition and LeoVnode classes, written in Pharo. Writing these classes brought to mind some of Vitalije's comments, to the effect that some vnode ivars might better be in other classes. That's not going to happen in Leo itself, but browser-related vnode ivars in the LeoVnode class might better be elsewhere, perhaps via an indirection, say v.browser_data. 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.
