- Pharo-dev - lists.pharo.org

more robust tests
by stepharo July 18, 2016

July 18, 2016

Hi While integrating some changes in P6.0 I got such tests failing. Only failing on mac. Could you check? Stef Regression GT.EventRecorder.Tests.Core.GTEventRecorderTest.testAddCollector3 (from GT-EventRecorder-Tests) Failing for the past 1 build (Since Unstable#7 ) Took 0.96 sec. add description Error Message Assertion failed Stacktrace GTEventRecorderTest(TestAsserter)>>assert: GTEventRecorderTest(TestAsserter)>>deny: GTEventRecorderTest>>assertReceiverSemaphore GTEventRecorderTest>>waitForDelivery GTEventRecorderTest>>testAddCollector3 GTEventRecorderTest(TestCase)>>performTest Stef

6 9

[ANN] file dialog replacement experiment
by Peter UhnÃ¡k July 17, 2016

July 17, 2016

Hi, last week I stitched together a simple file dialog replacement and today I managed to somewhat finish it. There is still a lot to be desired, but right now it supports things that were the most pain for me: * list of most common places (home, root, image directory, temp) * custom bookmarks by dragging folders from file-pane to bookmark-pane * toggle hidden files (right-click on file listing) * preset file name * filtering files by extensions or patterns and toggling between filters * synchronous and asynchronous mode â You can use it independently of Pharo's native dialogs FDOpenFileDialog new extensionFilters: {'STON files' -> #(ston). 'All files' -> #()}; defaultFolder: FileLocator imageDirectory asFileReference; openModal Or if you feel brave, I have an extended UIManager that will use thisâ¦, and then you can use regular manager commands UIManager default chooseFileMatching: #('*.ston') but you can always go back FDMorphicUIManager new beDefault. "use new dialogs" MorphicUIManager new beDefault. "use old dialogs" and of course the installation itself (I'll add it to catalog soon after I find a way to autogenerate configurations from git tags) Metacello new baseline: 'FileDialog'; repository: 'github://peteruhnak/file-dialog/repository'; load. More info and docs on GitHub https://github.com/peteruhnak/file-dialog Any comments/feedback/bug reports is appreciated. Peter

5 10

100 factorial asMethodConst
by Denis Kudriashov July 17, 2016

July 17, 2016

Hi. As continue to Marcus cool features around haltOnce I implement analogue of Dolphin ##() syntax. Slice is inbox (18768 <https://pharo.fogbugz.com/f/cases/18768/Inlined-method-const-could-be-imple…>). So it will be available soon. Idea is to send message #asMethodConst to result of expression which you want to cache. At first call it will replace full message send node with result as literal. And following method call will use this precomputed value. You can read details in my blog http://dionisiydk.blogspot.fr/2016/07/magic-with-pharo-reflectivity.html. Best regards, Denis

1 0

Pharo minimal & bootstrapping - Time & DelayScheduler
by Ben Coman July 17, 2016

July 17, 2016

A question on the minimization of the Pharo image and bootstrapping... Is there a desire to ultimately get down to the point of starting without the Time class and/or without the DelayScheduler class? DelayScheduler currently depends on Time, only due to calling "Time microsecondClockValue' which is <primitive: 240> so this dependency could be removed by copying #microsecondClockValue to DelayScheduler. How a bad is it to have one primitive invoked from two different methods? cheers -ben

2 1

Epicea?
by Alexandre Bergel July 16, 2016

July 16, 2016

Hi! When I close and open an image, there is an Epicea window, with apparently some of my previous change. I am not sure what to do with it beside closing it. What is it supposed to show me? A small help would great. Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

4 4

CFP: 1st Workshop on Meta-Programming Techniques and Reflection (META) with SPLASH 2016
by Stefan Marr July 15, 2016

July 15, 2016

**Call for Papers** ======================================================================== 1st Workshop on Meta-Programming Techniques and Reflection (METAâ16) Co-located with SPLASH 2016 October 30, 2016, Amsterdam, Netherlands http://2016.splashcon.org/track/meta2016 Follow us on twitter @MetaAtSPLASH ======================================================================== The Metaâ16 workshop aims to bring together researchers working on metaprogramming and reflection, as well as users building applications, language extensions such as contracts, or software tools. With the changing hardware and software landscape, and increased heterogeneity of systems, metaprogramming becomes an important research topic to handle the associate complexity once more. Contributions to the workshop are welcome on a wide range of topics related to design, implementation, and application of metaprogramming techniques, as well as empirical studies on and typing for such systems and languages. ### Important Dates 08 Aug 2016 - Abstract Submission 15 Aug 2016 - Paper Submission 05 Sep 2016 - Notification 09 Sep 2016 - Demo, position or work-in-progress paper submission 23 Sep 2016 - Demo, position or work-in-progress paper notification 30 Oct 2016 Workshop ### Topics of Interest The workshop is a venue for all approaches that embrace metaprogramming: - from static to dynamic techniques - reflection, meta-level architectures, staging, open language runtimes applications to middleware, frameworks, and DSLs - optimization techniques to minimize runtime overhead - contract systems, or typing of reflective programs reflection and metaobject protocols to enable tooling - case studies and evaluation of such techniques, e.g., to build applications, language extensions, or tools - empirical evaluation of metaprogramming solutions - security in reflective systems and capability-based designs - meta-level architectures and reflective middleware for modern runtime platforms (e.g. IoT, cyber-physical systems, mobile/cloud/grid computing, etc) - surveys, conceptualization, and taxonomization of existing approaches ### Types of Submissions and Workshop format We welcome both technical papers and work-in-progress and position papers from the academic as well as industrial perspective. Position paper should present new ideas and emerging problems and take a perhaps controversial stance on a specific topic and argue the position well. Furthermore, we plan interactive brainstorming and demonstration sessions between the formal presentations to enable an active exchange of ideas. The workshop papers will be put on the workshop website, if not requested otherwise by the authors, but they are not part of formal proceedings. Papers are to be submitted using the ACM sigplanconf style at 10pt font size. See http://www.sigplan.org/Resources/Author/. - demos and posters: 1-page abstract - position and work-in-progress paper: 1-4 pages - technical paper: up to 8 pages Demos, posters, position and work-in-progress papers can be submitted on a second, later deadline to discuss the latest results and current work. For the submission, please use the submission system at: https://meta16.hotcrp.com/ ### Organizing Committee Shigeru Chiba, University of Tokyo Elisa Gonzalez Boix, Vrije Universiteit Brussel Stefan Marr, Johannes Kepler University Linz ### Program Committee Marcus Denker, INRIA, France Robert Hirschfeld, HPI, Germany Hridesh Rajan, Iowa State University, USA Romain Rouvoy, University Lille 1 and INRIA, France Eric Tanter, University of Chile, Chile Tom Van Cutsem, Bell Labs, Belgium Tijs van der Storm, CWI, Netherlands Takuo Watanabe, Tokyo Institute of Technology, Japan

1 0

What is the correct way to create new integration configuration?
by Juraj Kubelka July 14, 2016

July 14, 2016

Hi, I am working on a new configuration for GTools. What is the correct way to integrate cases with a slice? For example this one: https://pharo.fogbugz.com/f/cases/18471/GTTools-relies-on-hasSpecialSelecto… <https://pharo.fogbugz.com/f/cases/18471/GTTools-relies-on-hasSpecialSelecto…> It has slice in Pharo60Inbox. Should I copy commits to GToolkit repository? And how it happens that GToolkit repository has commits done by TheIntegrator? Thanks, Juraj

3 6

Download link for latest Pharo6 image on download page
by Marcus Denker July 14, 2016

July 14, 2016

Hi, I have added a link to the download page for Pharo6: http://pharo.org/download This way it is easier to findâ¦ it is of course in active development, but quite usable most of the time. Marcus

3 3

tricks for XML parsing.
by stepharo July 14, 2016

July 14, 2016

Hi guys these free books may be interesting for you http://aosabook.org/ http://aosabook.org/en/posa/parsing-xml-at-the-speed-of-light.html stef

4 6

[pharo-project/pharo-core] ac9f62: 60149
by GitHub July 13, 2016

July 13, 2016

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: ac9f62ce8dea687da1b6f7675d47f43bee08dc65 https://github.com/pharo-project/pharo-core/commit/ac9f62ce8dea687da1b6f767… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-07-13 (Wed, 13 Jul 2016) Changed paths: A OpalCompiler-Core.package/AbstractCompiler.class/instance/accessing/encoderClass_.st M OpalCompiler-Tests.package/OCNewCompilerWithChangesFunctionalTests.class/instance/other-tests/testDifferentBlocksWithSameArgumentName.st M OpalCompiler-Tests.package/OCNewCompilerWithChangesFunctionalTests.class/instance/other-tests/testModulePrimitive.st M OpalCompiler-Tests.package/OCNewCompilerWithChangesFunctionalTests.class/instance/test - array compilation/testMultiElementArray.st M OpalCompiler-Tests.package/OCNewCompilerWithChangesFunctionalTests.class/instance/test - array compilation/testSimpleArray.st M OpalCompiler-Tests.package/OCNewCompilerWithChangesFunctionalTests.class/instance/test - block returning/testBlockReturning.st M OpalCompiler-Tests.package/OCNewCompilerWithChangesFunctionalTests.class/instance/tests/testBlockTemp.st M OpalCompiler-Tests.package/OCNewCompilerWithChangesFunctionalTests.class/instance/tests/testMethodArgument.st M OpalCompiler-Tests.package/OCNewCompilerWithChangesFunctionalTests.class/instance/tests/testMethodTemp.st M OpalCompiler-Tests.package/OCNewCompilerWithChangesFunctionalTests.class/instance/tests/testOneFloat.st M OpalCompiler-Tests.package/OCNewCompilerWithChangesFunctionalTests.class/instance/tests/testReturnBlockInMethod.st M OpalCompiler-Tests.package/OCNewCompilerWithChangesFunctionalTests.class/instance/tests/testSetUp.st M OpalCompiler-Tests.package/OCNewCompilerWithChangesFunctionalTests.class/instance/tests/testSteamContentsLimitedToSequenceableCollectionClass.st M OpalCompiler-Tests.package/OCNewCompilerWithChangesFunctionalTests.class/instance/tests/testToDoArgumentNotInlined.st M OpalCompiler-Tests.package/OCNewCompilerWithChangesFunctionalTests.class/instance/tests/testToDoInsideTempNotInlined.st M OpalCompiler-Tests.package/OCNewCompilerWithChangesFunctionalTests.class/instance/tests/testToDoOutsideTempNotInlined.st M OpalCompiler-Tests.package/OCNewCompilerWithChangesFunctionalTests.class/instance/tests/testWhileModificationAfterNotInlined.st M OpalCompiler-Tests.package/OCNewCompilerWithChangesFunctionalTests.class/instance/tests/testWhileModificationBeforeNotInlined.st M OpalCompiler-Tests.package/OCNewCompilerWithChangesFunctionalTests.class/instance/tests/testWhileWithTempNotInlined.st M Pharo-Help.package/PharoWelcomePage.class/class/accessing/title.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60148.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60149.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60148.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60149.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Spec-Examples.package/DynamicWidgetChange.class/instance/private/changeToButton.st M Spec-Examples.package/DynamicWidgetChange.class/instance/private/changeToList.st M System-Support.package/SystemVersion.class/instance/printing/shortVersionString.st Log Message: ----------- 60149 18390 System version should be "Pharo 6.0" instead of "Pharo6.0" and PharoWelcomePage should not hard code version https://pharo.fogbugz.com/f/cases/18390 18748 OpalCompiler Tests: OCNewCompilerWithChangesFunctionalTests should set encoder to OpalEncoderForV3PlusClosures https://pharo.fogbugz.com/f/cases/18748 15688 Remove ComposableModel>>#instantiateModels:s senders in Spec-Examples https://pharo.fogbugz.com/f/cases/15688 http://files.pharo.org/image/60/60149.zip

2 2