On Friday, July 7, 2017 at 9:41:51 AM UTC-5, Offray Vladimir Luna Cárdenas wrote:
I'm glad with this question, despite of not knowing the internals of how > this works, I just use it, but seeing this interest, I think is helpful in > the crosspollination of ideas. > We have been doing a lot of that lately. > If there is a crash, Pharo will load an Epicea logger that allows you to > list and recover last unsaved changes you choose to. > Nice. > Pharo support code refactoring by default (as usual in Smalltalk > versions), so any change is objects definition or methods is applied > consistently across the system with little user intervention. > Perhaps this is the heart of the matter. > Developing in the debugger is kind of natural in Pharo and I have been > making such transition myself, despite of coming from the tradition of > developing in the file system, by writing files (how quaint! :-P). > Hehe. I would advice to experience this by yourself. Click on the "Pharo3Theme > beCurrent" link. You will see the change happening lively. No freezing or > reloading involved. > Will do. All this sounds very cool. > I have passed your question to the Pharo community and I will post the > thread here, once starts to move. > Thanks. I am interested in learning how auto refactoring works. 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 leo-editor+unsubscr...@googlegroups.com. To post to this group, send email to leo-editor@googlegroups.com. Visit this group at https://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
