- Pharo-dev - lists.pharo.org

CompilationContext class>>initialize
by Stephan Eggermont Dec. 11, 2015

Dec. 11, 2015

Why do CompilationContext and CCompilationContext need super initialize in class side initialize? Stephan

2 1

a little poll on the importance of architecture
by Tudor Girba Dec. 11, 2015

Dec. 11, 2015

Hi, I created another little poll about the importance of architecture. If you have a Twitter account, feel free to participate: https://twitter.com/girba/status/675330047608299521 Cheers, Doru -- www.tudorgirba.com "Things happen when they happen, not when you talk about them happening."

1 0

a Mushroom architecture
by Robert Withers Dec. 11, 2015

Dec. 11, 2015

1 0

Ubuntu 14.04 with pharo-launcher
by Trussardi Dario Romano Dec. 11, 2015

Dec. 11, 2015

Ciao, on Ubuntu system 14.04 i load the Pharo-launcher support. Now all the pharo.image on the system run with the same pharo VM, but i have a image ( Glass TODE environment ) to load with specific VM and relative library. If i load it with the default pharo VM, when i do some Tode commands the system report: Error: External module not found. I think to create a new launcher application. I copy the /usr/share/applications/pharo-vm-desktop into pharoTode-vm.desktop [Desktop Entry] Name=Pharo Tode VM GenericName=Pharo Tode Virtual Machine Exec=pharo-vm-x %F Icon=pharo Terminal=false Type=Application StartupNotify=false Categories=Development; MimeType=application/x-pharo-image; NoDisplay=true but i don't understand how reference the specific Pharo VM. I have a gsDevKitHome/pharo directory with the todeClient.image, the pharo bash and pharo-vm subdirectory with the relative pharo-vm and relative lib* to connect with the glass environment. Thanks for considerations, Dario

5 5

Unified Property API and persistent properties (Pharo 5)
by Torsten Bergmann Dec. 10, 2015

Dec. 10, 2015

In Pharo 5 the "properties" API is unified (means you can associate properties to classes, methods, packages, ...). Really cool and a good step toward a unified and more flexible system. Exampel: |pck| pck := #'Foo-Kernel' asPackage. pck propertyAt: #'lastModified' put: DateAndTime now asString. pck propertyAt: #'generatedUsing' put: 'Pharo DynaCase'. pck properties So far it looks like the package properties are still transient - that means when you save the package and load in another image they will be empty again. Havent tried for class properties, ... Will this change in the near future so they are persistent? I wonder what the plans an next steps are in this area. Thanks T.

4 3

API for querying MC ancestors history?
by Mariano Martinez Peck Dec. 10, 2015

Dec. 10, 2015

Did someone ever finally started with an API to query a few things with a package history? To answer questions like... "in which version was this method deleted from this class". or "in which version was this class added" etc.. Thanks! -- Mariano http://marianopeck.wordpress.com

1 0

[pharo-project/pharo-core]
by GitHub Dec. 10, 2015

Dec. 10, 2015

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

1 0

[pharo-project/pharo-core] db7ddf: 50494
by GitHub Dec. 10, 2015

Dec. 10, 2015

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: db7ddf986f09c3821c725afa4917b234f9b80ea3 https://github.com/pharo-project/pharo-core/commit/db7ddf986f09c3821c725afa… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2015-12-10 (Thu, 10 Dec 2015) Changed paths: M Morphic-Core.package/Morph.class/instance/drop shadows/removeDropShadow.st M Morphic-Core.package/Morph.class/instance/drop shadows/shadowOffset_.st M Morphic-Widgets-Extra.package/DockingBarMenuItemMorph.class/instance/rounding/wantsRoundedCorners.st M Morphic-Widgets-Extra.package/DockingBarToggleMenuItemMorph.class/instance/accessing/wantsRoundedCorners.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50493.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50494.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50493.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50494.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st A Spec-Core.package/AbstractWidgetModel.class/instance/drag and drop/transferFor_from_.st M Spec-Core.package/AbstractWidgetModel.class/instance/initialization/initialize.st M Spec-Core.package/SpecAdapterBindings.class/instance/initialize/initializeBindings.st A Spec-Core.package/TransferModel.class/README.md A Spec-Core.package/TransferModel.class/class/specs/adapterName.st A Spec-Core.package/TransferModel.class/definition.st A Spec-Core.package/TransferModel.class/instance/accessing/from_.st A Spec-Core.package/TransferModel.class/instance/accessing/passenger.st A Spec-Core.package/TransferModel.class/instance/accessing/source.st A Spec-Core.package/TransferModel.class/instance/accessing/transfer_.st A Spec-Core.package/TransferModel.class/instance/initialize/initialize.st M Spec-Core.package/TreeModel.class/class/examples/example.st M Spec-MorphicAdapters.package/AbstractMorphicAdapter.class/instance/drag and drop - private/acceptDroppingMorph_event_inMorph_.st M Spec-MorphicAdapters.package/AbstractMorphicAdapter.class/instance/drag and drop - private/transferFor_from_.st M Spec-MorphicAdapters.package/MorphicAdapterBindings.class/instance/initialize/initializeBindings.st M Spec-MorphicAdapters.package/MorphicListAdapter.class/instance/widget API/acceptDroppingMorph_event_inMorph_.st A Spec-MorphicAdapters.package/MorphicTransferAdapter.class/README.md A Spec-MorphicAdapters.package/MorphicTransferAdapter.class/definition.st A Spec-MorphicAdapters.package/MorphicTransferAdapter.class/instance/factory/buildWidget.st A Spec-MorphicAdapters.package/MorphicTransferAdapter.class/instance/widget API/passenger.st A Spec-MorphicAdapters.package/MorphicTransferAdapter.class/instance/widget API/source.st M Spec-MorphicAdapters.package/MorphicTreeAdapter.class/instance/drag and drop - private/acceptDroppingMorph_event_inMorph_.st A Spec-MorphicAdapters.package/SpecTransferMorph.class/README.md A Spec-MorphicAdapters.package/SpecTransferMorph.class/definition.st A Spec-MorphicAdapters.package/SpecTransferMorph.class/instance/accessing/model.st A Spec-MorphicAdapters.package/SpecTransferMorph.class/instance/accessing/model_.st A Spec-MorphicAdapters.package/SpecTransferMorph.class/instance/accessing/passenger_.st A Spec-MorphicAdapters.package/SpecTransferMorph.class/instance/accessing/shouldCopy.st A Spec-MorphicAdapters.package/SpecTransferMorph.class/instance/accessing/source_.st A Spec-MorphicAdapters.package/SpecTransferMorph.class/instance/initialization/initialize.st Log Message: ----------- 50494 17216 Morph>>#removeDropShadow does not remove the shadowOffset https://pharo.fogbugz.com/f/cases/17216 17208 Remove rounded corners from MenuModel parent item https://pharo.fogbugz.com/f/cases/17208 16920 In TreeModel>>acceptDropBlock: the block receives morphs as arguments https://pharo.fogbugz.com/f/cases/16920 http://files.pharo.org/image/50/50494.zip

1 0

question re: String>>beginsWithEmpty:caseSensitive: failing on some test cases
by sheridan＠sheridan-mahoney.com Dec. 9, 2015

Dec. 9, 2015

Hi there, I have a single test case that causes String>>beginsWithEmpty:caseSensitive: to fail, as follows: ('ÃÃÃÃÃÃ' beginsWithEmpty: 'Ã©Ã¨Ã ' caseSensitive: false). What I am really wondering is what is the procedure for monitoring the lifetime of a failing test in Pharo? I would like to know, should I check in this test? I have a group of other tests that pass, and so could contribute a fuller test scenario. Or is it enough to just write up a bug report, and just re-run the test myself when the bug gets fixed? Many thanks, Sheridan

2 1

Call for Papers: Reflect'16, Workshop on Reflection and Runtime Meta-Programming Techniques
by Stefan Marr Dec. 9, 2015

Dec. 9, 2015

Call for Papers: Reflectâ16 =========================== Workshop on Reflection and Runtime Meta-Programming Techniques Co-located with Modularity 2016 March 14 or 15, 2016, MÃ¡laga, Spain Twitter @ReflectWorkshop http://2016.modularity.info/track/Reflect-2016-papers With modern mainstream languages embracing runtime reflection, for instance in JavaScript with proxies and Ruby with its culture of using meta-programming, the research on meta-architectures, reflective programming, and other meta-programming techniques have become relevant and timely once again. Over the last couple of years, these techniques saw a surge of interest benefiting from the JavaScript standardization process as well as performance improvements based on just-in-time compilation that increased their general acceptance. The Reflectâ16 workshop aims to bring together people who do research on reflection and runtime meta-programming, as well as users of such techniques to e.g. build applications, language extensions, or software tools. We invite contributions to the workshop on a wide range of topics related to design, implementation, and application of reflective APIs and runtime meta-programming techniques, as well as empirical studies and typing for such systems and languages. We welcome technical papers as well as work-in-progress and position papers from the academic as well as industrial perspective. Position paper should take a perhaps controversial stance on a specific topic and argue the position well. Topics of Interest ------------------ The topics of interest for the workshop include, but are not limited to: - applications to middleware, frameworks, and DSLs - reflection and metaobject protocols to enable tooling - meta-level architectures and reflective middleware for modern runtime platforms (e.g. IoT, cyber-physical systems, cloud/grid computing, exa-scale systems, smart grids, mobile systems) - optimization techniques to minimize runtime overhead of reflection - use for application-level runtime optimization - new language constructs for reflection and meta-programming - security in reflective systems and capability-based designs - application of reflective techniques to achieve adaptability, separation of concerns, code reuse, etc. - empirical studies to the dynamic behavior of reflective programs - application to enable complex concurrent systems - typing of reflective programs Workshop Format and Submissions ------------------------------- This workshop welcomes the presentation of mature work as well as discussion of new ideas and emerging problems as part of a mini-conference format. Furthermore, we plan for more interactive brainstorming and demonstration sessions between the formal presentations to enable an active exchange of ideas. The workshop papers will be published in both the electronic proceedings of the Modularity conference and in the ACM Digital Library, if not requested otherwise by the authors. Papers are to be submitted using the ACM sigplanconf style at 9pt font size. See http://www.acm.org/publications/article-templates/proceedings-template.html. position and work-in-progress paper: max. 4 pages technical paper: max. 8 pages demos and posters: 1-page abstract For the submission, please use the EasyChair system: https://easychair.org/conferences/?conf=reflect16 Important Dates --------------- abstract submission: January 11, 2016 paper submission: January 15, 2016 notification: February 6, 2016 camera-ready: February 13, 2016 all deadlines: Anywhere on Earth (AoE), i.e., GMT/UTCâ12:00 hour Workshop Organizers ------------------- Gilad Bracha, Google Shigeru Chiba, University of Tokyo Elisa Gonzalez Boix, Vrije Universiteit Brussel Stefan Marr, Johannes Kepler University Linz Program Committee ----------------- Daniele Bonetta, Oracle Labs, Austria Damien Cassou, University of Lille 1, France Siobhan Clarke, Trinity College Dublin, Ireland Stephane Ducasse, 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 Laurie Tratt, Kingâs College, UK Tom Van Cutsem, Bell Labs, Belgium Takuo Wantanabe, Tokyo Institute of Technology, Japan Tijs van der Storm, CWI, NL -- Stefan Marr Johannes Kepler UniversitÃ¤t Linz http://stefan-marr.de/research/

1 0