Hi Marten, Frankly speaking, I find Envy way too complicated. I am using it these days and I am really not happy with. If I have to read a book to understand how it works, than there is no way I can teach students on how to use it in a reasonable amount of time. Configuration Map, Application, edition, scratch version and many more are way too many concepts, in my opinion.
Alexandre On Apr 6, 2013, at 5:03 AM, Marten Feldtmann <mar...@schrievkrom.de> wrote: > In all the discussions about how to manage/organize Smalltalk code - I would > like to add, that ENVY (though it's so old) with its config maps, > applications, prerequisites is a pretty good example how it works. > > Take a look at the only available ENVY implementation today (VAST) and think > about the way they did it in the eighties ... > > The ENVY-(concept - not the implementation) is still a master peace in this > area - even when compared with VS or Eclipse - and it supports the power of > Smalltalk very much. > > There are questionable parts of ENVY and I do not use these parts of it very > often. But even these questionable parts of ENVY have not been better solved > by other Smalltalk source code management systems. > > I've repositories, which are around 10 years old - and ALL code is still > there, all versions for all different platforms - down to methods differences > within a mouse click and the speed within a LAN is so good. > > > Marten > > >> On Apr 5, 2013, at 11:28 PM, Alexandre Bergel<alexandre.ber...@me.com> >> wrote: >> >>> Just a question: Is there any plan for a Metacello 2? >> > <marten.vcf> -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
