Thank you, Stef, for providing this (and all else you do). As a very new user, I agree completely with your comment about the importance of documentation. I addition to the "Command/Package" based approach exemplified in this and the other books, I'd encourage the community to also consider a "Recipes/Cookbook" approach. I've linked to two examples below, but the basic idea is an organized structure of Problem: (E.g., I want to list all of the PDFs in a directory and its sub-directories). Solution: [Sample code, perhaps heavily commented to explain. May have a basic and a more advanced code snippet] Explanation: [An explanation of the sample code, if not provided in its comments] This approach is especially helpful when users may not be familiar with the ecosystem, meaning they wouldn't even know where to start looking for an answer. Also, some people learn best starting from specific problems. I feel bad recommending that "Someone should do this..." when I'm not in a position to help currently (heaviest teaching period of the year), but offer this up for consideration. https://books.google.com/books?id=wVsnCgAAQBAJ&pg=PA192&lpg=PA192&dq=swift+r... <https://books.google.com/books?id=wVsnCgAAQBAJ&pg=PA192&lpg=PA192&dq=swift+r...> https://iswift.org/cookbook/get-directory-contents <https://iswift.org/cookbook/get-directory-contents> ----- Glenn Hoetker ghoetker@me.com http://hoetker.faculty.asu.edu -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html