<body><div id="__MailbirdStyleContent" style="font-size: 10pt;font-family: Arial;color: #000000">
Installer can become a great starting point for code and resource loading for all kinds of local experiments. Including file-in from the file system. It might already be: Installer class >> installFile:.<div><br></div><div>So, Installer is at a different abstraction level and has different use cases compared to Metacello.</div><div><br></div><div>Best,</div><div>Marcel</div><div class="mb_sig"></div><blockquote class="history_container" type="cite" style="border-left-style:solid;border-width:1px; margin-top:20px; margin-left:0px;padding-left:10px;">
<p style="color: #AAAAAA; margin-top: 10px;">Am 30.04.2020 10:18:08 schrieb Marcel Taeumel <marcel.taeumel@hpi.de>:</p><div style="font-family:Arial,Helvetica,sans-serif"><div id="__MailbirdStyleContent" style="font-size: 10pt;font-family: Arial;color: #000000">
> ... <span style="font-family: Arial, Helvetica, sans-serif;font-size: 13px">having multiple, platformspecific ways really is against that spirit.</span><div><span style="font-family: Arial, Helvetica, sans-serif;font-size: 13px"><br></span></div><div><span style="font-family: Arial, Helvetica, sans-serif;font-size: 13px">So, in the long term, you want to get rid of Installer? Well, either that or fill it up to the current state of things. I did not argue that those Installer calls should be used in a cross-dialect setting. But it would help building things such as the PreferenceWizard.</span></div><div><span style="font-family: Arial, Helvetica, sans-serif;font-size: 13px"><br></span></div><div><span style="font-family: Arial, Helvetica, sans-serif;font-size: 13px">Best,</span></div><div><span style="font-family: Arial, Helvetica, sans-serif;font-size: 13px">Marcel</span></div><div class="mb_sig"></div><blockquote class="history_container" type="cite" style="border-left-style:solid;border-width:1px; margin-top:20px; margin-left:0px;padding-left:10px;">
<p style="color: #AAAAAA; margin-top: 10px;">Am 30.04.2020 10:13:07 schrieb Tobias Pape <das.linux@gmx.de>:</p><div style="font-family:Arial,Helvetica,sans-serif"><br>> On 30.04.2020, at 09:49, Marcel Taeumel <marcel.taeumel@hpi.de> wrote:<br>> <br>> > Because that would essentially be Metcallo itself.<br>> <br>> I think an additional way through the Installer protocol wouldn't hurt. Maybe "Installer metacello" could just return "Metacello new". Or directly map the #install call to Metacello in a custom InstallerMetacello as suggested:<br>> <br>> Installer metacello "returns a new InstallerMetacello"<br>> package: 'Xtreams'; "maps auto-magically to ConfigurationOfXtreams"<br>> install.<br><br>I'd really like to _not_ have that.<br><br>The very point of Metacello is that you can say <br><br>"Metacello new ..." on GemStone AND Squeak AND Pharo AND ...<br><br>and having multiple, platformspecific ways really is against that spirit.<br><br>Best regards<br> -Tobias <br><br></marcel.taeumel@hpi.de></div></blockquote>
</div></div></blockquote>
</div></body>