On Fri, Jun 27, 2008 at 01:09:36PM +0200, St?phane Ducasse wrote:
Hi matthew
Thanks for your explanation. We were afraid by MC1.5 because - the atomic loading features as hacked by ralph looked dubious to us.
Ralph's pseudo-atomic loader is not in MC1.5, according to Keith; however, a different pseudo-atomic loader written by keith is the default loader. It also includes the old loader (disabled by default), and an experimental true atomic loader (also disabled by default).
we did not want to break the dependency mechanism
As far as I am able to tell, MC1.5 has not touched the dependency mechanism, and it works fine on what I have tried it with (which is only Nile, so far)
- the problem with PLF is that it looks like a black box that loads a lot of stuff and we do not know why
LPF loads Installer, then Monticello 1.5, then Loader. That is all. It does this by using Installer, which is able to fetch scripts off the web, dispatching optionally based on the image version (Squeak3.9, Pharo0.1), and by author initials. Look at the bottom of http://installer.pbwiki.com/LevelPlayingField First it runs the script LevelPlayingField-Preamble, then it runs one of the LevelPlayingField-<image version> scripts, and finally it runs the LevelPlayingField-Postscript script That is all it does. The scripts are linked and viewable on the web, so you can check what they do, and edit them by logging into the wiki (password is squeak)
- since we do **everything** with MC is should work 100% or we are dead.
So do we. We keep it working
Now we would be happy to ask our MC expert (yes I looked at adrian and lukas) :) to check your changes and slowly incorporate them.
Ok. Do what suits your fancy. Seems like a strange approach, though, since that is exactly what MC1.5 is: a merge of all the features from all the older forks of Monticello: impara, 3.9, with a much more careful eye on backward compatability. Unlike Monticello in 3.9, MC1.5 can save packages that Monticello in 3.8 is able to read and load.
Alex did a small but cool improvement: dirty packages are always at the top of the mc browser. We found that cool and integrate it.
I'll integrate it too. Thanks for the notification. -- Matthew Fulmer -- http://mtfulmer.wordpress.com/