[Vm-dev] Fwd: Materializing BlockClosure's outerContext?

Jakob Reschke forums.jakob at resfarm.de
Sat Jan 5 16:58:04 UTC 2019


Hi Eliot,

Am Sa., 5. Jan. 2019 um 16:48 Uhr schrieb Eliot Miranda <
eliot.miranda at gmail.com>:

>
> Great news.  Thank you!  Could you post yo the list the exact load
> expression you used to load Scorching.  Also post how you update the Tonel
> code.  I am so excited!  I want this so badly :-). Thank you!!
>

It is not an integrated workflow yet. I cloned the Scorch repository using
the git command line:
    git clone https://github.com/clementbera/Scorch.git
Then, with the Tonel port loaded,
    Installer ensureRecentMetacello.
    (Smalltalk classNamed: #Metacello) new
      repository: 'github://j4yk/tonel:squeak';
      baseline: 'Tonel';
      load.
you can add tonel:// repositories in the Monticello browser.
Choose the "repository" subdirectory of the Scorch clone there, as in the
"old days" with FileTree.
Then you can open the Monticello Tonel repository, it should list the
Scorching packages each with -tonel.1 as the version indication, and load
the packages as usual.
As with metadata-less FileTree, you won't have any history in Monticello.
The history is only in Git.
To store back in Tonel format, save the packages with Monticello to the
Tonel repository. Then commit with Git to actually make it a version.
I still have to do the integration with the "Git browser" tool and the
underlying framework of it, which you can install via the Do menu, just
like I still haven't had time to look into the proper cooperation with
Metacello yet. Once that is done, I shall post a more discoverable
announcement (not hidden in another thread) on squeak-dev.

Also note that there won't be any method timestamps. I suppose in
Pharo/Iceberg they are derived from the Git history, so the timestamps are
not stored with the code.

Best,
Jakob

>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.squeakfoundation.org/pipermail/vm-dev/attachments/20190105/6b03bb83/attachment.html>


More information about the Vm-dev mailing list