On 8/6/15, Mariano Martinez Peck <marianop...@gmail.com> 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.
Simple and efficient indeed! +1 > > > > On Thu, Aug 6, 2015 at 7:13 PM, Sebastian Heidbrink <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 >
