CodeDmitry wrote > It's just nice to have a standalone code that I can give to my friends > that they can read and run to create the structure without having to setup > everything themselves, but at the same time not needing to use a package. > > A standalone script is quite elegant for situations like that, since it > well encapsulates the automation without forcing people to understand > packaging. > > I don't mind shooting myself in the foot, I want to understand how Pharo > runtime works, it has this strange circularity to it that I can't quite > wrap my mind around. > > I just like doing everything in Code if possible. I see no reason to use > the browser other to inspect system state at the moment.
Bear in mind, the browsers were created by the original authors to facilitate repetitive actions. They are tools for interacting with the objects in the system, just as are the debugger and inspector. That being said, I do agree i is important to understand how the tools do what they do. You should definitely browse the Behavior hierarchy. It contains all the code for creating classes, compiling (and installing!) methods, removing methods, and so on. Also, I noticed in your examples that you like to write ([ ... ] value). Why? Why not just write the actual code (shown as ... in my example)? > Personally I've never had more fun with Smalltalk as I did writing this > proof of concept. -- View this message in context: http://forum.world.st/New-to-Pharo-a-bunch-of-questions-tp4917701p4917926.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
