- Pharo-dev - lists.pharo.org

[pharo-project/pharo-core] 88cab8: 50487
by GitHub Dec. 5, 2015

Dec. 5, 2015

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: 88cab84fb6133980ee3626403fc4051134e52766 https://github.com/pharo-project/pharo-core/commit/88cab84fb6133980ee362640… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2015-12-05 (Sat, 05 Dec 2015) Changed paths: M Morphic-Core.package/Morph.class/instance/events-processing/handlesMouseMove_.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50486.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50487.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50486.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50487.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st R Shout.package/SHRBTextStyler.class/class/configuration/enableAstHighlightSetting_.st R Shout.package/SHRBTextStyler.class/class/configuration/useAstColoring.st R Shout.package/SHRBTextStyler.class/class/configuration/useAstColoring_.st M Shout.package/SHTextStylerST80.class/class/initialization/initialize.st R Shout.package/SHTextStylerST80.class/class/initialization/unload.st Log Message: ----------- 50487 17196 Remove check for event handler in #handlesMouseMove: https://pharo.fogbugz.com/f/cases/17196 17191 remove option #useAstColoring https://pharo.fogbugz.com/f/cases/17191 17079 no syntax highlighting in TimeProfilers code pane https://pharo.fogbugz.com/f/cases/17079 http://files.pharo.org/image/50/50487.zip

1 0

[pre-ANN][Job] two Pharo engineers for 2016
by Marcus Denker Dec. 5, 2015

Dec. 5, 2015

Hi, This is just a pre-announcement (We will write a formal call over the next days). We have the possibility to hire two programmers working in Pharo itself in 2016 -> one for one year -> one for one year with the possibility to extend another year. The place of work is Lille (due to the nature of the employment via Inria). If you are interested, please contact me. We will send a real announcement soon. Marcus

1 0

AST based syntax colouring: Shout cleanup possible
by marcus.denker＠inria.fr Dec. 5, 2015

Dec. 5, 2015

Hi, Interestingly with both Rubric and TxTxt we now use AST based syntax coverage by default (and the setting has no effect, it was just for PluggableTextMorph). As it seems that after the fixes that where done (mostly by Nicolai, thanks!!), the AST based syntax colouring is good enough to replace the one using SHParserST80. I am sure there are some smaller glitches still to be fixed, but it seems it has proven itself to the point we can start to clean up. SHParserST80 is used in addition by code completion, so we can not yet remove it yet, but we can radically simplify the SHTextStyler hierarchy. Anyone wants to give it a try? Marcus

1 0

[pharo-project/pharo-core] df0587: 50486
by GitHub Dec. 5, 2015

Dec. 5, 2015

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: df058777bc359dbcc0b72631e38e6cac232f4428 https://github.com/pharo-project/pharo-core/commit/df058777bc359dbcc0b72631… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2015-12-05 (Sat, 05 Dec 2015) Changed paths: R Nautilus.package/AbstractNautilusUI.class/instance/events handling/doubleClickOnGroup.st R Nautilus.package/AbstractNautilusUI.class/instance/menus behavior/createInitializerWithInstVars.st R Nautilus.package/AbstractNautilusUI.class/instance/menus behavior/restrictedBrowseHierarchy.st R Nautilus.package/AbstractNautilusUI.class/instance/plugins announcements/openClass.st R Nautilus.package/AbstractNautilusUI.class/instance/private/buildInitializerFor_.st R Nautilus.package/AbstractNautilusUI.class/instance/private/getGroupsKeyList.st R Nautilus.package/AbstractNautilusUI.class/instance/shortcuts/setClassShorcutsTo_.st R Nautilus.package/AbstractNautilusUI.class/instance/source code area/contentSelectionFor_.st M OpalCompiler-Core.package/AbstractCompiler.class/class/settings/compilerSettingsOn_.st R OpalCompiler-Core.package/CCompilationContext.class/class/accessing/warningAllowed.st R OpalCompiler-Core.package/CCompilationContext.class/class/accessing/warningAllowed_.st M OpalCompiler-Core.package/CCompilationContext.class/definition.st R OpalCompiler-Core.package/CCompilationContext.class/instance/accessing/warningAllowed.st R OpalCompiler-Core.package/CompilationContext.class/class/accessing/warningAllowed.st R OpalCompiler-Core.package/CompilationContext.class/class/accessing/warningAllowed_.st R OpalCompiler-Core.package/CompilationContext.class/instance/accessing/warningAllowed.st R OpalCompiler-Core.package/OCSemanticWarning.class/instance/accessing/errorNotification.st M OpalCompiler-Core.package/OCSemanticWarning.class/instance/correcting/defaultAction.st M Reflectivity.package/extension/RBProgramNode/instance/removeLink_.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50485.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50486.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50485.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50486.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st R Tool-Base.package/AbstractTool.class/instance/class/addCategoryIn_.st R Tool-Base.package/AbstractTool.class/instance/class/basicRemoveClass_.st R Tool-Base.package/AbstractTool.class/instance/method/findMethodIn_.st R Tool-Base.package/AbstractTool.class/instance/method/removeNonLocalSelector_from_.st R Tool-Base.package/AbstractTool.class/instance/method/selectMessageAndEvaluate_defaultValue_.st R Tool-Base.package/AbstractTool.class/instance/method/selectThenBrowseMessagesFrom_.st R Tool-Base.package/AbstractTool.class/instance/method/selectThenBrowseSendersOfMessagesFrom_.st R Tool-Base.package/AbstractTool.class/instance/method/selectThenGetSelectorAndSendQuery_to_with_selector_.st R Tool-Base.package/AbstractTool.class/instance/method/selectorFromPattern_withCaption_startingFrom_.st R Tool-Base.package/AbstractTool.class/instance/package/findPackageIn_.st R Tool-Base.package/AbstractTool.class/instance/package/packageFromPattern_withCaption_.st Log Message: ----------- 50486 17187 make link de- installation more stable https://pharo.fogbugz.com/f/cases/17187 17188 remove unsent methods from AbstracTool and Nautilus https://pharo.fogbugz.com/f/cases/17188 17163 remove Setting #warningAllowed https://pharo.fogbugz.com/f/cases/17163 http://files.pharo.org/image/50/50486.zip

1 0

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

Dec. 5, 2015

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

1 0

GTDebugger not draggable with latest VM
by Blondeau Vincent Dec. 4, 2015

Dec. 4, 2015

Hi, I have a problem on the latest Moose6.0 image. I was not able to open a Roassal view, I had a NativeBoost Generic failure... So I updated the VM to last stable, and, now, the GTdebugger and the Moose panel are not draggable anymore... Can somebody is able to reproduce the problem? Thanks Cheers, Vincent ________________________________ Ce message et les pi?ces jointes sont confidentiels et r?serv?s ? l'usage exclusif de ses destinataires. Il peut ?galement ?tre prot?g? par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir imm?diatement l'exp?diteur et de le d?truire. L'int?grit? du message ne pouvant ?tre assur?e sur Internet, la responsabilit? de Worldline ne pourra ?tre recherch?e quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'exp?diteur ne donne aucune garantie ? cet ?gard et sa responsabilit? ne saurait ?tre recherch?e pour tout dommage r?sultant d'un virus transmis. This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Worldline liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.

4 4

How to listen Monticello load start/end (and origin of changes)
by Martin Dias Dec. 4, 2015

Dec. 4, 2015

Hi, Doru asked me how does Epicea listen this information, and I created a snippet to demo it *in a plain Pharo 5 image* (no need to load Epicea before). Maybe somebody else is interested, that's why I share it with everybody. You can open a Transcript and evaluate the following snippet. After evaluation, you can add new methods in Nautilus and see the log in the Transcript. (The code is not very nice). Cheers, Martin "Listen load start" Job jobAnnouncer when: JobStart do: [ :aJobStart | | owner | owner := aJobStart job owner. (owner isKindOf: MCVersionLoader) ifTrue: [ ('Starting to load ', owner versions asArray asString) logCr ] ]. "Listen load end" Job jobAnnouncer when: JobEnd do: [ :aJobEnd | | owner | owner := aJobEnd job owner. (owner isKindOf: MCVersionLoader) ifTrue: [ ('Ending to load ', owner versions asArray asString) logCr ] ]. "Listen changes in the middle" SystemAnnouncer uniqueInstance when: MethodAdded do: [ :aMethodAdded | | mcLoaderJobOrNil | mcLoaderJobOrNil := Job current ifNil: [ nil ] ifNotNil: [ :currentJob | currentJob lookup: [ :job | job owner isKindOf: MCVersionLoader ] ifNone: [ nil ] ]. (aMethodAdded methodAdded printString, ' --- ', (mcLoaderJobOrNil ifNil: [ 'no info' ] ifNotNil: [ 'while loading ', mcLoaderJobOrNil owner versions asArray asString ])) logCr ]. "Try it loading" Gofer it smalltalkhubUser: 'MartinDias' project: 'AlarmClock'; package: 'AlarmClock'; load.

2 2

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

Dec. 4, 2015

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

1 0

[pharo-project/pharo-core] 7a8e6d: 50485
by GitHub Dec. 4, 2015

Dec. 4, 2015

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: 7a8e6d1b8907aa8fa9d5b71564122941517413f6 https://github.com/pharo-project/pharo-core/commit/7a8e6d1b8907aa8fa9d5b715… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2015-12-04 (Fri, 04 Dec 2015) Changed paths: M Monticello.package/MCVersion.class/instance/accessing/loadCompleteSnapshot.st M Nautilus.package/NautilusUI.class/instance/package filter/buildPackageSearch.st A OpalTools.package/extension/SymbolicBytecode/instance/gtSpotterCodePreviewIn_.st A OpalTools.package/extension/SymbolicBytecode/instance/spotterActDefault.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50484.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50485.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50484.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50485.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 50485 16964 Nautilus package search field cursor goes back to start when space is inserted at the end of the field https://pharo.fogbugz.com/f/cases/16964 17185 Broken changes view https://pharo.fogbugz.com/f/cases/17185 17172 SymbolicBytecode should be embeddable in Spotter https://pharo.fogbugz.com/f/cases/17172 http://files.pharo.org/image/50/50485.zip

1 0

Call for Papers: Constrained and Reactive Objects Workshop at Modularity 2016
by timfelgentreff Dec. 4, 2015

Dec. 4, 2015

CROW 2016 - Constrained and Reactive Objects Workshop The Constrained and Reactive Objects Workshop (CROW) invites papers that present research results related to using constraints and reactive programming in combination or integrated with imperative and object-oriented systems. This research area has recently received increasing interest again. Object-constraint, constraint-reactive, constraint-imperative systems and others were proposed in response to challenges posed by, for example, the requirements for applications to work across different devices and form-factors, to provide best-effort computing in the face of unreliable devices and networks, and to more fully utilise HPC technology. However, many questions remain. For example, the interactions among constraints, reactive or event-based programming, and mainstream imperative and object-oriented languages are still not well-understood, and different implementation techniques to combine these paradigms are still being explored. The lack of large applications written with combinations of these paradigms means that there is little experience with patterns and tools for such applications, and modularity mechanisms required for such large applications are in their infancy or completely absent. This workshop is intended to gather researchers working on using constraints or reactive programming in combination with mainstream imperative and object-oriented languages. The goal of this workshop is to present technical research results related to such systems, discuss applications, tools, and patterns used in these systems, and to define better the directions into which this field may evolve by providing overviews of existing work. Call for Papers Even though constraint-based and reactive programming are not new concepts, their combination and interaction with more mainstream imperative and object-oriented languages are receiving more and more attention. This workshop is an attempt to gather researchers working on models, languages, and implementations relating these paradigms. We welcome all submissions on language design, implementation, runtime systems, program analysis, software metrics, patterns, modularity principles, case-studies and benchmarks of systems that combine constraint-based or reactive programming with imperative paradigms. Of particular interest are topics from the following areas: â¢Study of the interactions of constraints and reactive programming with imperative language features such as object-oriented programming, mutable state, encapsulation, modules, or concurrency â¢Applications and case-studies that showcase examples in which the combination of constraints and reactive programming facilitates systems development â¢Empirical studies that motivate further research in the field â¢Patterns, modularity mechanisms, and best-practices for larger applications â¢IDEs and Tools â¢Language runtimes, virtual machine support, or compilers â¢Related fields that constraints and reactive programming can help facilitate, such as self-healing systems, best-effort computing, acceptability-oriented computing, or end-user programming Authors are invited to submit short position papers or long technical papers. using the ACM sigplanconf style at 9pt font size (see http://www.acm.org/publications/article-templates/proceedings-template.html) Short papers are imited to a maximum of 4 pages, excluding references. Long papers are limited to a maximum of 10 pages, including references. Submissions should not have been previously published nor be under review at other events. All submitted papers will be peer reviewed. Accepted papers will be published in the ACM Digital Library (unless the authors wish otherwise). Papers should be submitted via EasyChair: https://easychair.org/conferences/?conf=crow16. Workshop Format The format of the workshop will be that of a mini-conference. Participants can present their work in slots of 30 minutes including Q&A. Because it is often hard to understand the semantics of novel combinations of multiple paradigms as in this workshop just by looking at the code, we also encourage authors to present live demos. The goal of the workshop is to come to a better understanding of the the field. We hope to use the late afternoon session to draw conclusions from the presented work, and to identify fundamental paradigmatic problems that still need to be resolved to reconcile these different technologies and paradigms. Important Dates â¢Submission deadline: January 15, 2016 â¢Notification: February 6, 2016 â¢Camera ready: February 13, 2016 â¢Workshop: March 14-15, 2016 -- View this message in context: http://forum.world.st/Call-for-Papers-Constrained-and-Reactive-Objects-Work… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

1 0