Re: [Pharo-users] Why doesn't Pharo 7 Iceberg write changes to the git filesystem as you go?

On 22 May 2018 at 23:23, Tim Mackinnon wrote: > Hi - when trying out the new Iceberg with a bunch of developers and > explaining the challenges of integrating git and files into a smalltalk > realm of the image - there was a lot of interest in how this works. > > When you clone

Re: [Pharo-users] Why doesn't Pharo 7 Iceberg write changes to the git filesystem as you go?

Esteban A. Maringolo wrote > there is no way to "save" the package other than committing its changes to > the repo. In the past, I sorely missed a feature like this. When Iceberg (or I!) was confused about the state of the local repo/changes/whatever, I wished I had a way to write to disk and

Re: [Pharo-users] Pharo 7 - New Iceberg feedback

Tim Mackinnon wrote > Although possibly calling it “Commit…” might make it more obvious that you > have a chance to review changes and change your mind +1. This minor change would IMHO make things much more obvious, especially to people unfamiliar with git… - Cheers, Sean -- Sent from:

Re: [Pharo-users] Why doesn't Pharo 7 Iceberg write changes to the git filesystem as you go?

Actually I missed that one - thanks. Would have been a useful one to show everyone when we went through the commit process - it’s very good. Sent from my iPhone Sent from my iPhone > On 22 May 2018, at 17:16, Sven Van Caekenberghe wrote: > > Partial answer, but you saw this,

Re: [Pharo-users] Pharo 7 - New Iceberg feedback

The community has invested a lot in a new way of working - I’ve seen the pain, but I think it’s both inspiring , a difficult journey but ultimately well worth it. We need to finish this first leg though, but I’m still very proud to be a smalltalker ... Sent from my iPhone > On 22 May 2018,

Re: [Pharo-users] Why doesn't Pharo 7 Iceberg write changes to the git filesystem as you go?

I agree with you that it is weird, but as I understand it it is because the process of "Saving" a package and "Committing" it is merged into a single action, so there is no way to "save" the package other than committing its changes to the repo. This has the drawback you mentioned, but I guess

Re: [Pharo-users] Why doesn't Pharo 7 Iceberg write changes to the git filesystem as you go?

Partial answer, but you saw this, right ? https://github.com/pharo-vcs/iceberg/wiki/Iceberg-glossary > On 22 May 2018, at 17:23, Tim Mackinnon wrote: > > Hi - when trying out the new Iceberg with a bunch of developers and > explaining the challenges of integrating git and

[Pharo-users] Why doesn't Pharo 7 Iceberg write changes to the git filesystem as you go?

Hi - when trying out the new Iceberg with a bunch of developers and explaining the challenges of integrating git and files into a smalltalk realm of the image - there was a lot of interest in how this works. When you clone - you obviously see a series of files (in Tonel - nice) that are then

Re: [Pharo-users] Pharo 7 - New Iceberg feedback

Hi Tim, Thanks for the detailed/constructive feedback. I am sure it will be helpful. Sven > On 22 May 2018, at 17:15, Tim Mackinnon wrote: > > Hi - last night we managed to explore the new contribution process as well as > the new iceberg ui at the U.K. Smalltalk meetup

[Pharo-users] Pharo 7 - New Iceberg feedback

Hi - last night we managed to explore the new contribution process as well as the new iceberg ui at the U.K. Smalltalk meetup last night. Not many had seen it before so it was a good test run. As an initial comment - we need to invest a small amount of time to get the right docs in places you

Re: [Pharo-users] [TechTalk] TODAY, 17h: Pillar

> On 17 May 2018, at 15:44, Marcus Denker wrote: > > Hi, > > Today, 17h europe time. > > Pharo TechTalk: Pillar > https://association.pharo.org/event-2797069 > > Sorry for the late announcement (we did not know if we could make it today) > The recording is

Re: [Pharo-users] On UDP broadcast

HilaireFernandes wrote > Thanks Sven for the indications. > > Of course I already looked at this Test, but I got lost. I looked at it > again, and wrote something like: > > | socket data | socket := Socket newUDP. socket setPort: . > socket waitForConnectionFor: 2; waitForDataFor: 5

Re: [Pharo-users] [Pharo-dev] LibFFI/NB Cairo External Module Not Found debugging

why libcairo2-dev and not just libcairo2? cheers, Esteban > On 21 May 2018, at 17:25, Richard O'Keefe wrote: > > Thank you for that. The instructions there are incomplete. > It is necessary to add > sudo apt-get install libcairo2-dev:i386 > to the script. > > On 21 May 2018