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

some small rubric issues
by Nicolai Hess June 25, 2015

June 25, 2015

Please con someone look at these issues, they are easy to fix (i think), but I can not write to rubrics repository 15273 <https://pharo.fogbugz.com/default.asp?15273> Issue regarding print block in the playground window 15312 <https://pharo.fogbugz.com/default.asp?15312> Wrong position for completion menu in Rubric/Playground 15663 <https://pharo.fogbugz.com/default.asp?15663> styling in spotter preview broken thanks, nicolai

3 2

Detecting the context/producer of code change announcements
by Martin Dias June 25, 2015

June 25, 2015

Hi everybody, I'm writing you to discuss about a new feature for Pharo. I would like to know your opinions and ideas. Thanks in advance. My point is that there are operations like "MC version load", "change set file in", "RB refactoring execution", or "class copy" that produce code change announcements (e.g. ClassAdded or MethodAdded), but subscribers can't know that. I mean, a subscriber that listens a ClassAdded can't know if it is product of a "high-level" operation, or if it was manually performed by the user in the Nautilus browser. I think Pharo should provide a way to detect this information, because it can be very useful. For example, I can tell you about a tool I work on: Epicea. Epicea logs code changes while developer works (like traditionally done with the .changes file), and the user can browse, undo and redo changes. Now, imagine that your vm crashed and then you want to recover "lost" changes... you don't want to see hundreds of changes produced by Monticello when loading packages: in this case, such changes are noise and make you waste time when selecting what to redo. In Epicea package I have a workaround for detecting some "high-level" operations, but Epicea would need support from Pharo for a nice implementation. Brainstorming on implementations. I think announcements are a good mechanism to implement this feature. A simple approach is to provide *begin* and *end* *announcements* (e.g. *MCVersionLoadBegin* and *MCVersionLoadEnd*). Then, somebody that subscribes to such announcements can have a stack or state machine to know the context where each code change announcement is produced. It would look like: MCVersionLoader >> load ... SystemAnnouncer uniqueInstance announce: (*MCVersionLoadBegin* versionName: ...). [ ... produce code changes ... ] *ensure:* [ SystemAnnouncer uniqueInstance announce: (*MCVersionLoadEnd* versionName: ...) ]. which may be re-written with a convenience method as: ... SystemAnnouncer uniqueInstance *announceBefore*: (MCVersionLoadBegin versionName: ...) *announceAfter*: (MCVersionLoadEnd versionName: ...) *do: *[ ... produce code changes ... ] but, going one step further, we could reify the concept of announcement *begin* and *end* like: ... *announcement := (MCVersionLoad versionName: ...).* SystemAnnouncer uniqueInstance announceBefore: (*AnnouncementBegin* of: announcement) announceAfter: (*AnnouncementEnd* of: announcement) do: [ ... produce code changes ... ] which could be re-written as: ... SystemAnnouncer uniqueInstance *announceBeforeAndAfter*: (MCVersionLoad versionName: ...) *do*: [ ... produce code changes ... ] I think any approach can work, but I'd love to have some feedback. Kind regards, MartÃn

6 11

GT needs love
by stepharo June 25, 2015

June 25, 2015

Hi guys Nicolas proposed several fixes of GT and we are waiting that someone with a bit of knowledge integrate them in GT. I can do it but I would prefer that somebody with knowledge takes 10 min to do it. Stef

3 3

[pharo-project/pharo-core] 875d5b: 50135
by GitHub June 25, 2015

June 25, 2015

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: 875d5b3e6c92aa75b40ab710e64af05d823575e4 https://github.com/pharo-project/pharo-core/commit/875d5b3e6c92aa75b40ab710… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2015-06-25 (Thu, 25 Jun 2015) Changed paths: M OpalCompiler-Core.package/OCASTTranslator.class/instance/visitor-double dispatching/visitMethodNode_.st M OpalCompiler-Core.package/OCASTTranslator.class/instance/visitor-double dispatching/visitNode_.st M OpalCompiler-Core.package/OCASTTranslator.class/instance/visitor-double dispatching/visitReturnNode_.st M OpalCompiler-Core.package/OCASTTranslator.class/instance/visitor-double dispatching/visitVariableNode_.st R OpalCompiler-Core.package/OCASTTranslator.class/instance/visitor-double dispatching/visitVariableWrite_.st A Reflectivity-Tests.package/ReflectiveMethodTest.class/instance/tests - reifications/testReifyGlobalVariable.st A Reflectivity.package/RFASTTranslator.class/instance/visitor-double dispatching/visitNode_.st A Reflectivity.package/RFVariableReification.class/instance/generate/genForGlobal.st M Reflectivity.package/RFVariableReification.class/instance/generate/genForRBVariableNode.st A Reflectivity.package/RFVariableReification.class/instance/generate/genForSlot.st R Reflectivity.package/extension/OCASTTranslator/instance/emitMetaLinkAfter_.st R Reflectivity.package/extension/OCASTTranslator/instance/emitMetaLinkBefore_.st R Reflectivity.package/extension/OCASTTranslator/instance/visitStoreIntoTempNode_.st R Reflectivity.package/extension/OCASTTranslator/instance/visitStorePopIntoTempNode_.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50134.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50135.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50134.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50135.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 50135 15838 Reflectivity: allow to reify #variable for Globals https://pharo.fogbugz.com/f/cases/15838 15837 Move all RF code from Opal to Opal Plugin https://pharo.fogbugz.com/f/cases/15837 http://files.pharo.org/image/50/50135.zip

1 0

[pharo-project/pharo-core]
by GitHub June 25, 2015

June 25, 2015

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

1 0

OSWindow and event managing
by Matthieu Lacaton June 25, 2015

June 25, 2015

Hello everyone, I would like to talk a bit about the way OSWindow makes events available for the user. Currently, a dedicated process with a priority of 60 gets SDL events, converts them into OSWindow events and then makes them available to the user via the OSWindowEventVisitor. Now my concern is that, by default, it is this same process that executes actions specified by the user. (Actually every event is forked to be executed in its own thread but with the same priority of 60 so as Pharo scheduler is not pre emptive it does not change the execution order) So basically, all the operations made in the main thread will be interrupted by the operations made in the event thread since the event thread has a higher priority. I get that it makes the window more responsive since its events are treated almost immediately but if you are not aware of what you are doing you can have some weird behaviors as in every multi-threaded program. It means that if I am a simple user and I want to use OSWindow simply, by default I need to deal with 2 processes and to handle some kind of concurrency even if my application is very simple. I find it a bit harsh. Shouldn't we provide the user with something simple and "unbreakable" by default but let him the possibility to do whatever he wants with extra work instead of providing him with something a bit more advanced by default but that needs extra work to make simple ? Maybe we could provide something a bit like SDL does. Put OSWindow events in a queue and then create mechanisms arround to manage this queue and let the user easily get events he wants. By default any application would be mono-processed but nothing would prevent the user to create a new process dedicated to event handling. What are your thoughts about all that ? Thanks, Matthieu

1 0

[pharo-project/pharo-core]
by GitHub June 25, 2015

June 25, 2015

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

1 0

[pharo-project/pharo-core] f1e4b4: 50134
by GitHub June 25, 2015

June 25, 2015

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: f1e4b4275da241f32f438cfc486d0be90d477551 https://github.com/pharo-project/pharo-core/commit/f1e4b4275da241f32f438cfc… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2015-06-25 (Thu, 25 Jun 2015) Changed paths: M NautilusRefactoring.package/NautilusRefactoring.class/instance/class/buildRenameRefactoringEngineFor_.st M OpalCompiler-Core.package/OCASTTranslator.class/instance/visitor-double dispatching/emitMessageNode_.st M OpalCompiler-Core.package/OCASTTranslator.class/instance/visitor-double dispatching/visitAssignmentNode_.st A Reflectivity.package/RFASTTranslator.class/instance/reflectivity/emitMetaLinkAfter_.st A Reflectivity.package/RFASTTranslator.class/instance/reflectivity/emitMetaLinkBefore_.st A Reflectivity.package/RFASTTranslator.class/instance/reflectivity/visitStoreIntoTempNode_.st A Reflectivity.package/RFASTTranslator.class/instance/reflectivity/visitStorePopIntoTempNode_.st A Reflectivity.package/RFASTTranslator.class/instance/visitor-double dispatching/emitMessageNode_.st A Reflectivity.package/RFASTTranslator.class/instance/visitor-double dispatching/visitAssignmentNode_.st A Reflectivity.package/RFASTTranslator.class/instance/visitor-double dispatching/visitMethodNode_.st A Reflectivity.package/RFASTTranslator.class/instance/visitor-double dispatching/visitReturnNode_.st A Reflectivity.package/RFASTTranslator.class/instance/visitor-double dispatching/visitVariableNode_.st A Reflectivity.package/RFASTTranslator.class/instance/visitor-double dispatching/visitVariableWrite_.st A Reflectivity.package/RFASTTranslatorForEffect.class/instance/visitor-double dispatching/emitMessageNode_.st A Reflectivity.package/RFASTTranslatorForEffect.class/instance/visitor-double dispatching/visitArrayNode_.st A Reflectivity.package/RFASTTranslatorForEffect.class/instance/visitor-double dispatching/visitBlockNode_.st A Reflectivity.package/RFASTTranslatorForEffect.class/instance/visitor-double dispatching/visitLiteralArrayNode_.st A Reflectivity.package/RFASTTranslatorForEffect.class/instance/visitor-double dispatching/visitLiteralNode_.st A Reflectivity.package/RFASTTranslatorForEffect.class/instance/visitor-double dispatching/visitParseErrorNode_.st A Reflectivity.package/RFASTTranslatorForEffect.class/instance/visitor-double dispatching/visitSequenceNode_.st A Reflectivity.package/RFASTTranslatorForEffect.class/instance/visitor-double dispatching/visitVariableNode_.st M Reflectivity.package/ReflectiveMethod.class/instance/evaluation/recompileAST.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50133.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50134.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50133.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50134.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 50134 15830 enable compiler subclass for Reflectivity, start to move hooks from superclass https://pharo.fogbugz.com/f/cases/15830 15836 Abort Rename class refactoring https://pharo.fogbugz.com/f/cases/15836 http://files.pharo.org/image/50/50134.zip

1 0

Pharo 4 and Roassal
by Juan June 25, 2015

June 25, 2015

Hi I recently tried experimenting with Pharo and Roassal and I found some problems, so I would like to know how to load Roassal in pharo 4 to retry everything from scratch and also see if the problems are due to some other cause. best regards JMDC

6 15

does anyone actually uses NewList?
by Esteban Lorenzano June 24, 2015

June 24, 2015

because we are targeting to remove it from system: it never worked properly and the design is not satisfactory. at the moment Iâm writing this, Stef is integrating the Fast Tableâ¦ the replacement for lists I started to write and I hope you (the community) help me finish :P Esteban

4 3