On Wed, Jul 17, 2019 at 4:59 PM Alexandre Bergel via Pharo-users <pharo-users@lists.pharo.org> wrote: > > Thanks Cyril, > > This look awesome. A quick question: to access external resources, I usually > use the expression (that you provide me some times ago) > > repo := (IceRepository registry detect: [ :each | each includesPackageNamed: > 'GeneticAlgorithm' ] ifNone: [ self error: 'Please add a clone of this > project to Iceberg to access to the resources' ]) location. > > In this case, I can use some resources located in the git repository of the > GeneticAlgorithm project. Eg. repo / ‘my image.png’ > > What does GitBridge bring more than that? I feel I miss something obvious... >
Well, it is mostly that. If you check the implementation it uses the same kind of expression. What it bring more is to factorise the code to do it (Like this if Iceberg change I just need to update GitBridge and all projects using it will be fixed). It also brings methods such as #version that can be useful and I hope we will add useful things to it to avoid everyone duplicating their own version in their project. Last thing is that the API is clear. For example you can just do: `GABridge images` instead of the whole detect on the Iceberg registry. > Cheers, > Alexandre > > > -- Cyril Ferlicot https://ferlicot.fr
