Stéphane Ducasse wrote: > > Alain is our setting expert and we gotstuck on the how do write a setting > chapter. > So I'm happy other people like you push this further. >
My experience as a settings beginner. It was actually really easy because: * '*setting*' is used everywhere, so I did a 'class find' and immediately found the settings categories * there are a lot of examples all together in the settings categories I think the hardest thing was the "xxxOn: aBuilder <pragma>" concept in general (same goes for the new world menu) - it's not immediately obvious (via my typical highlight and "browse it" method) where to look for the class that scooped all the setting methods up and built the browser. I remember my initial thought was "now what would I look under to find the thing that generates and passes in aBuilder?" Also, I think this model of keeping settings in separate packages is definitely easier from a learning perspective because you have all working examples in the same place. When I implemented my first worldMenu pragma method, it took a while to figure out how to generate a list of all methods currently using <worldMenu> so I could see how it was done. I was looking for a SystemNavigator >> allMethodsUsingPragma: aSymbol, or something like that. With that funtionality, I guess it really wouldn't matter where they were located - or am I missing an easy way to find these methods? Sean -- View this message in context: http://n4.nabble.com/Fix-2329-Default-MC-Directory-Setting-tp2019559p2019958.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com. _______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
