- Pharo-dev - lists.pharo.org

Concerts of Iron Maiden Analyzed
by Alexandre Bergel Jan. 6, 2014

Jan. 6, 2014

Load Roassal to enjoy Dowser, a relational tower visualization. The following expression relates the year and locations of Iron Maidenâs concerts: RODowserExample new example10 More Screenshots available on: https://www.facebook.com/media/set/?set=a.567893596630575.1073741840.340543… Thanks Ricardo for this excellent piece of work! Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

3 6

Re: [Pharo-dev] XMLParser Problem with SVG
by monty Jan. 6, 2014

Jan. 6, 2014

I saved lion.svg to my shared directory, and (XMLDOMParser parseFileNamed: 'lion.svg') worked fine. I am using the latest version. Are you using the latest version? Also, what type of error? File system related, parsing, network? What is your platform? ----- Original Message ----- From: J.F. Rick Sent: 01/05/14 09:19 AM To: Pharo Development List Subject: [Pharo-dev] XMLParser Problem with SVG I am trying to use SVG with Athens; however, the XMLParser for Pharo 3.0 cannot read normal SVG files that it used to. So, the demo of "ASVGMorph fromFile: 'lion.svg'" fails in the XMLParser (i.e., before ASVGMorph really does anything to it). It seems to download the DTD file from the Internet and then cannot properly parse it. Here is my setup: Up-to-date Pharo 3.0. Added XMLParser from the Configuration Browser.Example file can be found here: http://www.thetangentbundle.net/w/images/f/ff/lion.svg The following brings up an error: XMLDOMParser parseFileNamed: 'lion.svg' Cheers, Jeff -- Jochen "Jeff" Rick, Ph.D. http://www.je77.com/ Skype ID: jochenrick

1 0

Shortcuts for tools
by Nicolai Hess Jan. 5, 2014

Jan. 5, 2014

Can someone please comment on 12103 <https://pharo.fogbugz.com/default.asp?12103> shortcuts for tools. It just doesn't work for me. But having this shortcuts would be cool. Nicolai

1 0

issue 12506 Vm crashes vm when testing updates [A-L]
by Nicolai Hess Jan. 5, 2014

Jan. 5, 2014

My observations for issue 12506 - I can reproduce it on linux - segfault happens in primtiveNextInstance - tests A-L worked in 30663 - tests A-L segfault since 30664 - doesn't segfaults anymore if you open the image, change some code, save and close the image - it segfaults if you just run a subset of the A-L tests (pharo --nodisplay Pharo.image test --junit-xml-output 'FileSystem-Tests-Core' 'FreeTypeTests' 'FileSystem-Tests-Disk' 'FuelTests' 'FileSystem-Tests-Memory' 'KernelTests') - this "fail"-subset is different for the different images (30664, 30665, ...) - it does not segfault if you omit the junit-xml-output option And someone knows what happened with the image between version 30663 and 30666, because only 30664 and 30665 need the PharoV20.sources in the same directory as the VM, for all other versions it suffices if the sources are where the image file is. (Same as in http://forum.world.st/pharo-3-0-image-td4732890.html) Nicolai

3 5

what happened with RectangleMorph?
by Esteban Lorenzano Jan. 5, 2014

Jan. 5, 2014

â¦ is not there anymore. And Magritte-Morph requires it :( my guess: I was another victim of Stef compulsion of giving us a better and cleaning system :) But it should be replaced by what? Esteban

4 11

[pharo-project/pharo-core]
by GitHub Jan. 5, 2014

Jan. 5, 2014

Branch: refs/tags/30672 Home: https://github.com/pharo-project/pharo-core

1 0

[pharo-project/pharo-core] c01a1a: 30672
by GitHub Jan. 5, 2014

Jan. 5, 2014

Branch: refs/heads/3.0 Home: https://github.com/pharo-project/pharo-core Commit: c01a1a1b7aaeefa47df79071a6b67052f8a735b0 https://github.com/pharo-project/pharo-core/commit/c01a1a1b7aaeefa47df79071… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-01-05 (Sun, 05 Jan 2014) Changed paths: M Kernel.package/CompiledMethod.class/instance/literals/literalStrings.st M Kernel.package/CompiledMethod.class/instance/literals/sendsSelector_.st M Komitter.package/extension/MCPatch/instance/initializeWithTarget_.st M NewList.package/NewList.class/instance/protocol/cacheAt_.st M NewList.package/NewListAdapter.class/instance/accessing/separatorSelector.st M NewList.package/NewListAdapter.class/instance/list protocol/separatorAfter_at_.st M OpalCompiler-Core.package/OpalCompiler.class/instance/public access/evaluate.st A Polymorph-TaskbarIcons.package/extension/MorphicWindowAdapter/instance/taskbarIcon.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - scripts/script325.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - updates/update30672.st M ScriptLoader30.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 30672 12571 #evaluate should always #generateWithSource https://pharo.fogbugz.com/f/cases/12571 12562 NewList separatorAt bug fix https://pharo.fogbugz.com/f/cases/12562 12556 debugger is not showing correct icon in taskbar https://pharo.fogbugz.com/f/cases/12556 12563 Comments in CompiledMethod https://pharo.fogbugz.com/f/cases/12563 12564 Error in #initializeWithTarget: https://pharo.fogbugz.com/f/cases/12564 http://files.pharo.org/image/30/30672.zip

1 0

Jan. 5, 2014

Hi guys Iâm trying to build a ridiculously simple browser to be able to edit code when nothing else works. So just a list of classes and methods. No more. Doing so I fixed some issues in NewList and got blocked in PluggableListMorph mess. Now I saw that NewList depends on Spec (because it uses ValueHolders). So this prevents to build low level tools for minimal envrionment. I want to propose the following: I would like to have layers - elementary widgets should not depend on Spec - now since I like the valueHolder idea. I suggest that we we create a new package ValueHolders and move it outside of Spec. https://pharo.fogbugz.com/default.asp?12572 Stef

1 0

Unifying Testing Ideas
by Sean P. DeNigris Jan. 4, 2014

Jan. 4, 2014

We have some cool matchers (Phexample, StateSpecs), some nice mocking libraries (Mocketry, BabyMock), and Phexample's acknowledgement that tests build on each other. The problem is, it's hard to cherry-pick and build one's perfect test enviroment. For example: - Phexample and Mocketry, whose matching frameworks break each other - Phexample and BabyMock both require subclassing from their own TestCase subclass, so they can't be used together. I wonder what the solution is? Maybe some registration scheme? It'd be nice to be more coordinated here. As a first step, I manually merged BabyMock and Phexample to produce the following (IMHO) gorgeous tests... testNew self library should receive: #FMOD_System_Create:; with: FMOD_SYSTEM new; does: [ :h | h handle: 20. 0 ]. self library should receive: #FMOD_System_Init:; with: [ :a | a handle = 30 ]; answers: 0. ^ FmodSystem new. testNewSound | soundFile system | system := self given: #testNew. soundFile := FileLocator vmBinary. self library should receive: #FMOD_System_CreateSound:to:with:; with: soundFile fullName and: FMOD_SOUND new and: [ :h | h = system handle ]; answers: 0. ^ system newSoundFromFile: soundFile. testPlaySound | sound | sound := self given: #testNewSound. self library should receive: #FMOD_System:PlaySound:on:; with: sound system handle and: sound handle and: FmodChannel new; answers: 0. ^ sound play. testChannelIsPlaying | channel | channel := self given: #testPlaySound. self library should receive: #FMOD_Channel_IsPlaying:storeIn:; with: channel and: NBExternalAddress new; does: [ :c :isPlaying | isPlaying value: 1 ]. ^ channel isPlaying. The tests... let's call them specifications... clearly state how the object should talk to the FMOD library. The neat part of Phexample is that even though each specification uses the result of the last, it's smart enough not to fail the dependent if the #given: fails. It moves it into "expected failures" this is important because otherwise a failure deep in the system would make it difficult to pinpoint since there could be many failing specifications. n.b. in this case, I'm not sure that mocking is the best strategy and I may end up using a hand-written stub, but I wanted to do a case study. One area where I've really found mocks to shine is internal to one's system. That is, I'm writing an object and discover that it must talk to another as-yet-unwritten object. So I mock it out and in so doing define its API, which I then go implement. Also, the mocks are using a custom extension to BabyMock that allows you to pass the arguments do #does:, so it will not run on vanilla BabyMock ----- Cheers, Sean -- View this message in context: http://forum.world.st/Unifying-Testing-Ideas-tp4726787.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

7 19

Head over to Youtube and Reddit to show Adele Goldberg some love!!
by vfclists . Jan. 4, 2014

Jan. 4, 2014

There is a post on reddit, http://www.reddit.com/r/programming/comments/1udl9x/adele_goldberg_intervie… an interview with Adele Goldberg at http://www.youtube.com/watch?v=IGNiH85PLVg and it isn't seeing much activity. Folks ought to head over and show her some love. She is the First Lady of Smalltalk you know. If it was Alan Kay or Martin Odersky the comments and views would be in 1000s. No wonder Smalltalk appears to be dying. Not enough loyal devotees ready to worship at they feet of their Goddess,:) -- Frank Church ======================= http://devblog.brahmancreations.com

1 0