> On 2 Dec 2018, at 11:31, Hilaire <hila...@drgeo.eu> wrote:
>
> Hi Ichi,
>
> If you are learning Pharo I suggest you to not follow this way for now
> as it may result in cognitive overload and frustration.
Although the workflow described below does indeed work, it
(1) assumes you already know how to handle a classic VCS on the command line
(2) does not give you elementary diff tools in the IDE that understand your
programming language
So I don't think it is 'the (better) way to go'.
In my experience, using Iceberg in the image, combined with the GitHub Web UI
and the git command line tools, works really well, once you 'get' it. Yes,
there is a learning curve as with anything.
> If you just want to save your code on some repo, use Metacello to create
> a tonel repository, then do code revision the way you use to do it
> (command line, third party GUI application).
>
> Your workflow will be:
>
> 1. Create a tonel report from Monticello: click on '+Repository' and
> chose tonel://, then select the direcotory in your host to save the code.
>
> 2. On this repo do Add to package to add your code (hope it works in
> released P7, does not on my Pharo7.0-32bit-0c5ade3).
>
> 2. Do the code versioning in the way you use to do it and with the tool
> you want. (git, svn, bzr, CLI, GUI)
>
> 3. Each time you want to save code change, go to Monticello and save
> dirty package
>
> 4. make the commit with your versioning system
>
> Hilaire
>
>
> Le 01/12/2018 à 12:10, Ichiseki a écrit :
>> Hi,
>> You are not alone.
>> I have the same impression that Metacello+Git+Iceberg is something very
>> difficult to grasp.
>> It is getting hard to keep the pace with a constant evolving Pharo system.
>> best
>> ichi
>
> --
> Dr. Geo
> http://drgeo.eu
>
>
>
