stepharo wrote > but this is just a tooling issue Tooling would certainly help, but I think the issue is a little deeper. It's about the amount of effort required to understand the purpose of the project. If you're scanning a list of titles of possible projects, and you see "DeprecationRewriter" or "MigrationHelper", you have an idea whether it's helpful or not, but something like "Playa" forces you to dig into the metadata you're talking about. Also, once the project is in core, the same applies to seeing "Debugger", "Compiler", etc in the browser
----- Cheers, Sean -- View this message in context: http://forum.world.st/Deprecator-tp4769844p4769909.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.
