Very cool! I think the quickstart section would benefit from an example such as loading icons or a test resource (mse file for moose).
Also, can you explain how updating a Readme.md would work using GitBridge? I assume it would be modified with a text editor in Pharo then Iceberg will see the changes to commit them? Sorry if I'm reading too much into it. On Tue, Jul 16, 2019, 22:40 Tomohiro Oda <[email protected]> wrote: > Cyril, > > Awesome! > I've been wanting to make something like this for my project. > Great thanks! > --- > tomo > > 2019年7月17日(水) 5:07 Cyril Ferlicot D. <[email protected]>: > > > > Hi! > > > > Today I released the v1 of a project I wanted to do since a long time: > > GitBridge. > > > > The goal of the project is to easily access external resources stored in > > the git repository of the project and other information. > > > > For more infos check the Quick start or documentation present at: > > https://github.com/jecisc/GitBridge > > > > When Monticello was the most common VCS usable with Pharo we stored a > > lot of external resources in the image. Now we are able to store them > > outside, get a lighter image and make it easier to edit and version them! > > > > This can be useful to store test resources, CSS/JS files for web > > applications, documentation, etc. > > > > This can also be useful to get from the application some information > > such as the current version of the application instead of hard-coding it > > in a method to update at each release. > > > > It implementation relies on Iceberg and the repositories registered in > it. > > > > -- > > Cyril Ferlicot > > https://ferlicot.fr > > > >
