August 2017 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] [ANN] Pharo 6.1 (summer) released!

by Marcus Denker

> On 18 Aug 2017, at 09:56, Marcus Denker <marcus.denker(a)inria.fr> wrote: > >> >> What I think would have been good is to list all the updates that where done between >> releasing 6.0 and 6.1 *as part of the changelog* of 6.1 (even though they were already >> in the image that you got a minute before Pharo6.1 was released, as they where released as >> hot fixes before). >> > > The changelog of things done between releasing 6.0 and the release of 6.1: > I added a link to the complete changeling to http://pharo.org/news/pharo6.1-released <http://pharo.org/news/pharo6.1-released> Marcus

Aug. 22, 2017

Re: [Pharo-dev] 19609 FileReference>>base should be before last separator

by Stephane Ducasse

Thanks Alistair. On Thu, Aug 17, 2017 at 5:50 PM, Alistair Grant <akgrant0710(a)gmail.com> wrote: > Hi Stef, > > On Thu, Aug 17, 2017 at 05:08:40PM +0200, Stephane Ducasse wrote: >> I do not know but I imagine that I added basenameWithoutExtension because >> I found the name much much clearer. I would have never guessed that >> base is the basename without the extension. >> >> Stef > > Thanks for the clarification. Although #base isn't the name without the > extension, it is the portion of the name up to the first extension > delimiter (for names with a single extension delimiter the two will of > course be the same, but for names with multiple extension delimiters > they will be different). > > In that case, assuming no one else comes up with additional > information, I would argue that the issue should be closed (rejected), > and Michael should change his code to use #basenameWithoutExtension > instead of #base. > > It would be nice to improve the comments in the code - I'll add it to my > list. :-) > > > Cheers, > Alistair > > >> On Wed, Aug 16, 2017 at 9:46 PM, Alistair Grant <akgrant0710(a)gmail.com> wrote: >> > Hi All, >> > >> > I've just taken a look at issue 19609 FileReference>>base should be >> > before last separator and wonder whether it is a correct interpretation >> > of the original intentions. >> > >> > The original author of the issue, Michael, seems to feel that >> > FileReferene>>base and FileReference>>basenameWithoutExtension are the >> > same. >> > >> > My reading of the comments is that they perform a different function, >> > i.e.: >> > >> > >> > '/a/b/c.d.e' asFileReference base. "c" >> > '/a/b/c.d.e' asFileReference basenameWithoutExtension. "c.d" >> > >> > >> > are both the expected values, i.e.: >> > >> > - #base answers the name up to the first extensionDelimiter. >> > - #basenameWithoutExtension answers the name without what is typically >> > considered the file extension (the bit after the last >> > extensionDelimiter). >> > >> > Not shown above, but: >> > >> > - #basename answers the entire filename, i.e. "c.d.e". >> > >> > >> > Does anyone know the history of these methods? >> > >> > >> > Cheers, >> > Alistair >> > >> >

Aug. 22, 2017

Re: [Pharo-dev] Launcher Opening Tiny Windows

by Stephane Ducasse

Yes I experienced this problem too. I have the impression that during the build the size of the window are messed up. Stef On Sun, Aug 20, 2017 at 2:44 AM, Tim Mackinnon <tim(a)testit.works> wrote: > It's a known problem for any image that was saved in headless mode (not just launcher) - we should find a way to resolve this. > > Tim > > Sent from my iPhone > >> On 20 Aug 2017, at 00:35, Sean P. DeNigris <sean(a)clipperadams.com> wrote: >> >> Check out this screenshot. >> <http://forum.world.st/file/n4962615/Screenshot_2017-08-19_19.png> >> >> The red arrow points to an open "window" of a newly created Pharo 6.0 based >> image, minimized to the point of barely being visible. Clicking on it makes >> a title bar somewhat more visible, the edges of which can then be dragged as >> any other window. >> >> Anyone else seeing this? >> >> >> >> ----- >> Cheers, >> Sean >> -- >> View this message in context: http://forum.world.st/Launcher-Opening-Tiny-Windows-tp4962615.html >> Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >> > >

Aug. 22, 2017

Re: [Pharo-dev] Latest Debian, Ubuntu and CentOS packages of the pharo-vm

by Stephane Ducasse

Tx norbert I updated the blog post on pharoweekly. On Mon, Aug 21, 2017 at 11:18 AM, Norbert Hartl <norbert(a)hartl.name> wrote: > For the .deb based distributions the adding of the repo is missing. This would be for > > Ubuntu 16.04 > > echo "deb http://download.opensuse.org/repositories/devel:/languages:/pharo:/latest/x… ./" > /etc/apt/sources.list.d/pharo.list > > Ubuntu 14.04 > > echo "deb http://download.opensuse.org/repositories/devel:/languages:/pharo:/latest/x… ./" > /etc/apt/sources.list.d/pharo.list > > Debian 8 > > Ubuntu 16.04 > > echo "deb http://download.opensuse.org/repositories/devel:/languages:/pharo:/latest/D… ./" > /etc/apt/sources.list.d/pharo.list > > As nobody noticed I'm not sure if this is really needed ;) > > Feedback is highly appreciated! > > Norbert > >> Am 18.08.2017 um 11:54 schrieb Holger Freyther <holger(a)freyther.de>: >> >> Hi, >> >> when running Pharo in production you might want to install the image and a VM from distribution packages. So far there were no current public packages and during the last months I have modernized the debian packaging and recently added CentOS rpm packaging as well. The process of generating new source packages is integrated into the pharo-vm travis-ci build as well. >> >> Every time that master of pharo-vm.git is updated a new source package will be uploaded to the Open(SUSE) Build Service and new packages will be built and are available in a "latest" package feed. The generated (and used) sourcecode is inside the source package and will be archived by the OBS platform (one can even nicely diff versions). The "stable" VM is not built from pharo-vm.git (yet?) so it doesn't show on OBS yet. >> >> Below are some semi-tested installation notes in case you want to try it out. The binary names are picked to allow to install the 32bit and 64bit VM in parallel. The names currently are: >> >> - pharo6-32 (32bit version) >> - pharo6-64 (64bit version) >> - pharo6-32-ui (32bit version with X11 dependencies) >> - pharo6-64-ui (64bit version with X11 dependencies) >> >> >> CentOS 6.8: >> >> # Add the repo >> $ yum-config-manager --add-repo http://download.opensuse.org/repositories/devel:/languages:/pharo:/latest/C… >> >> # Install 32bit packages (with X11 dependency for *-ui or not) >> >> $ yum install pharo6-32-ui.i686 or pharo6-32.i386 >> >> # Install 64bit packages >> >> $ yum install pharo6-64-ui.x86_64 pharo6-64.x86_64 >> >> >> >> CentOS 7 (only 64bit): >> >> >> $ yum-config-manager --add-repo http://download.opensuse.org/repositories/devel:/languages:/pharo:/latest/C… >> $ yum install pharo6-64-ui.x86_64 pharo6-64.x86_64 >> >> >> Debian 8: >> >> # Add signing key >> $ wget -O - http://download.opensuse.org/repositories/devel:/languages:/pharo:/latest/D… | apt-key add - >> >> # Update and install >> $ apt update >> $ apt install pharo6-32-ui pharo6-64-ui (or pharo6-32 or pharo6-64) >> >> Ubuntu 14.04 LTS >> >> # Add signing key >> $ wget -O - http://download.opensuse.org/repositories/devel:/languages:/pharo:/latest/x… | apt-key add - >> >> # Update and install >> $ apt update >> $ apt install pharo6-32-ui pharo6-64-ui >> >> Ubuntu 16.04 >> >> # Add signing key >> $ wget -O - http://download.opensuse.org/repositories/devel:/languages:/pharo:/latest/x… | apt-key add - >> >> # Update and install >> $ apt update >> $ apt install pharo6-32-ui pharo6-64-ui >

Aug. 22, 2017

Re: [Pharo-dev] TechTalk Dates for the rest of 2017

by Alexandre Bergel

>> I'm not sure Pharo tech talk is the good place but would love to see such a presentation. >> > Why not? I am sure Alex will have some code in there.. " programming, from scratch, a small artificial intelligenceâ > if done with Pharo would be a very nice thing todo for the tech talk. Yes, that is the plan. It could be a very practical lecture, with a lot of coding (but not many lines of code). Alexandre > >> Maybe you can do a Google or Twitch live video about that ? >> > Yes, that at one of the pre-defined tech talk dates. > > Marcus > >

Aug. 22, 2017

[ Pharo 70 ] Build 52 PR 195 Make-SUnit-loadable-by-Hermes

by Marcus Denker

[ Pharo 70 ] Build 52 PR 195 Make-SUnit-loadable-by-Hermes https://pharo.fogbugz.com/f/cases/20306/Make-SUnit-loadable-by-Hermes https://github.com/pharo-project/pharo/pull/195

Aug. 22, 2017

[Wanted] Newsletter topics and "takeovers"

by Marcus Denker

Hi, As you for sure know, we have now a good monthly rhythm with the newsletter. http://us11.campaign-archive1.com/home/?u=6f667565c2569234585a7be77&id=0486… <http://us11.campaign-archive1.com/home/?u=6f667565c2569234585a7be77&id=0486…> And the number of subscribers is growing! If you have ideas for the next newsletters (August is done and will be posted soon, but we need content for September and laterâ¦) We need both small and larger items. Example for smaller news: - announcements of new libraries - new releasese - links to videos - links to blog posts And larger items. These have not just the title and link, but a short description and if possible a picture. (If you look at the older newsletters it should be clear what is needed). Another idea I had: we could even have âcomplete takeoverâ of a newsletter by someone who wants to edit a newsletter for one specific topic. This can be about one project, or just a âthemeâ (e.g. âcloud deployment with Pharoâ) if you are interested â> send a mail to board(a)pharo.org <mailto:board@pharo.org> Marcus

Aug. 22, 2017

Spotter references?

by Stephane Ducasse

Hi I tried Command Shift n to get the class references in Spotter I got #References Point but I got an empty list while if I do Point Cmd shift n I get a list Stef

Aug. 22, 2017

Re: [Pharo-dev] TechTalk Dates for the rest of 2017

by Marcus Denker

> On 21 Aug 2017, at 19:08, serge.stinckwich(a)gmail.com wrote: > > I'm not sure Pharo tech talk is the good place but would love to see such a presentation. > Why not? I am sure Alex will have some code in there.. " programming, from scratch, a small artificial intelligenceâ if done with Pharo would be a very nice thing todo for the tech talk. > Maybe you can do a Google or Twitch live video about that ? > Yes, that at one of the pre-defined tech talk dates. Marcus

Aug. 22, 2017

IMKClient Stall detected, *please Report* ??

by Tim Mackinnon

Iâve noticed that even in later 6.1 images I am seeing the following stall message on the console in OS X? IMKClient Stall detected, *please Report* your user scenario attaching a spindump (or sysdiagnose) that captures the problem - (imkxpc_attributesForCharacterIndex:reply:) block performed very slowly (4.57 secs). Is this something that is known or do I need to report it? This is with a pretty virgin zero conf image (in fact it may even be a fresh image). What is a spindump it refers to? Tim

Aug. 21, 2017