Keith, please correct me if I'm wrong:
- Sake is a domain specific language with all required tools to define make-like rules. It allows people to describe tasks (as done in the Ant/Java world) and execute these tasks when necessary (http://wiki.squeak.org/squeak/5953)
Yes we need that
- Packages uses Sake to reimplement a universe-like tool with dependencies. Then, it describes a lot of Squeak packages with their dependencies.
Ok
What is PackagesSqueak310U....?
this is a class which has been generated automatically by a Sake task from the Dev Universe. This means that each change I do in the Universe system is reflected automatically in Sake just by running a task.
Moreover, the fact that each package is describe in a method using only Smalltalk code makes creating new set of packages very easy. For Pharo, we could just subclass PackagesSqueak310U and override the methods we want to change. For Seaside, they could just provide yet another class... I think it's much easier than with Universes. Finally, the package descriptions are hosted on SqueakSource instead of one's particular server.
Good! So let us check that. Don't you want to write something for the next book Squeak by Example VOl 2 (err....Phar ....) Stef
-- Damien Cassou Peter von der Ahé: «I'm beginning to see why Gilad wished us good luck». (http://blogs.sun.com/ahe/entry/override_snafu) _______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project