On Thu, Aug 6, 2015 at 7:43 PM, Sebastian Heidbrink <shei...@yahoo.de> wrote:
> Hi Mariano, > > that is what I do, too. > I mean a case where I sit next to somebody and he uses his own computer > and we dabble around. > After a while one sometimes want to just provide the other with some > snippets or classes just implemented. > > Email and USB stick are not always an option... > > OK, I see now. So for that what I do is that I have a "MarianoSandbox" repository in Shub which is public write access and I simply commit there... But I don't remember if even if the project is public write, if someone would still need a Shub user, which in your case would not be fun. Cheers, > Sebastian > > > > On 2015-08-06 3:17 PM, Mariano Martinez Peck wrote: > > Something I do since years is to have my own cross-image-shared package > cache or explicit directory-based monticello repository (added to your > projects) where I have everything. Then, you can simply commit to your > local directory based monticello report and load it in the other > image..quite simple. > > > > > On Thu, Aug 6, 2015 at 7:13 PM, Sebastian Heidbrink < <shei...@yahoo.de> > shei...@yahoo.de> wrote: > >> Hi again, >> >> I find my self more and more often showing others Pharo and very often it >> might be great to just push code changes from one image directly to another. >> >> Is there a in-image monticello server available that would mimic a >> repository server? >> >> I already thought about webannouncements as a solution to broadcast/push >> code within the network. >> Or a shared remote playground that keeps a websocket connection between >> images and would provide an easy way to copy&paste snippets... >> >> @Stephan: How did you solve your latency issues with your remote >> introductions? Couldn't one just extend gui announcements by web >> announcements to remote control other images? >> >> Sebastian >> >> >> >> > > > -- > Mariano > http://marianopeck.wordpress.com > > > -- Mariano http://marianopeck.wordpress.com
