February 2018 - Pharo-dev - lists.pharo.org

[CfP] ICOOOLPS 2018
by Tim Felgentreff Feb. 5, 2018

Feb. 5, 2018

Call for Papers: ICOOOLPS'18 ============================ 13th Workshop on Implementation, Compilation, Optimization of Object- Oriented Languages, Programs and Systems Co-located with ECOOP 2018 held Mon 16 - Sun 22 July in Amsterdam, Netherlands Twitter: @ICOOOLPS URL: https://conf.researchr.org/track/ecoop-issta-2018/ICOOOLPS-2018-papers The ICOOOLPS workshop series brings together researchers and practitioners working in the field of language implementation and optimization. The goal of the workshop is to discuss emerging problems and research directions as well as new solutions to classic performance challenges. The topics of interest for the workshop include techniques for the implementation and optimization of a wide range of languages including but not limited to object-oriented ones. Furthermore, meta-compilation techniques or language-agnostic approaches are welcome, too. ### Topics of Interest A non-exclusive list of topics of interest for this workshop is: - Implementation and optimization of fundamental languages features (from automatic memory management to zero-overhead metaprogramming) - Runtime systems technology (libraries, virtual machines) - Static, adaptive, and speculative optimizations and compiler techniques - Meta-compilation techniques and language-agnostic approaches for the efficient implementation of languages - Compilers (intermediate representations, offline and online optimizations,â¦) - Empirical studies on language usage, benchmark design, and benchmarking methodology - Resource-sensitive systems (real-time, low power, mobile, cloud) - Studies on design choices and tradeoffs (dynamic vs. static compilation, heuristics vs. programmer input,â¦) - Tooling support, debuggability and observability of languages as well as their implementations ### Workshop Format and Submissions This workshop welcomes the presentation and discussion of new ideas and emerging problems that give a chance for interaction and exchange. More mature work is welcome as part of a mini-conference format, too. We aim to interleave interactive brainstorming and demonstration sessions between the formal presentations to foster an active exchange of ideas. The workshop papers will be published in ACM DL or an open archive (to be confirmed). Papers are to be submitted using the sigplanconf LaTeX template (http://www.sigplan.org/Resources/LaTeXClassFile/) Please submit contributions via EasyChair: https://easychair.org/conferences/submission_show_all.cgi?a=17114062 ### Important Dates Submissions: 18 May 2018 Author Notification: 8 June 2018 ### Program Committee The program committee consists of the organizers and the following reviewers: Nada Amin, University of Cambridge ClÃ©ment BÃ©ra, RMOD - INRIA Lille Nord Europe Shigeru Chiba, University of Tokyo Benoit Daloze, JKU Linz GÃ¶rel Hedin, Lund University Eric Jul, University of Oslo Stefan Marr, University of Kent Eliot Miranda, Cadence Design Systems Sarah Mount, King's College London Tobias Pape, Hasso Plattner Institute Jennifer Sartor, Vrije Universiteit Brussel + University Ghent ### Workshop Organizers Tim Felgentreff, Oracle Labs Potsdam Olivier Zendra, INRIA / LORIA

1 0

Pavel's ChangeLog week of 2018-01-29
by Pavel Krivanek Feb. 5, 2018

Feb. 5, 2018

Hi, on my laptop, I have a 13.3" display with resolution 3200x1800. The value of PPI of this display is 276 and because I'm using Linux that does not provide a simple way how to scale the resolution of a window that does not provide high PPI out of the box, it makes Pharo with the default settings usable on that machine only with a magnifier. I need to say that Pharo is not alone, a huge amount of application has real troubles with high values of PPI on Linux. Pharo provides a possibility to increase the size of the fonts which makes system more usable but it has a lot of issues. The icons, scrollbars and other elements keep the original size so they are really tiny. The grips for windows resizing too which makes them hard to catch. The default size of the windows is not changed as well so you need to resize literally every window by hand. This is not only an issue of high PPI displays. When you do a presentation on projectors, in most cases you need to make text bigger. Unfortunately, in current Morphic it is not imaginable that we will solve this issue properly on the level of canvases. The rendering of the Morphic with Athens is a better way but nor ready and no-one will spend energy on it with the planned switch to Bloc that will finally solve this issue properly. But because I needed some solution, I decided to introduce a worldScaleFactor that provides a simple constant that that will scale the UI elements and then started to use it in all places where it is needed. It is a dirty solution but starts to work quite well. You can scale the UI down too. From the screenshot, you can see that some places still need to be improved. The next issue whit high PPI on Linux VM is with the cursor's size. It cannot be replaced by bigger ones that the package VistaCursors provides because the primitive for the cursor replacing fails. But fortunately it has a simple solution, the VM needs to be linked with Xrender library, see https://pharo.fogbugz.com/f/cases/12960/Primitive-101-Cursor-beCursor-fails… Cheers, -- Pavel

1 1

git workflow (iceberg) and monticello packages
by Nicolai Hess Feb. 5, 2018

Feb. 5, 2018

Hi , I am still not sure I understand the git based development workflow. I set up my image and repository as described by the guide. now, if new commits are in the pharo-project, iceberg shows the list of incoming changes (commits). Ok, but: If I modify code in my image (for example, change a method in class Morph), the morphic-core package is marked as dirty in monticello and my pharo repository in iceberg is marked with an asterisk. If I choose "synchronize repository ..." I would expect my change to be an uncommited change, but instead, it isn't shown and the Morphic-core package isn't dirty anymore. Is it because I need to create a branch first ? But why is the Morphic-core package not dirty anymore, the change is not commited or published, how do I know where are my changes ? nicolai

2 1

[Pharo 7.0-dev] Build #498: 20937-Add-horizontal-scrollbar-to-FastTable
by ci-pharo-ci-jenkins2＠inria.fr Feb. 4, 2018

Feb. 4, 2018

There is a new Pharo build available! The status of the build #498 was: SUCCESS. The Pull Request #657 was integrated: "20937-Add-horizontal-scrollbar-to-FastTable" Pull request url: https://github.com/pharo-project/pharo/pull/657 Issue Url: https://pharo.fogbugz.com/f/cases/20937 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #497: 20124-FTTreeFunctionStrategy-call-deprecated-method
by ci-pharo-ci-jenkins2＠inria.fr Feb. 4, 2018

Feb. 4, 2018

There is a new Pharo build available! The status of the build #497 was: FAILURE. The Pull Request #796 was integrated: "20124-FTTreeFunctionStrategy-call-deprecated-method" Pull request url: https://github.com/pharo-project/pharo/pull/796 Issue Url: https://pharo.fogbugz.com/f/cases/20124 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #496: 21227-MBCommandrepositoryOfPackageNamed-sends-MCCacheRepository-default
by ci-pharo-ci-jenkins2＠inria.fr Feb. 4, 2018

Feb. 4, 2018

There is a new Pharo build available! The status of the build #496 was: FAILURE. The Pull Request #795 was integrated: "21227-MBCommandrepositoryOfPackageNamed-sends-MCCacheRepository-default" Pull request url: https://github.com/pharo-project/pharo/pull/795 Issue Url: https://pharo.fogbugz.com/f/cases/21227 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #495: 21231-tabmorph-close-icon-is-not-well-aligned
by ci-pharo-ci-jenkins2＠inria.fr Feb. 3, 2018

Feb. 3, 2018

There is a new Pharo build available! The status of the build #495 was: SUCCESS. The Pull Request #793 was integrated: "21231-tabmorph-close-icon-is-not-well-aligned" Pull request url: https://github.com/pharo-project/pharo/pull/793 Issue Url: https://pharo.fogbugz.com/f/cases/21231 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #494: 21232-BenchmarkResultprintFrequencyOn-can-be-confusing
by ci-pharo-ci-jenkins2＠inria.fr Feb. 3, 2018

Feb. 3, 2018

There is a new Pharo build available! The status of the build #494 was: SUCCESS. The Pull Request #794 was integrated: "21232-BenchmarkResultprintFrequencyOn-can-be-confusing" Pull request url: https://github.com/pharo-project/pharo/pull/794 Issue Url: https://pharo.fogbugz.com/f/cases/21232 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Disabling a MenuGroupModel
by HernÃ¡n Morales Durand Feb. 3, 2018

Feb. 3, 2018

Hi guys, If you develop an application window with multiple grouped menu items, you will certainly be able to enable/disable menu groups at once. Currently it is not possible with MenuGroupModel (Morphic). - A menu (item or group) model manages its state using enabledHolder instance variable (the enabledHolder is configured in its superclass' initialize) -- Being a value holder, one might think there is a propagation of state (enabled/disabled) changes to subwidgets, but it does not happen currently. --- Longer explanation: On static menu building, MenuGroupModel does not propagate #enable: state changes to its widget because "widget" i.v. is nil. The reason is a MenuGroupModel #enabled: is evaluated BEFORE its widget is built. How to reproduce: | mm | mm := MenuModel new addGroup: [ :group | group addItem: [ :item | item name: 'File'; icon: #openIcon asIcon; subMenu: (MenuModel new addGroup: [ : gp | gp disable; " <------ HERE we disable the group " addItem: [ : it | it name: 'Open'; icon: #openIcon asIcon; shortcut: $o meta; action: [ self inform: 'Open' ] ]; addItem: [ : it | it name: 'Save'; icon: #smallSaveIcon asIcon; shortcut: $s meta; action: [ self inform: 'Save' ] ] ]) ] ]; yourself. mm extent: 200 @ 100. mm openWithSpec. mm inspect. (it doesn't matter if #disable is sent after the #addItem: block evaluation) - Even after all MenuGroupModel widgets were built, if you try to disable a menu group dinamically: mm menuGroups anyOne menuItems anyOne subMenu menuGroups anyOne disable. you would get "Instance of OrderedCollection did not understand #enabled:" (the widget of a MenuGroupModel is an OrderedCollection!!). - However disabling/enabling MenuItemModel works: mm menuGroups anyOne menuItems anyOne subMenu menuGroups anyOne menuItems first disable. - MenuItemModel gets actually disabled in the ToggleMenuItemMorph/UpdatingMenuMorph (#isEnabled:) when the Canvas draws it. - Incredibly, all disabled groups are re-enabled from several places in the image. -- When the menu is clicked, a ToolDockingBarMorph triggers re-enablement of the MenuMorph in #removeMatchString/#displayFiltered:. This is presumably the code triggered when a menu is displayed and you type to filter the menu items. Something like this: "As initially there is no matchString in the activeSubMenu, then enable all menu items". Obviously it cleans disabled items. The message flow is: DockingBarMorph>>activeSubmenu: -> MenuMorph>>removeMatchString -> MenuMorph>>displayFiltered: --> m isEnabled: isMatch - Another place where menu items are automatically disabled is this flow: FormCanvas>>draw: -> ToggleMenuItemMorph>>drawOn: --> ToggleMenuItemMorph>>isEnabled --> ToggleMenuItemMorph>>isEnabled: !!! --> MorphicMenuItemAdapter>>enabled (This actually CHANGES the enabled state on the Model, disconnecting enabled state between the morph and the model adapter) This seem to have multiple paths of resolution. I'm going to propose a fix that I tested in Pharo 6.1 and Pharo 7. I don't know yet how to fix the menu search auto-enable on key-press but would be glad to read a solution to distinguish between both uses. My idea for now is to have a Morphic property which sets #doNotAutoReEnableItems. However I will open an issue and let people check. You can test it with " Disable the group " mm menuGroups anyOne menuItems anyOne subMenu menuGroups anyOne disable. " Enable the group " mm menuGroups anyOne menuItems anyOne subMenu menuGroups anyOne enable. Cheers, HernÃ¡n

2 2

FileSystem copyTo:
by Stephane Ducasse Feb. 3, 2018

Feb. 3, 2018

I have two folders: a/ and d/ and I want to copy file c in a but keeping its path. i.e. a/b/c copyTo: d and I want to get a/b/c and d/b/c It looks like I have to do all the logic to create intermediary folders (b) under d/ :( Stef

1 0