April 2014 - Pharo-users - lists.pharo.org

Error: No factory specified

by Esteban A. Maringolo

I'm trying to load a Metacello Configuration I use in Pharo 2 into a brand new Pharo 3 image. However I'm getting an error when attempting to load it, and it opens the emergency evaluator. In the console I see following stack, which repeats over and over: LRUCache(Object)>>error: LRUCache(Cache)>>at: ScrollBar class>>arrowOfDirection:size:color: ScrollBar>>upImage ScrollBar>>updateUpButtonImage ScrollBar>>initializeUpButton ScrollBar>>initializeSlider ScrollBar(Slider)>>extent: ScrollBar>>extent: ScrollBar(Morph)>>bounds: MorphTreeMorph(ScrollPane)>>hResizeScrollBar MorphTreeMorph(ScrollPane)>>resizeScrollBars MorphTreeMorph(ScrollPane)>>hideOrShowScrollBars MorphTreeMorph(ScrollPane)>>setScrollDeltas MorphTreeMorph>>adjustSubmorphPositionsOf:startIdx:startPos: MorphTreeMorph>>adjustSubmorphPositions MorphTreeMorph>>innerWidgetChanged MorphTreeMorph>>privateUpdateColumnMorphs MorphTreeMorph>>updateColumnMorphs MorphTreeMorph>>addSubmorphsFromNodeList:previouslyExpanded: MorphTreeMorph>>updateContentsWithPreviouslyExpanded: MorphTreeMorph>>updateList MorphTreeMorph>>update: PackageTreeModel(Object)>>changed: in Block: [ :aDependent | aDependent update: aParameter ] DependentsArray>>do: PackageTreeModel(Object)>>changed: PackageTreeNautilusUI>>updatePackageView PackageTreeNautilusUI(AbstractNautilusUI)>>mcWorkingCopyCreated: WeakMessageSend>>value: WeakMessageSend>>cull: Error: No factory specified Any clues? Esteban A. Maringolo

April 8, 2014

Re: [Pharo-users] [ANN] JNIPort for Pharo 3.0 alpha

by Pharo4Stef

In VW there is the concept of object bodies and head now we will eventually have that with Spur. Maybe clement explained it somewhere in his blog (I understood the point once and of course I forgot). Now I wonder what changed so much between 1.2 and 3.0 > >> Yes, #become: is *very* slow in Pharo. No problem at all in VisualWorks or Dolphin Smalltalk or Pharo 1.2, though! >> >> Time millisecondsToRun: [1000 timesRepeat: [String new become: String new ]] >> >> Pharo 3.0 (and also in 2.0 and 1.4): >> 3948 3495 2891 2532 3162 >> >> Pharo 1.2 with the Squeak 4.2.5beta1U VM: >> 90 89 82 90 72 >> >> VisualWorks 7.9.1: note that this is measured in microseconds: >> Time microsecondsToRun: [1000 timesRepeat: [String new become: String new ]] >> 211 208 222 212 208 > > Yes, this is an extreme difference. > > On my machine, the above takes between 1 and 2 seconds in Pharo 3 (Pharo VM) and Squeak 4.5 (Cog VM), while VW 7.1 takes just 100 to 200 microseconds. > > Normally, #become: has to iterate over all memory, but this benchmark is a bit special, since it involves two new objects, maybe VW's memory manager somehow optimises this away. > > Sven

April 8, 2014

Pharo Consortium: New Bronze Member Ta MÃ¨re

by Marcus Denker

The Pharo Consortium is very happy to announce that Ta MÃ¨re has joined the Consortium as a Bronze Industrial Member. More about - Ta MÃ¨re: http://tamere.eu - Pharo Consortium: http://consortium.pharo.org The goal of the Pharo Consortium is to allow companies to support the ongoing development and future of Pharo. Individuals can support Pharo via the Pharo Association: http://association.pharo.org

April 8, 2014

Bug in SSL

by Norbert Hartl

As you might know a sever bug in the openssl library har been reported to the public. This bug is pretty nasty and allows in an easy fashion to access protected data. Please consider upgrading your products and operating systems to a fixed version of openssl. https://www.openssl.org/news/secadv_20140407.txt regards, Norbert

April 8, 2014

Re: [Pharo-users] [ANN] WIP iStoa

by Hilaire Fernandes

Le 07/04/2014 10:01, Bernat Romagosa a Ã©crit : > Just FYI, I had to replace the shipped vm and plugins by the latest ones > to get it to work on my Debian Wheezy machine. But wait, how come more recent VM work for you and not a bit older one (a few months)? Indeed I used a stock VM coming with Pharo3 linux distribution. The problem comes from GLIBC with hardlink dependencies to 2.15. $ objdump -T iStoa.app/bin/pharo | grep GLIBC_2.15 00000000 DF *UND* 00000000 GLIBC_2.15 __fdelt_chk Therefore I will be curious about objdump -T iStoa.app/bin/pharo | grep __fdelt_chk in your vm. Then what about dpkg -l | grep libc6 I don't understand much why and how there are multiple glibc version dependencies. Thanks a lot. Hilaire -- Dr. Geo http://drgeo.eu

April 8, 2014

Re: [Pharo-users] [ANN] BabyMock 2

by Christophe Demarey

Hello, Thanks. Very nice library! I have a question: is it possible to expect a method to throw an Exception? I would like something like: protocol describe once: mock recv: #aMethod ; signal: anError. I did not find anything in the documentation. I don't want to test that the mock signals an error but I want to test a code that needs to take into account an exception. Best regards, Christophe. Le 11 mars 2014 Ã 12:30, Attila Magyar a Ã©crit : > I'm pleased to announce the 2.0 version of BabyMock. BabyMock is a visual > mock object library that supports test-driven development. > > This version has a new syntax which is incompatible with the old version. > Therefore it has a new repository > http://smalltalkhub.com/#!/~zeroflag/BabyMock2 > (BabyMock 1 is still available at its old location, but in the future I'd to > focus on the development of BabyMock2, so don't expect too many changes > regarding the old version). > > Changes in 2.0 > > - A new, extensible DSL (no more should/can) > - Improved error messages, history of messages, detailed information about > argument mismatches > - An improved, Spec based GUI > - Clicking on a mock opens an inspector on the expectations > - Clicking on a message opens an inspector on the message > - Object methods can be mocked by defaults > - Blocks can be executed after receiving a message by the mock. The block > has access to the arguments of the incoming message. > - Any argument matcher > - Cleanups and simplifications in the code > > I hope you don't mind the changes regarding the syntax. Personally I think > it has lot more pros than cons. > > More information > > http://smalltalkhub.com/#!/~zeroflag/BabyMock2 > > p.s. > It needs Pharo3.0. > > Attila > > > > -- > View this message in context: http://forum.world.st/ANN-BabyMock-2-tp4748530.html > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. >

April 8, 2014

Re: [Pharo-users] [ANN] JNIPort for Pharo 3.0 alpha

by Sven Van Caekenberghe

On 05 Apr 2014, at 23:35, Joachim Geidel <joachim.geidel(a)onlinehome.de> wrote: > Yes, #become: is *very* slow in Pharo. No problem at all in VisualWorks or Dolphin Smalltalk or Pharo 1.2, though! > > Time millisecondsToRun: [1000 timesRepeat: [String new become: String new ]] > > Pharo 3.0 (and also in 2.0 and 1.4): > 3948 3495 2891 2532 3162 > > Pharo 1.2 with the Squeak 4.2.5beta1U VM: > 90 89 82 90 72 > > VisualWorks 7.9.1: note that this is measured in microseconds: > Time microsecondsToRun: [1000 timesRepeat: [String new become: String new ]] > 211 208 222 212 208 Yes, this is an extreme difference. On my machine, the above takes between 1 and 2 seconds in Pharo 3 (Pharo VM) and Squeak 4.5 (Cog VM), while VW 7.1 takes just 100 to 200 microseconds. Normally, #become: has to iterate over all memory, but this benchmark is a bit special, since it involves two new objects, maybe VW's memory manager somehow optimises this away. Sven

April 8, 2014

Re: [Pharo-users] [ANN] WIP iStoa

by Bernat Romagosa

Hi Hilarie, this is the error message I get: (...)/iStoa.app/bin/pharo: /lib/i386-linux-gnu/i686/cmov/libc.so.6: version `GLIBC_2.15' not found (required by (...)/iStoa.app/bin/pharo) And this is the output of ldd -v on the vm I used to run iStoa: linux-gate.so.1 => (0xb77b1000) libm.so.6 => /lib/i386-linux-gnu/i686/cmov/libm.so.6 (0xb7774000) libdl.so.2 => /lib/i386-linux-gnu/i686/cmov/libdl.so.2 (0xb7770000) libpthread.so.0 => /lib/i386-linux-gnu/i686/cmov/libpthread.so.0 (0xb7756000) libc.so.6 => /lib/i386-linux-gnu/i686/cmov/libc.so.6 (0xb75f2000) /lib/ld-linux.so.2 (0xb77b2000) Version information: /home/bromagosa/Smalltalks/Pharos/vm/latest/pharo: libdl.so.2 (GLIBC_2.1) => /lib/i386-linux-gnu/i686/cmov/libdl.so.2 libdl.so.2 (GLIBC_2.0) => /lib/i386-linux-gnu/i686/cmov/libdl.so.2 libpthread.so.0 (GLIBC_2.1) => /lib/i386-linux-gnu/i686/cmov/libpthread.so.0 libpthread.so.0 (GLIBC_2.0) => /lib/i386-linux-gnu/i686/cmov/libpthread.so.0 libm.so.6 (GLIBC_2.1) => /lib/i386-linux-gnu/i686/cmov/libm.so.6 libm.so.6 (GLIBC_2.0) => /lib/i386-linux-gnu/i686/cmov/libm.so.6 libc.so.6 (GLIBC_2.4) => /lib/i386-linux-gnu/i686/cmov/libc.so.6 libc.so.6 (GLIBC_2.3) => /lib/i386-linux-gnu/i686/cmov/libc.so.6 libc.so.6 (GLIBC_2.1) => /lib/i386-linux-gnu/i686/cmov/libc.so.6 libc.so.6 (GLIBC_2.11) => /lib/i386-linux-gnu/i686/cmov/libc.so.6 libc.so.6 (GLIBC_2.3.4) => /lib/i386-linux-gnu/i686/cmov/libc.so.6 libc.so.6 (GLIBC_2.1.3) => /lib/i386-linux-gnu/i686/cmov/libc.so.6 libc.so.6 (GLIBC_2.2) => /lib/i386-linux-gnu/i686/cmov/libc.so.6 libc.so.6 (GLIBC_2.0) => /lib/i386-linux-gnu/i686/cmov/libc.so.6 /lib/i386-linux-gnu/i686/cmov/libm.so.6: ld-linux.so.2 (GLIBC_PRIVATE) => /lib/ld-linux.so.2 libc.so.6 (GLIBC_2.1.3) => /lib/i386-linux-gnu/i686/cmov/libc.so.6 libc.so.6 (GLIBC_PRIVATE) => /lib/i386-linux-gnu/i686/cmov/libc.so.6 libc.so.6 (GLIBC_2.0) => /lib/i386-linux-gnu/i686/cmov/libc.so.6 /lib/i386-linux-gnu/i686/cmov/libdl.so.2: ld-linux.so.2 (GLIBC_PRIVATE) => /lib/ld-linux.so.2 libc.so.6 (GLIBC_PRIVATE) => /lib/i386-linux-gnu/i686/cmov/libc.so.6 libc.so.6 (GLIBC_2.1.3) => /lib/i386-linux-gnu/i686/cmov/libc.so.6 libc.so.6 (GLIBC_2.1) => /lib/i386-linux-gnu/i686/cmov/libc.so.6 libc.so.6 (GLIBC_2.0) => /lib/i386-linux-gnu/i686/cmov/libc.so.6 /lib/i386-linux-gnu/i686/cmov/libpthread.so.0: ld-linux.so.2 (GLIBC_2.1) => /lib/ld-linux.so.2 ld-linux.so.2 (GLIBC_PRIVATE) => /lib/ld-linux.so.2 ld-linux.so.2 (GLIBC_2.3) => /lib/ld-linux.so.2 libc.so.6 (GLIBC_2.3.2) => /lib/i386-linux-gnu/i686/cmov/libc.so.6 libc.so.6 (GLIBC_2.1.3) => /lib/i386-linux-gnu/i686/cmov/libc.so.6 libc.so.6 (GLIBC_2.1) => /lib/i386-linux-gnu/i686/cmov/libc.so.6 libc.so.6 (GLIBC_PRIVATE) => /lib/i386-linux-gnu/i686/cmov/libc.so.6 libc.so.6 (GLIBC_2.0) => /lib/i386-linux-gnu/i686/cmov/libc.so.6 libc.so.6 (GLIBC_2.2) => /lib/i386-linux-gnu/i686/cmov/libc.so.6 /lib/i386-linux-gnu/i686/cmov/libc.so.6: ld-linux.so.2 (GLIBC_2.3) => /lib/ld-linux.so.2 ld-linux.so.2 (GLIBC_PRIVATE) => /lib/ld-linux.so.2 ld-linux.so.2 (GLIBC_2.1) => /lib/ld-linux.so.2 Cheers, Bernat. 2014-04-07 21:29 GMT+02:00 Hilaire Fernandes <hilaire.fernandes(a)gmail.com>: > Hello, > > Can you tell me the error message you get when executing from a terminal? > > Also I am curious about the output you get from your latest VM with this > command: > > ldd -v bin/pharo > > Thanks > > Hilaire > > Le 07/04/2014 10:01, Bernat Romagosa a Ã©crit : > > Very nice, Hilarie! > > > > Just FYI, I had to replace the shipped vm and plugins by the latest ones > > to get it to work on my Debian Wheezy machine. > > > > Congrats! > > > > > > 2014-04-05 18:20 GMT+02:00 Hilaire Fernandes > > <hilaire.fernandes(a)gmail.com > > <mailto:hilaire.fernandes@gmail.com>>: > > > > Hello, > > > > For those who want to give a try to work in progress iStoa on Linux, > an > > Interactive math exercises book. > > > > > https://launchpad.net/istoa/alpha/14.04/+download/iStoa.app-14.04a.zip > > > > Hilaire > > > > -- > > Dr. Geo http://drgeo.eu > > > > > > > > > > > > -- > > Bernat Romagosa. > > -- > Dr. Geo http://drgeo.eu > > > -- Bernat Romagosa.

April 8, 2014

Re: [Pharo-users] Use of FileDialogWindow : getting the result

by Thomas Bany

> > Why do you need a dialog window in fullscreen size, if it is modal anyway > ? > Actualy, I need it to be fullscreen. I mentioned a dialog window because I was only able to retrieve the answer this way but I don't want a dialog window :) > Have you tried FileList (it isn't fullscreen, and doesn't look as nice as > the FileDialogWindow, but maybe it is easier to hack around with.) > > FileList modalFolderSelector: FileSystem disk workingDirectory > Well I think it looks better than my shrank version, I will look into it !

April 8, 2014

Re: [Pharo-users] Compiler evaluate: -> Smalltalk evaluate:

by Marcus Denker

On 07 Apr 2014, at 14:02, Sergi Reyner <sergi.reyner(a)gmail.com> wrote: > 2014-04-07 11:51 GMT+01:00 Marcus Denker <marcus.denker(a)inria.fr>: > In 4.0, we will remove the old compiler and then we can see how to make the API perfect. > > Will it be able to decompile by then? > Yes, we will solve that problem, too. Marcus

April 8, 2014