Dale, I looked at the docs but it was kind of a hunt as they were a bit kind of everywhere.\
* Book chapters (Pharo). This including preversions with more info than the published one * Google code wiki pages * Github * Other but can't even remember Is there an official place for all things Metacello? Metacello is great, especially with GTInspector so that we can see the directives etc. Compared to Maven pom.xml / parent and nexus/artefactory repos, it is easier to deal with I'd say. Phil On Fri, Oct 21, 2016 at 10:15 PM, Dale Henrichs < dale.henri...@gemtalksystems.com> wrote: > > > On 10/21/2016 07:30 AM, Norbert Hartl wrote: > > Dale, > > Am 21.10.2016 um 16:12 schrieb Dale Henrichs < > dale.henri...@gemtalksystems.com>: > > Norbert, > > I didn't realize that you were claiming that the new text model for Sparta > was (potentially) inferior. > > The other day you were expressing sadness about having to use the newer > version of Metacello (which is *only* 3 years old), so I assumed that you > were just being generally cranky about change:). > > it might be true it is a current topic for me. In my struggle to establish > a solid devlopment process I have sometimes the feeling it is impossible. > Especially when the new metacello thingie improves something I don't know > but at the same time I loose Versionner and the commandline handlers which > I know :) > The current (!) complaint is rather based on the fact that everything > regarding the graphics backend, widget and tools appears sometimes as an > indefinite loop of reinventing stuff and improving and never get the job > done. Did I mention 64bit, UFFI,… I'm glad all these topics are worked one > and I see a bright future if half of them are done. But then sometimes it > looks rather dark and the light at the end of the tunnel just went off :) > > <dark mode off/> > > Okay, so you _are_ being generally cranky:) > > FWIW, I took great pains to ensure the the old way of using Metacello > continued to work the old (buggy) way while introducing the new (non-buggy) > way and that you should be happy to only start feeling the pain of this new > feature 3 years after it was introduced:) > > I should also note that I have no plans to remove the old way of doing > things, even though I don't recommend that anyone use the old way anymore > ... At GemStone we have users running on 20 year old versions of our > product, so I have an appreciation for "legacy users." > > If you are using filetree based projects then the only way to access them > is the new way... > > Regarding the "command-line", did you know that once you've loaded a > project using the new way, that you can re-load a project using the > following shorter smalltalk script: > > Metacello image baseline: 'AAA'; load > > I made a sweep through the docs a couple of years ago, but since no one > seemed to be interested in using the new API I found other things to do ... > and now that there's more interest in the "new way" I simply don't have the > time (right now) to make another pass through the docs ... so you can be > cranky about that too :) > > Dale > > > > > > >
