April 2015 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Spotter

by Aliaksei Syrel

Hi Ben, It's CMD+Shift+Right On Apr 5, 2015 2:23 AM, "Ben Coman" <btc(a)openinworld.com> wrote: > Just a note, I went back to an old image and really miss the Spotter > workflow. > > One thing, can you remind me how when it shows 5/30 implementors I get a > list of all 30? I'm sure I've done this before but can't remember. > Perhaps this means its not obvious and maybe should appear in a "How To > Use" section in the Release Notes. > > cheers -ben >

April 5, 2015

Spotter

by Ben Coman

Just a note, I went back to an old image and really miss the Spotter workflow. One thing, can you remind me how when it shows 5/30 implementors I get a list of all 30? I'm sure I've done this before but can't remember. Perhaps this means its not obvious and maybe should appear in a "How To Use" section in the Release Notes. cheers -ben

April 5, 2015

Re: [Pharo-dev] Who maintains Aconcagua & Chalten?

by Sean P. DeNigris

Hernan Wilkinson-3 wrote > I answer you in the morning, contact me directly if you did not get the > answer Hi Hernan, I emailed you a few times. I'm afraid my messages have either gotten trapped in your spam filter or I have the wrong address. Let me know... ----- Cheers, Sean -- View this message in context: http://forum.world.st/Who-maintains-Aconcagua-Chalten-tp4813575p4817606.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

April 4, 2015

Re: [Pharo-dev] Downloading the latest 40 Image -> Error

by Sven Van Caekenberghe

I think this has to do with CDN caching or cache invalidation. > On 04 Apr 2015, at 21:09, Max Leske <maxleske(a)gmail.com> wrote: > > Confirmed. > >> On 04 Apr 2015, at 20:46, HernÃ¡n Morales Durand <hernan.morales(a)gmail.com> wrote: >> >> FYI >> >> $ wget -O- get.pharo.org/40+vm | bash >> --2015-04-04 18:41:59-- http://get.pharo.org/40+vm >> Resolving get.pharo.org... 128.93.162.72 >> Connecting to get.pharo.org|128.93.162.72|:80... connected. >> HTTP request sent, awaiting response... 200 OK >> Length: 2885 (2.8K) [text/html] >> Saving to: `STDOUT' >> >> 100%[======================================>] 2,885 --.-K/s in 0.001s >> >> 2015-04-04 18:42:00 (2.54 MB/s) - written to stdout [2885/2885] >> >> Downloading the latest 40 Image: >> http://files.pharo.org/image/40/latest.zip >> [image.MJSoCf/image.zip] >> End-of-central-directory signature not found. Either this file is not >> a zipfile, or it constitutes one disk of a multi-part archive. In the >> latter case the central directory and zipfile comment will be found on >> the last disk(s) of this archive. >> unzip: cannot find zipfile directory in one of image.MJSoCf/image.zip or >> image.MJSoCf/image.zip.zip, and cannot find image.MJSoCf/image.zip.ZIP, >> period. >

April 4, 2015

Re: [Pharo-dev] Downloading the latest 40 Image -> Error

by Max Leske

Confirmed. > On 04 Apr 2015, at 20:46, HernÃ¡n Morales Durand <hernan.morales(a)gmail.com> wrote: > > FYI > > $ wget -O- get.pharo.org/40+vm <http://get.pharo.org/40+vm> | bash > --2015-04-04 18:41:59-- http://get.pharo.org/40+vm <http://get.pharo.org/40+vm> > Resolving get.pharo.org... 128.93.162.72 > Connecting to get.pharo.org <http://get.pharo.org/>|128.93.162.72|:80... connected. > HTTP request sent, awaiting response... 200 OK > Length: 2885 (2.8K) [text/html] > Saving to: `STDOUT' > > 100%[======================================>] 2,885 --.-K/s in 0.001s > > 2015-04-04 18:42:00 (2.54 MB/s) - written to stdout [2885/2885] > > Downloading the latest 40 Image: > http://files.pharo.org/image/40/latest.zip <http://files.pharo.org/image/40/latest.zip> > [image.MJSoCf/image.zip] > End-of-central-directory signature not found. Either this file is not > a zipfile, or it constitutes one disk of a multi-part archive. In the > latter case the central directory and zipfile comment will be found on > the last disk(s) of this archive. > unzip: cannot find zipfile directory in one of image.MJSoCf/image.zip or > image.MJSoCf/image.zip.zip, and cannot find image.MJSoCf/image.zip.ZIP, > period.

April 4, 2015

Downloading the latest 40 Image -> Error

by HernÃ¡n Morales Durand

FYI $ wget -O- get.pharo.org/40+vm | bash --2015-04-04 18:41:59-- http://get.pharo.org/40+vm Resolving get.pharo.org... 128.93.162.72 Connecting to get.pharo.org|128.93.162.72|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 2885 (2.8K) [text/html] Saving to: `STDOUT' 100%[======================================>] 2,885 --.-K/s in 0.001s 2015-04-04 18:42:00 (2.54 MB/s) - written to stdout [2885/2885] Downloading the latest 40 Image: http://files.pharo.org/image/40/latest.zip [image.MJSoCf/image.zip] End-of-central-directory signature not found. Either this file is not a zipfile, or it constitutes one disk of a multi-part archive. In the latter case the central directory and zipfile comment will be found on the last disk(s) of this archive. unzip: cannot find zipfile directory in one of image.MJSoCf/image.zip or image.MJSoCf/image.zip.zip, and cannot find image.MJSoCf/image.zip.ZIP, period.

April 4, 2015

Re: [Pharo-dev] UpdatedPharoByExample for 3.0, 4.0, 5.0

by Dmitri Zagidulin

I agree 100% that we should keep separate book versions for the corresponding Pharo versions. Specifically: - Use the 'master' branch for the current stable version (4.0). Basically, the way things are right now. This at least won't break existing CI jobs (tests and PDF generation). - Have a 3.0 and a 5.0 branch (or maybe just 5.0, going forward, if there's not enough demand or reason to do 3.0). - When time comes for 5.0 release, the 5 branch gets moved to master, and the previous master gets moved to a 4.0 branch. And so on. (Btw, I don't think it would make sense for us to use tags like 'Pharo-4-final', since the whole point about having a book under source control like that is that it's continuously improving. It makes sense to freeze software with tags (well, sort of, except you still end up making bugfix releases), but less so for books.) I think the time / energy investment problem that stepharo was mentioning has to do with: 1) setting up the Jenkins and Travis CI jobs for the various branches. Annoying, but at least it's just an initial effort (plus subsequent bursts of effort for each Pharo version branch). 2) porting new content (or even revisions) to multiple versions. So, if a new chapter is added to the 5.0 branch in the future, is it then a requirement to also back-port it to 4.0 (and 3.0, if we have it)? (And to do the resulting small tweaks to make sure the code still works for that version, change the screenshots and so on)? This is where most of the effort comes in, as I see it. The solution is probably in relaxed expectations. We could have an implicit (or even explicitly stated in the readme) policy that new revisions will only propagate from the current version upwards (but not backwards). Or, even simpler, just leave it up to individual contributors' motivations -- meaning, new revision comes in, we open up tickets to back-port it to previous versions, and if somebody cares enough to do it, it'll get ported. On Sat, Apr 4, 2015 at 10:19 AM, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > stepharo wrote > > there is a huge time / energy investment problems. > > I don't see it. The simplest thing (which is 0 extra work AFAICT) would be > to tag the last version before we start updating for 5.0 as something like > 'Pharo-4-final'. Almost as easy would be to have a branch per version, so > e.g. typos could be merged back if someone was interested. But maybe I'm > missing something - where specifically do you see the time & energy > investment? Because I think we could've set it up in less time than it took > me to write this reply! > > > > ----- > Cheers, > Sean > -- > View this message in context: > http://forum.world.st/UpdatedPharoByExample-for-3-0-4-0-5-0-tp4817514p48175… > Sent from the Pharo Smalltalk Developers mailing list archive at > Nabble.com. > >

April 4, 2015

Re: [Pharo-dev] VM and .sources in separate dirs question

by Dmitri Zagidulin

Ok, that's awesome. Thank you for explaining! On Sat, Apr 4, 2015 at 8:50 AM, Max Leske <maxleske(a)gmail.com> wrote: > > On 03 Apr 2015, at 19:02, Dmitri Zagidulin <dmitri(a)zagidulin.net> wrote: > > Do you happen to know how it does it? (I wouldn't know where to look, in > the source code). Does it still work if you move the sources to another > directory, from your current one? Does Pharo do a whole-disk search every > time? (Or just when it doesn't find them?) > > On Fri, Apr 3, 2015 at 12:00 PM, Max Leske <maxleske(a)gmail.com> wrote: > >> >> On 03 Apr 2015, at 17:55, Dmitri Zagidulin <dmitri(a)zagidulin.net> wrote: >> >> On Fri, Apr 3, 2015 at 11:49 AM, Max Leske <maxleske(a)gmail.com> wrote: >>> >>> > that you can keep the VM and .sources in different directories? How do >>> you tell the VM where to locate the sources? >>> >>> You donât. Itâs detected automagically! >>> >> >> Wait, how does it know which .sources file to pick? :) What if there are >> .sources from multiple versions of Pharo, etc, lying around on the hard >> drive? >> >> > No, Pharo wonât search your disk, that would take way too long. Basically, > the image tries to find the sources in two places: > 1. the image directory > 2. the vm directory > > In reality Pharo tries to do a bit more. The places Pharo looks in are > listed in OSPlatform>>potentialLocationsOfSourcesFile (and subclasses). > > See also PharoFilesOpener>>openSources. > > Note that the Pharo implementation has probably diverged a bit from the > one that Squeak uses / used to use. > > Cheers, > Max > > >> >> The image decides which sources file it needs. I have all of mine in a >> single directory with all the different VMs. Works like a charm. >> > > >

April 4, 2015

Re: [Pharo-dev] UpdatedPharoByExample for 3.0, 4.0, 5.0

by Sean P. DeNigris

stepharo wrote > there is a huge time / energy investment problems. I don't see it. The simplest thing (which is 0 extra work AFAICT) would be to tag the last version before we start updating for 5.0 as something like 'Pharo-4-final'. Almost as easy would be to have a branch per version, so e.g. typos could be merged back if someone was interested. But maybe I'm missing something - where specifically do you see the time & energy investment? Because I think we could've set it up in less time than it took me to write this reply! ----- Cheers, Sean -- View this message in context: http://forum.world.st/UpdatedPharoByExample-for-3-0-4-0-5-0-tp4817514p48175… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

April 4, 2015

Re: [Pharo-dev] Brand new modern Spotter design!

by stepharo

doru it would be fun to have an even redder GTSpotter and some colored windows In a dark background it can be really "efficient" :) Stef Le 3/4/15 18:27, Tudor Girba a Ã©crit : > I wonder :) > > Doru > > On Fri, Apr 3, 2015 at 3:14 PM, Sven Van Caekenberghe <sven(a)stfx.eu > <mailto:sven@stfx.eu>> wrote: > > Maybe the color is an April 1st joke ? > > > On 03 Apr 2015, at 10:30, Tudor Girba <tudor(a)tudorgirba.com > <mailto:tudor@tudorgirba.com>> wrote: > > > > Universal :)))) > > > > Doru > > > > On Fri, Apr 3, 2015 at 9:47 AM, Stephan Eggermont > <stephan(a)stack.nl <mailto:stephan@stack.nl>> wrote: > > On 01/04/15 11:53, Tudor Girba wrote: > > Nah, you have to experience it first hand yourself. It's too cool to > > experience it via a dead picture. > > > > On wednesday we used it in the devnology workshop. > > It just works, no participants had any remarks :) > > > > Stephan > > > > > > > > > > > > > > -- > > www.tudorgirba.com <http://www.tudorgirba.com> > > > > "Every thing has its own flow" > > > > > > -- > www.tudorgirba.com <http://www.tudorgirba.com> > > "Every thing has its own flow"

April 4, 2015