Guillermo Polito wrote > > Hmm, I do not like the idea of having subclasses of references for > different kind of files... I believe that things like fileIn for example, > or extract zip should be external to the file library... >
My motivation is to make the system live and direct. In the domain of files, an extension signifies a type. As a user, if I have a file type I'm not familiar with, I want to know what kinds of things I can do with it. This approach puts those behaviors in the object that I'm handed back, which represents the file in the Pharo world. I would expect that many of these will in fact simply forward the request to an object external to the file library, but the advantage is that they are reified in the object that the user already has in hand, so they don't have to go searching for that external object. -- View this message in context: http://forum.world.st/ENH-FileReference-subclasses-tp4643116p4643223.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
