On Dec 16, 2011, at 5:41 PM, Sean P. DeNigris wrote:
Benjamin Van Ryseghem-2 wrote
But sometimes, we want different script for different version.
If you mean different Pharo versions, this is part of what Metacello provides e.g. load only in on #'Pharo1.3.x'.
Benjamin Van Ryseghem-2 wrote
When Stef is integrating, paths for scripts are different, and so are repos.
So each person would have their own configuration (just like they would presumably have their own startup preference file
Benjamin Van Ryseghem-2 wrote
The Metacello approach is network dependent.
Metacello is not any more network dependent than a preference file. Each person could keep the config on their local machine.
It still seems that the preference file approach adds complexity without providing any benefit. Of course I may be missing something ;-) So, now that the Metacello approach is on the table, which is already used successfully (at least by myself and Mariano), what does the preference file add - what can you do with the file that can't be done with Metacello?
You are right. It doesn't add a lot, except maybe that you can set an action do be performed only once per image and not at every launch. But may be you can do it also with Metacello :) But the thing is, we could use metacello to laod something from your hard drive instead of serializing. The thing is to have an automatic mechanism which can load sth ( a st file, a mc configuration, a fuel objet, idk ) which is shared among images. So yes, why not replaced StartupAtomics by metacello script ? I think the only argument is the "unique execution" thing Ben
-- View this message in context: http://forum.world.st/Startup-Preferences-tp4129591p4205366.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.