December 2015 - Pharo-dev - lists.pharo.org

[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

How does Nautilus change highlighting for class definitions
by Damien Cassou Dec. 9, 2015

Dec. 9, 2015

Hi, in short: in which method is Nautilus adapting source-code highlighting based on the selection (class or method)? slightly longer: With Marco Naddeo we wanted to add ini-modules to Nautilus. Because an ini-module definition is a Smalltalk expression (just like a class definition), we want Nautilus to do source-code highlighting of an ini-module the same way it does for class definitions. How is Nautilus changing the source-code highlighting process depending on the selection (class or method)? Thank you -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill

4 6

layoutChanged call too much ?
by Ferlicot D. Cyril Dec. 9, 2015

Dec. 9, 2015

Hi, I wanted to execute an action each time we resize some window and I wanted to see easily if the method layoutChanged is call each time we resize it. To test that I added Â«Transcript crShow: DateAndTime now asStringÂ» inside the method TransforMorph>>#layoutChanged. I wanted to resize a TransformMorph and check the transcript. But went I opened the Transcriptâ¦ Surprise ! I had a lot of lines. I did the same in a new image of Pharo 5 and even with only 2 TransformMorph in the image there is A LOT of call to the method all the time. Is that normal ? Here an example: http://s11.postimg.org/n4rtz6xm9/Pharo_Screenshot.png -- Cyril Ferlicot http://www.synectique.eu 165 Avenue Bretagne Lille 59000 France

3 4

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

Dec. 9, 2015

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

1 0

[pharo-project/pharo-core] 804dcf: 50493
by GitHub Dec. 9, 2015

Dec. 9, 2015

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: 804dcf1adc2f65b37e1f8b493360d517bda3b3b9 https://github.com/pharo-project/pharo-core/commit/804dcf1adc2f65b37e1f8b49… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2015-12-09 (Wed, 09 Dec 2015) Changed paths: A Metacello-MC.package/extension/MCFileTreeRepository/instance/versionInfoFromVersionNamed_.st A Monticello-Tests.package/MCRepositoryTest.class/instance/tests/testCanCreateFiletreeRepositoryFromUrlWithRelativePath.st M MonticelloFileTree-Core.package/MCFileTreeRepository.class/class/utility/urlAsFileReference_.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50492.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50493.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50492.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50493.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 50493 17212 DNU on MCFileRepository class>>#basicFromUrl: https://pharo.fogbugz.com/f/cases/17212 17213 DNU when trying to retrieve version info from filetree repository https://pharo.fogbugz.com/f/cases/17213 http://files.pharo.org/image/50/50493.zip

1 0

[ ANN ] Pharo Days 2016
by Sven Van Caekenberghe Dec. 9, 2015

Dec. 9, 2015

Dear fellow Pharoers, Mark your calendars: on Thursday March 31 & Friday April 1 we are organising the Pharo Days 2016. This year we moved the location to Namur, Belgium, just a bit south of Brussels, at the very beautiful location of the âCercle de Wallonieâ overlooking the river Meuse. Weâll update the following page moving forward. https://medium.com/concerning-pharo/pharo-days-2016-c52fe4d7caf You can ask questions on any of the Pharo mailing lists or you can email the Pharo Board. Let's make this another success, together ! We hope to see as many of you as possible.

1 0

Re: [Pharo-dev] [squeak-dev] Re: [Cuis] Sorting Unicode strings (Re: [Unicode] collation sequences (Re: Unicode Support))
by H. Hirzel Dec. 9, 2015

Dec. 9, 2015

Hi Stephan What you mention is an edge case. A regular case which is not implemented yet is language insensitive sorting http://www.unicode.org/versions/Unicode8.0.0/UnicodeStandard-8.0.pdf <citation> In some circumstances, an application may need to do language-insensitive sortingâthat is, sorting of textual data without consideration of language-specific cultural expectations about how strings should be ordered. </citation> This is currently not the case as there is no normalization. As the Unicode Character Database [1] is already available in Squeak / Pharo (and could easily be loaded into Cuis) the implementation effort for language-insensitive sorting seems to be in reach without a big effort. [1] http://wiki.squeak.org/squeak/6244 Hannes On 12/9/15, Stephan Eggermont <stephan(a)stack.nl> wrote: > On 08-12-15 22:35, Dale Henrichs wrote: >> What I meant is that you can't _always_ use the code point for >> collation, i.e., sorting based on the value of code points is not always >> correct[1]. > > I have given up on universal sorting when I learned that dutch libraries > sorting of author names depends on the country of origin of the author. > So if Jan van Beek is dutch he will be sorted under B, while if he's > belgian under V. I haven't checked what happens if the author emigrates, > or changes nationality... > > Stephan > > > >

1 0

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

Dec. 9, 2015

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

1 0