- Pharo-dev - lists.pharo.org

WhatsUp from: 2014-11-03 until: 2014-11-16
by seaside＠rmod.lille.inria.fr Nov. 4, 2014

Nov. 4, 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-11-16 (*): - $NEXT_STEPS_TOWARDS_WORLD_DOMINATION (*) we'll be expecting results by then ;)

2 1

SmalltalkHub Recent watched events
by Torsten Bergmann Nov. 4, 2014

Nov. 4, 2014

The "Recent watched events" still show no new entries. Only ones from 2004. Anyone know how to fix this? Thanks T.

3 2

Internship position at Thales
by stepharo Nov. 4, 2014

Nov. 4, 2014

Please distribute and contact eric eric.lepors(a)fr.thalesgroup.com Begin forwarded message: From: LE PORS Eric <eric.lepors(a)fr.thalesgroup.com> Subject: Ouverture de sujet de stage Pharo Date: 3 Nov 2014 11:12:18 GMT+1 To: StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> STAGE : Multi-fenÃªtrage sous Pharo Smalltalk (Logiciel) (H/F) - 1413963 Stage - Temps plein Famille professionnelle 06 - R&D : Logiciel Lieu principal FR-Bretagne-Brest Organisation Thales France Dans le cadre de notre dÃ©veloppement, nous recherchons un(e) : STAGE : Multi-fenÃªtrage sous Pharo Smalltalk (Logiciel) â H/F BasÃ©(e) Ã Brest (29) Contexte : Notre entitÃ© dÃ©veloppe rÃ©guliÃ¨rement des maquettes dâinterfaces homme-machine (IHM) innovantes. Lâinnovation se situe autant au niveau de lâergonomie quâau niveau du design graphique visuel ou des Ã©lÃ©ments dâinteraction. Le maquettage est souvent utilisÃ© en sÃ©ance avec les opÃ©rationnels, dâoÃ¹ lâemploi dâun langage dynamique comme Smalltalk qui permet la modification rapide (et en sÃ©ance) du code et des Ã©lÃ©ments dâinteraction. Le maquettage/prototypage des interfaces Homme-Machine est donc actuellement rÃ©alisÃ© sous SMOCK, un framework de maquettage dÃ©veloppÃ© en Smalltalk. Smalltalk Pharo est un excellent candidat pour la plateforme finale d'exÃ©cution du framework de maquettage/prototypage, cependant, certaines limitations de Pharo nous empÃªchent de l'utiliser de maniÃ¨re industrielle. Missions : Nous souhaitons expÃ©rimenter un environnement de maquettage sous Pharo, cependant, cette derniÃ¨re limite lâaffichage des IHM Ã lâintÃ©rieur d'une seule fenÃªtre de l'OS. Nous souhaitons, en relation avec la communautÃ© Pharo, dÃ©velopper le multi-fenÃªtrage. Le stagiaire devra implÃ©menter un mÃ©canisme permettant l'ouverture et gestion de fenÃªtres multiples dans les OS Windows et Linux Ã minima. Une rÃ©utilisation de code existant dans la communautÃ© Pharo et une reversion de code en OpenSource est envisageable. Le candidat sera l'interlocuteur entre Thales et la communautÃ© Pharo. Le candidat Ã©valuera diffÃ©rentes solutions de multi- fenÃªtrage sous diffÃ©rents critÃ¨res (performance, robustesse de la solution, portabilitÃ© de la solution...). La solution devra anticiper le futur et prÃ©voir d'afficher des contenus visuels variÃ©s (vidÃ©o, primitives de dessin 2D, OpenGL...). L'objectif sera de dÃ©velopper un prototype IHM multi-fenÃªtres de dÃ©monstration sur Pharo afin de dÃ©montrer les nouvelles capacitÃ©s et un aperÃ§u des performances. Formation souhaitÃ©e : Master 2 Pro ou 3Ã¨me annÃ©e d'Ecole d'IngÃ©nieur. Connaissances souhaitÃ©es : Le stagiaire devra avoir une connaissance du Smalltalk ou Ãªtre motivÃ© par lâapprentissage de celui-ci. Il devra ensuite Ãªtre motivÃ© par la conception dâinterfaces homme machine de nouvelle gÃ©nÃ©ration. PÃ©riode souhaitÃ©e et durÃ©e : Ã partir de janvier 2015 pour une durÃ©e de 6 mois. Au sein de nos Ã©quipes, nous vous offrons : du challenge, des opportunitÃ©s de carriÃ¨re, et des technologies innovantes pour rendre le monde plus sÃ»r. Le monde mÃ©rite un bel avenir. Vous aussi. Toutes nos offres sur : https://www.thalesgroup.com/fr/homepage/carrieres

2 1

ImageCleaner interaction with Delay
by Ben Coman Nov. 3, 2014

Nov. 3, 2014

ImageCleaner>>cleanUpForRelease calls >>cleanUpMethods which calls Delay class>>startTimerEventLoop. I thought this would have started with a clean/empty suspended delays heap, but it carries forward the old SuspendedDelays. So if there happened to be a suspended delay expiring in a month's time, that would not be affected by ImageCleaner and would end up in the release. I believe the correct behaviour would be for ImageCleaner to produce a clean/empty suspended delays, and so that no waiting processing get stuck, signal any remaining suspended delays when the timer event loop is stopped by Delay class>>stopTimerEventLoop. Any objections? cheers -ben

2 2

[pharo-project/pharo-core]
by GitHub Nov. 3, 2014

Nov. 3, 2014

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

1 0

[pharo-project/pharo-core] 27bfd3: 40351
by GitHub Nov. 3, 2014

Nov. 3, 2014

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: 27bfd36879b17e6012f9eeffd702073842607d7b https://github.com/pharo-project/pharo-core/commit/27bfd36879b17e6012f9eeff… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-11-03 (Mon, 03 Nov 2014) Changed paths: M Kernel.package/CompiledMethod.class/instance/comparing/sameLiteralsAs_.st M Manifest-Tests.package/SmalllintManifestCheckerTest.class/instance/running/tearDown.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script351.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40351.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Spec-Tools.package/AbstractApiSetter.class/instance/initialize/setValueTo_.st M Spec-Tools.package/AbstractApiSetter.class/instance/protocol/updateWith_.st M Spec-Tools.package/ChangeSorterApplication.class/instance/menu/changeSetMenu_shifted_.st M Spec-Tools.package/ChangeSorterApplication.class/instance/menu/classMenu_shifted_.st M Spec-Tools.package/ChangeSorterApplication.class/instance/menu/messageMenu_shifted_.st M Spec-Tools.package/ConfigurationGenerator.class/instance/metacello/addMetacelloBaseline.st M Spec-Tools.package/ConfigurationGenerator.class/instance/metacello/createVersionForBlessing_.st M Spec-Tools.package/ConfigurationGenerator.class/instance/metacello/dependentPackages.st M Spec-Tools.package/DiffChangeRecordConverter.class/definition.st M Spec-Tools.package/DiffChangeRecordConverter.class/instance/private/priorVersionOfAMethod_.st M Spec-Tools.package/DiffMorphChangeRecordConverter.class/definition.st M Spec-Tools.package/DualChangeSorterApplication.class/instance/event/refeshedChangeSet_.st M Spec-Tools.package/DualChangeSorterApplication.class/instance/menu - change set/checkThatSidesDiffer_.st M Spec-Tools.package/DualChangeSorterApplication.class/instance/menu - class/moveClassFrom_to_.st M Spec-Tools.package/DualChangeSorterApplication.class/instance/menu/changesMenu_shifted_from_to_.st M Spec-Tools.package/MessageBrowser.class/definition.st M Spec-Tools.package/MessageBrowser.class/instance/initialization/initialize.st R Spec-Tools.package/MessageBrowser.class/instance/protocol/title_.st M Spec-Tools.package/MessageBrowser.class/instance/testing/sortClassesInCachedHierarchy_b_.st M Spec-Tools.package/MessageBrowser.class/instance/text selection/searchedString_in_.st M Spec-Tools.package/NewVersionBrowser.class/definition.st M Spec-Tools.package/NewVersionBrowser.class/instance/menu/compareToOtherVersion.st M Spec-Tools.package/WorkingCopyToolBar.class/definition.st R Spec-Tools.package/WorkingCopyToolBar.class/instance/initialization/initialize.st M Spec-Tools.package/WorkingCopyToolBar.class/instance/initialize/createPackage.st M Versionner-Tests-Core-Commands.package/VSReleaseDevelopmentVersionCommandTest.class/instance/running/tearDown.st Log Message: ----------- 40351 14246 CompiledMethod>>hash can produce clashes https://pharo.fogbugz.com/f/cases/14246 14379 Code critique pass Spec-Tools https://pharo.fogbugz.com/f/cases/14379 14375 Random #obsoleteClasses test failures https://pharo.fogbugz.com/f/cases/14375 http://files.pharo.org/image/40/40351.zip

1 0

Failing #obsoleteClasses test
by Max Leske Nov. 3, 2014

Nov. 3, 2014

I spent a couple of hours trying to find out why the #obsoleteClasses test sporadically fails. Iâve found one candidate that fixes all the failures that I could produces. Simply put, any test that does something AST related (e.g. runs critics) *has to* reset the ASTCache during #tearDown: ASTCache reset. Iâve found two test classes that needed to be adapted: SmalllintManifestCheckerTest and VSReleaseDevelopmentVersionCommandTest. Issue with slice: https://pharo.fogbugz.com/f/cases/14375/Random-obsoleteClasses-test-failures <https://pharo.fogbugz.com/f/cases/14375/Random-obsoleteClasses-test-failures> Cheers, Max

4 4

VersionnerRepositoriesManager - Why clear okAction?
by Sean P. DeNigris Nov. 3, 2014

Nov. 3, 2014

No class is safe from my wrath he he... VersionnerRepositoriesManager class>>#open | dialog | dialog := remotesUI openDialogWithSpec. dialog okAction: [ ] - why were we wiping the okAction? "dialog okAction: [ ]" does not reveal any intention. At minimum, a comment would be good - it would be good to return something here so users can customize more easily. Even though this is tightly integrated with Versionner, a tiny bit of care makes the system more easily extensible. We should record some patterns here... ----- Cheers, Sean -- View this message in context: http://forum.world.st/VersionnerRepositoriesManager-Why-clear-okAction-tp47… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

2 2

[pharo-project/pharo-core] c5ed9d: 40350
by GitHub Nov. 3, 2014

Nov. 3, 2014

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: c5ed9d14cec80d2fc6531709abdcd7ec442b887f https://github.com/pharo-project/pharo-core/commit/c5ed9d14cec80d2fc6531709… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-11-03 (Mon, 03 Nov 2014) Changed paths: M Kernel.package/ClassOrganization.class/instance/backward compatibility - file in%2Fout/putCommentOnFile_numbered_moveSource_forClass_.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script350.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40350.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M System-Changes.package/ChangeSet.class/class/current changeset/newChanges_withOld_.st M System-Support.package/ChangesLog.class/instance/event-listening/registerToAnnouncements.st Log Message: ----------- 40350 14373 Replace Announcer>>#on:send:to:s senders in System-Support https://pharo.fogbugz.com/f/cases/14373 14372 Replace Announcer>>#on:send:to:s senders in System-Changes https://pharo.fogbugz.com/f/cases/14372 14377 FileOut creates invalid comment entries for classes with class side methods https://pharo.fogbugz.com/f/cases/14377 http://files.pharo.org/image/40/40350.zip

1 0

[pharo-project/pharo-core]
by GitHub Nov. 3, 2014

Nov. 3, 2014

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

1 0