Am 17.02.2017 um 18:51 schrieb Esteban A. Maringolo: > I've used ENVY for a couple of years, and marginally used Store. Store > is nothing compared with ENVY, ENVY is far superior. Store is like > Monticello, but as such it lacks the "Configuration Map" part of it, > that is offered by Metacello in Pharo/Squeak/GemStone. > > However I find ENVY to be too cumbersome for an agile way of working.
And another point is, that the way of ENVYs thinking is also available in the tools they offer for the developer (let it be VW 2.5.2 or VASmalltalk). Same tools on all platforms. This way of thinking is also introduced in the kind of browsers you have - which offers different ways of views on your projects. For me the most and strongest point in the ENVY-Browsers area is the ApplicationBrowser. Its shows you only the part of the image of a specific application (package) , which are new classes introduced by you in this application (package) - but also all the extension methods you added in this application (package) to classes. That means - programmers can stay for the whole life of a project - in only this kind of browsers. A wonderful way of viewing the image. Sadly this is gone or simply only badly implemented. E.g. in Pharo you can select a package - fine, but to know, what has been extended in this package ?. The name of the method categories also define in which package this method is located in. Make a type error and the method goes into a different package and you will not recognize it. Solutions born by the idea: how can we make it simple to have a solution this evening - and these solutions survive over the years. ENVY for the first time used ? Well I remember, that I was crazy about this tool - all this versioning, prerequisites etc ... but now after 20 years ? I'm used to the tools available on the Smalltalk market - but really nice versioning (with several platforms): ENVY is the way to go. And the original version had several user interactions implemented - which have been defined by VASmalltalk (e.g. change the developer role and make this or that in one click). ENVY is also the tool, where I have so much confidence with, because over the last 20 years I've never seen crashes and data losses. A strong point for a closed-source software repository. Marten -- Marten Feldtmann
