Hi!

Keith Hodges <keith_hodges at yahoo.co.uk> wrote:
> If I am wanting to deploy a minimal image I do not want to duplicate
> functionality, SqueakMap is duplicate functionality, because Installer
> can load from squeakmap and Installer is one class!
> 
> Ok it may not be the best design or code out there but making it one
> class was an initial goal for this reason. On the basis that other

Note that the reason SM is larger is because you get the full domain
model of SM inside your image.
This means that you can easily write snippets of code interrogating it,
you can use it offline (yes you can) etc etc.

AFAIK Installer (while being a nice concept) operates by web scraping,
which is fine BUT it thus "works around" the SM model and does not work
offline and does not offer the domain model and does not give you client
side caching (?) and does also not have code to use the server side
cache (I am guessing).

So even though I like Installer, don't simplify it for people who know
less - it is NOT a drop in replacement of the SM code.

But yes, if you WANT to skip all the above parts - then fine, it works.

regards, Göran