October 2014 - Pharo-dev - lists.pharo.org

WhatsUp from: 2014-10-20 until: 2014-10-31
by seaside＠rmod.lille.inria.fr Oct. 20, 2014

Oct. 20, 2014

Hi! We're sending this automatic email twice a month, to give the community an opportunity to easily know what's happening and to coordinate efforts. Just answer informally, and feel free to spawn discussions thereafter! ### Here's what I've been up to since the last WhatsUp: - $HEROIC_ACHIEVEMENTS_OR_DISMAL_FAILURES_OR_SIMPLE_BORING_NECESSARY_TASKS ### What's next, until 2014-10-31 (*): - $NEXT_STEPS_TOWARDS_WORLD_DOMINATION (*) we'll be expecting results by then ;)

1 0

Issue 14269 Komitter: Improve layout for long repo names
by Sean P. DeNigris Oct. 19, 2014

Oct. 19, 2014

https://pharo.fogbugz.com/default.asp?14269 Right now, no matter how wide the Komitter window is, the repo drop down often too narrow to see the repo names: <http://forum.world.st/file/n4785409/Screenshot_2014-10-19_16.png> Fix in inbox: SLICE-Issue-14269-Komitter-Improve-layout-for-long-repo-names-SeanDeNigris.1 - Add vertical splitter and intially equal columns between commit message widget and author/repo widgets Ready for review. ----- Cheers, Sean -- View this message in context: http://forum.world.st/Issue-14269-Komitter-Improve-layout-for-long-repo-nam… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

1 0

Spec Understandability
by Sean P. DeNigris Oct. 19, 2014

Oct. 19, 2014

What is one supposed to do with an error like this? It's about as readable as a C++ template error ;) PanelMorph(Object)>>doesNotUnderstand: #layout: SpecInterpreter>>actionToPerformWithSelector:arguments: SpecInterpreter>>performNextSelectorAndIncrementIndex SpecInterpreter>>interpretASpec:selector: SpecInterpreter>>interpretASpec:model:selector: SpecInterpreter class>>private_interpretASpec:model:selector: SpecInterpreter>>performNextSelectorAndIncrementIndex in Block: [ :each | self class private_interpretASpec: each ...etc... Array(SequenceableCollection)>>collect: SpecInterpreter>>performNextSelectorAndIncrementIndex SpecInterpreter>>interpretASpec:selector: SpecInterpreter>>interpretASpec:model:selector: SpecInterpreter class>>private_interpretASpec:model:selector: SpecInterpreter>>computeSpecFrom:selector: SpecInterpreter>>retrieveSpecFrom:selector: SpecInterpreter>>interpretASpec:selector: SpecInterpreter>>interpretASpec:model:selector: SpecInterpreter class>>private_interpretASpec:model:selector: SpecInterpreter>>performNextSelectorAndIncrementIndex in Block: [ :each | self class private_interpretASpec: each ...etc... Array(SequenceableCollection)>>collect: SpecInterpreter>>performNextSelectorAndIncrementIndex SpecInterpreter>>interpretASpec:selector: SpecInterpreter>>interpretASpec:model:selector: SpecInterpreter class>>private_interpretASpec:model:selector: SpecInterpreter class>>private_buildWidgetFor:withSpec: (ComposableModel)>>private_buildWithSpec: (ComposableModel)>>private_buildWithSpec SpecInterpreter>>returnInterpretationOf: SpecInterpreter>>interpretASpec:selector: SpecInterpreter>>interpretASpec:model:selector: SpecInterpreter class>>private_interpretASpec:model:selector: ----- Cheers, Sean -- View this message in context: http://forum.world.st/Spec-Understandability-tp4778370.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

1 3

[pharo-project/pharo-core]
by GitHub Oct. 19, 2014

Oct. 19, 2014

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

1 0

[pharo-project/pharo-core] 7e3d20: 40311
by GitHub Oct. 19, 2014

Oct. 19, 2014

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: 7e3d202a32741fac22952cdc42205959083c0656 https://github.com/pharo-project/pharo-core/commit/7e3d202a32741fac22952cdc… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-10-19 (Sun, 19 Oct 2014) Changed paths: M Refactoring-Critics.package/RBSmalllintChecker.class/instance/private/checkMethodsForClass_.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script311.st M ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40310.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40311.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 40311 14228 critic rules running on all methods of a class extended by a package https://pharo.fogbugz.com/f/cases/14228 http://files.pharo.org/image/40/40311.zip

1 0

Announcement Handlers Fail Silently?
by Sean P. DeNigris Oct. 18, 2014

Oct. 18, 2014

It seems that exceptions get swallowed by the system in #30858. Is that intended/still the case in 4.0? It makes it confusing to debug and develop via the debugger... e.g.: anAnnouncer when: ItemAdded do: [ :it | nil nonExistantMethod ]. fails silently, and the exception is not propagated to the UI i.e. no debugger appears ----- Cheers, Sean -- View this message in context: http://forum.world.st/Announcement-Handlers-Fail-Silently-tp4785326.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

2 1

#openPharoZenWorkspace broken
by Sven Van Caekenberghe Oct. 18, 2014

Oct. 18, 2014

So I noticed that #openPharoZenWorkspace is broken, because that code makes assumptions that GT-Playground does not offer. I know this has been discussed before, what is the strategy going forward ? Sven

2 3

New Spur trunk image available
by Eliot Miranda Oct. 18, 2014

Oct. 18, 2014

Hi All, finally the Spur Squeak trunk image is updateable. The image in http://www.mirandabanda.org/files/Cog/SpurImages/2014-10-16/ was created today and thanks to Bert Freudenberg's latest Monticello work can be updated independently of the non-Spur trunk. Spur VMs are available in http://www.mirandabanda.org/files/Cog/VM/VM.r3105/ (and later as they appear). Without wanting to appear too overconfident the Spur system looks to be ready for use apart from image segments (which I hope to have working some time next month). I'm really interested in having this stress tested by as many people as possible. Spur really does offer a significant performance and functionality improvement over the current system, but it needs testing to ensure its reliability. Esteban Lorenzano is hard at work on the Pharo bootstrap for Spur so I hope Pharo 4 Spur will be available soon. As far as trunk goes, using Spur alongside non-Spur trunk is going to be difficult to manage for the near future. Right now, Spur modifies the Collections, Compiler, Kernel and System packages, and this is done by auto-editing the non-Spur versions of those packages, something I do periodically as new versions arrive. I also auto-edit trunk configurations (the part of the image update scheme that ensures packages are loaded in the right order when there are dependencies between packages) from non-Spur "update" to Spur "update.spur" forms. This at east means that Spur can keep up with trunk. But it does /not/ provide a way of committing to Collections.spur, Compiler.spur, Kernel.spur or System.spur without getting out of sync with non-Spur trunk. Note that apart from these packages, one /can/ safely commit any other package from a Spur image to trunk. Right now the plan is to release both V3 (the pre-Spur format) and Spur versions of Squeak 4.6 (I hope it'll be called Squeak 5.0). This isn't my preference. I'd like to see just Spur released, once reliability is verified. But I understand the safety and backward-compatibility concerns (Spur won't be able to load V3 image segments, and vice verse). The issue is of course that we have this tricky package situation to manage where, to keep the two systems in sync, modifications to Collections, Compiler, Kernel and System need to be committed from V3 and auto-edited to Spur. I think that's too clumsy to be practicable. Perhaps allowing the two systems to fork and doing a manual merge will be acceptable, but it'll be work to keep them in sync. -- best, Eliot

4 4

CompiledMethod>>hash can produce clashes
by Max Leske Oct. 17, 2014

Oct. 17, 2014

We found an issue where CompiledMethods can produce the same hash event within the same MethodDictionary. Reported here: https://pharo.fogbugz.com/f/cases/14246/CompiledMethod-hash-can-produce-cla… <https://pharo.fogbugz.com/f/cases/14246/CompiledMethod-hash-can-produce-cla…> Cheers, Max

8 22

TLS SNI[1] for SqueakSSL on unix
by stepharo Oct. 17, 2014

Oct. 17, 2014

Might be interesting for some of you. Hi, I've implemented support for TLS SNI[1] for SqueakSSL on unix. I've uploaded the modified source files[2][3], a diff[4], and a prebuilt module[5] (built on Ubuntu 14.04 from the Cog branch). The image side code is also available[6], along with an updated version of the WebClient[7] package, and intermediate packages with various improvements[8]. The image side code works even if the plugin doesn't support TLS SNI, but this version of WebClient won't work with older versions of the SqueakSSL-Core package. Please review the changes, and consider adding them to the corresponding repositories! Levente [1] https://en.wikipedia.org/wiki/Server_Name_Indication [2] http://leves.web.elte.hu/squeak/SqueakSSL/SqueakSSL.h [3] http://leves.web.elte.hu/squeak/SqueakSSL/sqUnixOpenSSL.c [4] http://leves.web.elte.hu/squeak/SqueakSSL/diff.txt [5] http://leves.web.elte.hu/squeak/SqueakSSL/SqueakSSL [6] http://leves.web.elte.hu/squeak/SqueakSSL/SqueakSSL-Core-ul.29.mcz [7] http://leves.web.elte.hu/squeak/SqueakSSL/WebClient-Core-ul.98.mcz [8] http://leves.web.elte.hu/squeak/SqueakSSL/

1 0