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

[pharo-project/pharo-core]

by GitHub

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

Sept. 23, 2015

[pharo-project/pharo-core] 5df743: 50338

by GitHub

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: 5df743a26ea61bad6af7552562d60b4a41d9541f https://github.com/pharo-project/pharo-core/commit/5df743a26ea61bad6af75525… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2015-09-23 (Wed, 23 Sep 2015) Changed paths: R Refactoring-Critics.package/RBAbstractClassRule.class/README.md R Refactoring-Critics.package/RBAbstractClassRule.class/class/accessing/uniqueIdentifierName.st R Refactoring-Critics.package/RBAbstractClassRule.class/definition.st R Refactoring-Critics.package/RBAbstractClassRule.class/instance/accessing/group.st R Refactoring-Critics.package/RBAbstractClassRule.class/instance/accessing/name.st R Refactoring-Critics.package/RBAbstractClassRule.class/instance/accessing/rationale.st R Refactoring-Critics.package/RBAbstractClassRule.class/instance/accessing/severity.st R Refactoring-Critics.package/RBAbstractClassRule.class/instance/running/checkMethod_.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50337.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50338.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50337.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50338.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Spec-MorphicAdapters.package/MorphicTextAdapter.class/instance/accessing/interactionModel.st A System-Changes-FileServices.package/extension/ChangeSet/class/fileReaderServicesForFile_suffix_.st A System-Changes-FileServices.package/extension/ChangeSet/class/serviceFileIntoNewChangeSet.st A System-Changes-FileServices.package/extension/ChangeSet/class/services.st R System-Changes.package/ChangeSet.class/class/file services/fileReaderServicesForFile_suffix_.st R System-Changes.package/ChangeSet.class/class/file services/serviceFileIntoNewChangeSet.st R System-Changes.package/ChangeSet.class/class/file services/services.st Log Message: ----------- 50338 15858 review rule RBAbstractClassRule https://pharo.fogbugz.com/f/cases/15858 16402 Diff view partly broken (Refactorgin ChangesBrowser) https://pharo.fogbugz.com/f/cases/16402 16600 System-Changes should not depend on system-FileRegistry https://pharo.fogbugz.com/f/cases/16600 http://files.pharo.org/image/50/50338.zip

Sept. 23, 2015

List Archive Error: lists.pharo.org

by Torsten Bergmann

I get an Internal Server Error on: http://lists.pharo.org/mailman/listinfo

Sept. 23, 2015

Re: [Pharo-dev] multiple selection in Nautilus

by Peter UhnÃ¡k

I created a bug issue for it https://pharo.fogbugz.com/f/cases/16625/Right-click-in-Nautilus-lists-cance… As a meantime, you should be able to SHIFT+right-click (this selects the methods and opens the menu at once). Also shortcuts shouldn't be affected. Peter On Wed, Sep 23, 2015 at 2:41 PM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > Hi! > > Methods cannot be multiply selected. This is such a pityâ¦ > It makes me much slower > > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > >

Sept. 23, 2015

multiple selection in Nautilus

by Alexandre Bergel

Hi! Methods cannot be multiply selected. This is such a pityâ¦ It makes me much slower Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Sept. 23, 2015

[pharo-project/pharo-core]

by GitHub

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

Sept. 23, 2015

[pharo-project/pharo-core] d206d0: 50337

by GitHub

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: d206d023b7292356686c26e50f99e477fd0ef800 https://github.com/pharo-project/pharo-core/commit/d206d023b7292356686c26e5… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2015-09-23 (Wed, 23 Sep 2015) Changed paths: M ConfigurationOfRubric.package/ConfigurationOfRubric.class/instance/symbolic versions/stable_.st A ConfigurationOfRubric.package/ConfigurationOfRubric.class/instance/versions/version1187_.st M ConfigurationOfRubric.package/ConfigurationOfRubric.class/instance/versions/version1214Moose51_.st M Morphic-Base.package/SimpleBorder.class/instance/initialization/initialize.st M Refactoring-Critics.package/RBGuardClauseRule.class/README.md M Refactoring-Critics.package/RBGuardClauseRule.class/instance/accessing/name.st M Refactoring-Critics.package/RBGuardClauseRule.class/instance/accessing/rationale.st M Refactoring-Critics.package/RBToDoCollectRule.class/instance/accessing/name.st M Rubric.package/RubAbstractTextArea.class/instance/accessing text/textColor_.st M Rubric.package/RubSmalltalkEditor.class/class/keymapping/buildShortcutsOn_.st M Rubric.package/RubSmalltalkEditor.class/instance/menu messages/selectedSelector.st M Rubric.package/RubSmalltalkEditor.class/instance/menu messages/sendersOfIt.st M Rubric.package/RubTextSegmentMorph.class/instance/accessing/from_to_.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50336.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50337.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50336.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50337.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 50337 16616 "Eliminate guarding clauses" critic is named wrong and maybe should be removed https://pharo.fogbugz.com/f/cases/16616 16624 SimpleBorder borderStyle should initialize its width to a number https://pharo.fogbugz.com/f/cases/16624 16622 Merge latest rubric fixes https://pharo.fogbugz.com/f/cases/16622 http://files.pharo.org/image/50/50337.zip

Sept. 23, 2015

Some references to transcript should be changed into File stdout

by stepharo

Hi I have the impression that some references to Transcript should be rewritten as File stdout For example DummyUIManager>>unhandledErrorDefaultAction: anException Transcript show: '*** EXCEPTION ***'; cr. Transcript show: anException; cr. Transcript show: (thisContext stack first: (20 min: thisContext stack size)); cr. anException isResumable ifTrue: [ anException resume ] Stef

Sept. 23, 2015

Position for a PhD student on Hot software update

by Noury Bouraqadi

Hi, As part of the ongoing partnership between INRIA and Mines Douai, we have a funding for a PhD student to work on hot software update. You'll find below a description of the position. Best, Noury â Prof. Noury Bouraqadi Ecole des Mines de Douai http://car.mines-douai.fr/noury --- CONTACT Prof. S. Ducasse, stephane.ducasse AT inria.fr, INRIA, France Prof. N. Bouraqadi, noury.bouraqadi AT mines-douai.fr, Mines Douai, France Dr. M. Denker, marcus.denker AT inria.fr, INRIA, France Dr. L. Fabresse, luc.fabresse AT mines-douai.fr, Mines Douai, France CONTEXT Building next generation systems that can not be stopped is an interesting challenge for industry. Indded, when we need to replace current software for an upgrade or a bug fix, it is mandatory to stop the old running version, make the change and then restart the new version. However, there are situations where a such process is either impossible or at least undesirable because of the costs resulting from a shutdown (e.g production line, robot on mars, ...). We believe that software built with from the beginning the property to work indefinetly, will be by construction more robust to change, intrinsicly capable of evolution and more agile than traditional software. Dynamic languages such as CLOS, Ruby, Python, and Pharo provide a support for updates that only involve code change. Even if they are more advanced compared to other languages, their solutions ar mainly ad hoc and deserve being rethought. We believe it is important to have a mechanism and an infrastructure that allow adaptive and safe software updates. By "safe" we mean that this solution should support different conditions, such as a series of updates performed in the wrong sequence. In such situations, instances of changed classes should migrate in a satisfactory fashion. Safety also means verifying loaded changes. This means that changes should be checked and possibly rejected if they make the system instable or if they introduce errors. SCINTIFIC GOALS The questions we would like to target in this PhD are the following: - What is a good inftrastructure to support a dynamic and reliable code update? Do we need to analyse changes? - Does an infrastructure based on isolated environments is enough to ensure update safety? What atomicity level is required? - Which meta-object protocol is required to migrate objets? - Would it be interesting to have different version of a given class or package for the same software? BIBLIOGRAPHY . D. Duggan. Type-based hot swapping of running modules. In Intl. Conf. on Functional Programming, pages 62â73, 2001. . M. Denker, T. GÃ®rba, A. Lienhard, O. Nierstrasz, L. Renggli, and P. Zumkehr. Encapsulating and exploiting change with Changeboxes. In Proc. Int. Conference on Dynamic Languages, pages 25â49. ACM Digital Lib., 2007. . M. Dmitriev. Safe Class and Data Evolution in Large and Long-Lived Java Applications. PhD thesis, University of Glasgow, 2001. . M. Hicks and S. Nettles. Dynamic software updating. ACM Transactions on Programming Languages and Systems, 27(6):1049â1096, nov 2005. . J. Kephart. Research challenges of autonomic computing. In ICSE 2005, pages 15â22, may 2005. . G. Kniesel. Type-safe delegation for run-time component adaptation. In R. Guerraoui, editor, Proceedings ECOOP â99, volume 1628 of LNCS, pages 351â366, Lisbon, Portugal, June 1999. Springer-Verlag. . I. Neamtiu, M. W. Hicks, G. Stoyle, and M. Oriol. Practical dynamic software updating for c. In PLDI, pages 72â83, 2006. . G Polito, StÃ©phane Ducasse, N Bouraqadi, L Fabresse, M Mattone. Virtualization Support for Dynamic Core Library Update. Onward!, Oct 2015, Pittsburg, USA. . X. Ren, F. Shah, F. Tip, B. Ryder, and O. Chesley. Chianti: A tool for change impact analysis of Java programs. In Proceedings of OOPSLA 2004), pages 432â448, 2004.

Sept. 23, 2015

reviews needed (collection of rubric fixes)

by Nicolai Hess

Some reviews needed for latest fixes I added to Rubric repository: Issue 16622 Merge latest rubric fixes(and subcases). btw the monkey does not check the issue 16622 (all subcases are resolved and a configuration is provided, did I miss something?) nicolai

Sept. 23, 2015

- 250 * 1.5 is not the same as 250 * 1.5

by stepharo

Hi guys I think that this is quite bad that - 250 * 1.5 returns -2.25 while -250 * 1.5 return 375 stef

Sept. 23, 2015

Re: [Pharo-dev] ConfigurationOfRoassal2 broken

by Alexandre Bergel

> Can anyone explain ConfigurationOfRoassal2? Not me :-) > Where does that work? I have just added: development: spec <symbolicVersion: #'development'> spec for: #'common' version: '1.4-baseline'. spec for: #'pharo4.x' version: '1.5-baseline'. spec for: #'pharo5.x' version: '1.6-baselineâ. stable: spec <symbolicVersion: #'stable'> spec for: #'common' version: '1.11'. spec for: #'pharo4.x' version: '1.13'. spec for: #'pharo3.x' version: '1.6'. spec for: #'pharo5.x' version: '1.16'. I have no idea whether this is sufficient or not. Alexandre > > stable: spec > <symbolicVersion: #'stable'> > > spec for: #'common' version: '1.11'. > spec for: #'pharo4.x' version: '1.13'. > spec for: #'pharo3.x' version: '1.6'. > > development: spec > <symbolicVersion: #'development'> > > spec for: #'common' version: '1.4-baseline'. > spec for: #'pharo4.x' version: '1.5-baseline'. > > > > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Sept. 22, 2015

Re: [Pharo-dev] Help with RBTransformationRule needed!

by Thierry Goubier

Le 22/09/2015 19:14, Jan Vrany a Ã©crit : > >> RBTransformationRule (you need to activate that verificationBlock >> when >> you create your rewriter). > > Yes, and this is the tricky bit :-) Because there's no guarantee that > this block is functional. For example, it may access context ivar > which, by the time UI is retrieving intervals is already nilled out > or even filled again with some other unrelated context if you're > reusing rule instances (but if not, you may run into performance > problems...) I'm not sure I see the issue. That block is evaluated just when you match, before the rewrite. So, at that point, everything is valid. You're right, the node may not be valid anymore after the rewrite if I record the node. But if I record a copy of that source and the index (you ask complete source to that node and startPosition / stopPosition) then you're set for highlighting. Thierry

Sept. 22, 2015

Re: [Pharo-dev] [Reflectivity] Slides ESUG talk

by Marcus Denker

> On 22 Sep 2015, at 17:23, roberto.minelli(a)usi.ch wrote: > > Hi Marcus, > > I am finally playing with Reflectivity. In the first place, thanks a lot for this contribution! > > I am wondering what is the âcorrectâ way to âremoveâ a MetaLink. Is it enough to call #uninstall on the MetaLink Yes! > or should I also recompile the class/method where the link is installed? If you recompile, you remove all links. (even the ones others installed). In the tests I do that often to be sure everything is clean. > I spotted a problem with the control #after. If you try to pass #arguments to the meta, an error is returned. To reproduce: http://ws.stfx.eu/ONC4K9KQRTNQ > > Is this behavior somewhat desired, or is a bug? > Bug, I will fix it... > Dictionary>>errorKeyNotFound: > [ self errorKeyNotFound: key ] in Dictionary>>at: in Block: [ self errorKeyNotFound: key ] > Dictionary>>at:ifAbsent: > Dictionary>>at: > IRPushClosureCopy>>indexForVarNamed: > IRTranslatorV2>>visitPushTemp: > IRPushTemp>>accept: > IRTranslatorV2(IRVisitor)>>visitNode: > IRTranslatorV2>>visitInstruction: > [ :instr | self visitInstruction: instr ] in IRTranslatorV2(IRVisitor)>>visitSequence: in Block: [ :instr | self visitInstruction: instr ] > OrderedCollection>>do: > IRSequence>>do: > IRTranslatorV2(IRVisitor)>>visitSequence: > IRTranslatorV2>>visitSequence: > IRSequence>>accept: > IRTranslatorV2(IRVisitor)>>visitNode: > [ :each | self visitNode: each ] in IRTranslatorV2(IRVisitor)>>visitNodes: in Block: [ :each | self visitNode: each ] > SortedCollection(OrderedCollection)>>do: > IRTranslatorV2(IRVisitor)>>visitNodes: > IRTranslatorV2>>visitSequences: > IRTranslatorV2>>visitMethod: > IRMethod>>accept: > IRTranslatorV2(IRVisitor)>>visitNode: > IRMethod>>generate: > IRMethod>>compiledMethodWith: > RBMethodNode>>generate: > ReflectiveMethod>>recompileAST > ReflectiveMethod>>compileAndInstallCompiledMethod > ReflectiveMethod>>run:with:in: > UndefinedObject>>DoIt > > Cheers, > Roberto > >> On 04 Sep 2015, at 14:16, Marcus Denker <marcus.denker(a)inria.fr> wrote: >> >> Hi Roberto, >> >> Very good! I am now working on #after for methods+sequence. *And* primitives... this should all be committed early next week. >> >> After that, I need to actually use it to find remaining problems, so this is very good that you will start now. >> >> Marcus >> >> On Thu, Sep 3, 2015 at 2:50 PM, roberto.minelli(a)usi.ch <roberto.minelli(a)usi.ch> wrote: >> Very good talk Marcus. >> >> In the next weeks I will finally have some time to try Reflectivity out! >> >> Thanks a lot for all your effort! >> >> Cheers, >> Roberto >> >>> On 31 Jul 2015, at 13:23, Marcus Denker <marcus.denker(a)inria.fr> wrote: >>> >>> >>>> On 15 Jul 2015, at 10:15, Marcus Denker <marcus.denker(a)inria.fr> wrote: >>>> >>>> Hi, >>>> >>>> the slides for my ESUG talk are online: >>>> >>>> http://www.slideshare.net/MarcusDenker/reflection-in-pharo5 >>>> >>>> >>> >>> Video is online, too: >>> >>> https://www.youtube.com/watch?v=Ik539CtjtTI >>> >>> >>> >>> Marcus >>> >> >> >> >> >> -- >> -- >> Marcus Denker -- denker(a)acm.org >> http://www.marcusdenker.de >

Sept. 22, 2015

Re: [Pharo-dev] Help with RBTransformationRule needed!

by Jan Vrany

> RBTransformationRule (you need to activate that verificationBlock > when > you create your rewriter). Yes, and this is the tricky bit :-) Because there's no guarantee that this block is functional. For example, it may access context ivar which, by the time UI is retrieving intervals is already nilled out or even filled again with some other unrelated context if you're reusing rule instances (but if not, you may run into performance problems...)

Sept. 22, 2015

Re: [Pharo-dev] Help with RBTransformationRule needed!

by Thierry Goubier

Le 22/09/2015 17:56, Yuriy Tymchuk a Ã©crit : > Hi everyone, > > I need someone who knows how RBParseTreeRewriter & co. work. May of > quality rules are implemented as rewrite rules which is cool. But > they donât report the interval in source code which can be > highlighted to help with understanding of the issue. > > Nowâ¦ the check happens in RBTransformationRule>>#checkMethod:. Is it > possible to obtain the matched string there? Because in that case we > can get highlighting working which will be very useful. Silly me. It's so simple: | rw | rw := RBParseTreeRewriter new. rw replace: ' `#a `{:aNode | aNode value isCharacter}' with: '`#a newMessage' when: [:n | n logCr. false]. Use the when: block argument to trace all the matched nodes. Once you have the nodes, you can highlight them. Thierry > Cheers! Uko >

Sept. 22, 2015

Re: [Pharo-dev] Help with RBTransformationRule needed!

by Thierry Goubier

Le 22/09/2015 18:26, Jan Vrany a Ã©crit : > Yeah, I remember this is a pain. When I did years ago what > you're doing now with QA, I ended up practicing black magic, > sacrificing chickens and other things you'd better not to know. > > IIRC, the trick is to turn rewrite rules in ParseTreeEnvironment > into search rules and then run the searches. Now this is tricky > as these rules quite often refers to blocks, which then refers to outer > contexts and you need these blocks do something different now (report > nodes rather then transform stuff). This is the main problem. I think what you can simply do is trap the place where the rewrites are done, in RBStringReplaceRule. There is a verificationBlock instance variable which sees every match node, as far as I can read through the code, and this would change a bit the interface to call the rewrites in RBTransformationRule (you need to activate that verificationBlock when you create your rewriter). As far as I can see, if verificationBlock print its argument to the Transcript and returns false, your rewriter becomes a searcher which print every match to the transcript. Thierry > If you have the guts, you may find the code here: > > https://bitbucket.org/janvrany/stx-goodies-smallsense > and here: > http://swing.fit.cvut.cz/hg/stx.goodies.refactoryBrowser/ > > (alternatively, downlaod https://swing.fit.cvut.cz/projects/stx-jv/ > and browse the code in Smalltalk browser). > > You may want to trace the code starting from > ParseTreeEnvironment>>selectionIntervalsForSource:tree:do: > RBParseTreeRule>>copyMatchDo: and implementors is also > worth mentioning. > > After doing this, I concluded that SmallLint as it's now is not > well designed for this task and it would need a significant > refactoring. However, as always, I was never given time to do it. > > HTH, Jan > > > On Tue, 2015-09-22 at 17:56 +0200, Yuriy Tymchuk wrote: >> Hi everyone, >> >> I need someone who knows how RBParseTreeRewriter & co. work. May of >> quality rules are implemented as rewrite rules which is cool. But >> they donât report the interval in source code which can be >> highlighted to help with understanding of the issue. >> >> Nowâ¦ the check happens in RBTransformationRule>>#checkMethod:. Is it >> possible to obtain the matched string there? Because in that case we >> can get highlighting working which will be very useful. >> >> Cheers! >> Uko >> > >

Sept. 22, 2015

Re: [Pharo-dev] Help with RBTransformationRule needed!

by Jan Vrany

Yeah, I remember this is a pain. When I did years ago what you're doing now with QA, I ended up practicing black magic, sacrificing chickens and other things you'd better not to know. IIRC, the trick is to turn rewrite rules in ParseTreeEnvironment into search rules and then run the searches. Now this is tricky as these rules quite often refers to blocks, which then refers to outer contexts and you need these blocks do something different now (report nodes rather then transform stuff). This is the main problem. If you have the guts, you may find the code here: https://bitbucket.org/janvrany/stx-goodies-smallsense and here: http://swing.fit.cvut.cz/hg/stx.goodies.refactoryBrowser/ (alternatively, downlaod https://swing.fit.cvut.cz/projects/stx-jv/ and browse the code in Smalltalk browser). You may want to trace the code starting from ParseTreeEnvironment>>selectionIntervalsForSource:tree:do: RBParseTreeRule>>copyMatchDo: and implementors is also worth mentioning. After doing this, I concluded that SmallLint as it's now is not well designed for this task and it would need a significant refactoring. However, as always, I was never given time to do it. HTH, Jan On Tue, 2015-09-22 at 17:56 +0200, Yuriy Tymchuk wrote: > Hi everyone, > > I need someone who knows how RBParseTreeRewriter & co. work. May of > quality rules are implemented as rewrite rules which is cool. But > they donât report the interval in source code which can be > highlighted to help with understanding of the issue. > > Nowâ¦ the check happens in RBTransformationRule>>#checkMethod:. Is it > possible to obtain the matched string there? Because in that case we > can get highlighting working which will be very useful. > > Cheers! > Uko >

Sept. 22, 2015

Re: [Pharo-dev] Help with RBTransformationRule needed!

by Thierry Goubier

Le 22/09/2015 17:56, Yuriy Tymchuk a Ã©crit : > Hi everyone, > > I need someone who knows how RBParseTreeRewriter & co. work. May of > quality rules are implemented as rewrite rules which is cool. But > they donât report the interval in source code which can be > highlighted to help with understanding of the issue. > > Nowâ¦ the check happens in RBTransformationRule>>#checkMethod:. Is it > possible to obtain the matched string there? Because in that case we > can get highlighting working which will be very useful. Hi Uko, it seems all the information is in the context of the RBParseTreeRewriter instance, but I'm not finding how to get the top-level node (the root of the tree which will be replaced), knowing that you may have multiple matches in a method (i.e. that there is multiple nodes). Thierry

Sept. 22, 2015

Help with RBTransformationRule needed!

by Yuriy Tymchuk

Hi everyone, I need someone who knows how RBParseTreeRewriter & co. work. May of quality rules are implemented as rewrite rules which is cool. But they donât report the interval in source code which can be highlighted to help with understanding of the issue. Nowâ¦ the check happens in RBTransformationRule>>#checkMethod:. Is it possible to obtain the matched string there? Because in that case we can get highlighting working which will be very useful. Cheers! Uko

Sept. 22, 2015

Re: [Pharo-dev] [Reflectivity] Slides ESUG talk

by roberto.minelli＠usi.ch

Hi Marcus, I am finally playing with Reflectivity. In the first place, thanks a lot for this contribution! I am wondering what is the âcorrectâ way to âremoveâ a MetaLink. Is it enough to call #uninstall on the MetaLink or should I also recompile the class/method where the link is installed? I spotted a problem with the control #after. If you try to pass #arguments to the meta, an error is returned. To reproduce: http://ws.stfx.eu/ONC4K9KQRTNQ Is this behavior somewhat desired, or is a bug? Dictionary>>errorKeyNotFound: [ self errorKeyNotFound: key ] in Dictionary>>at: in Block: [ self errorKeyNotFound: key ] Dictionary>>at:ifAbsent: Dictionary>>at: IRPushClosureCopy>>indexForVarNamed: IRTranslatorV2>>visitPushTemp: IRPushTemp>>accept: IRTranslatorV2(IRVisitor)>>visitNode: IRTranslatorV2>>visitInstruction: [ :instr | self visitInstruction: instr ] in IRTranslatorV2(IRVisitor)>>visitSequence: in Block: [ :instr | self visitInstruction: instr ] OrderedCollection>>do: IRSequence>>do: IRTranslatorV2(IRVisitor)>>visitSequence: IRTranslatorV2>>visitSequence: IRSequence>>accept: IRTranslatorV2(IRVisitor)>>visitNode: [ :each | self visitNode: each ] in IRTranslatorV2(IRVisitor)>>visitNodes: in Block: [ :each | self visitNode: each ] SortedCollection(OrderedCollection)>>do: IRTranslatorV2(IRVisitor)>>visitNodes: IRTranslatorV2>>visitSequences: IRTranslatorV2>>visitMethod: IRMethod>>accept: IRTranslatorV2(IRVisitor)>>visitNode: IRMethod>>generate: IRMethod>>compiledMethodWith: RBMethodNode>>generate: ReflectiveMethod>>recompileAST ReflectiveMethod>>compileAndInstallCompiledMethod ReflectiveMethod>>run:with:in: UndefinedObject>>DoIt Cheers, Roberto > On 04 Sep 2015, at 14:16, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > Hi Roberto, > > Very good! I am now working on #after for methods+sequence. *And* primitives... this should all be committed early next week. > > After that, I need to actually use it to find remaining problems, so this is very good that you will start now. > > Marcus > > On Thu, Sep 3, 2015 at 2:50 PM, roberto.minelli(a)usi.ch <roberto.minelli(a)usi.ch> wrote: > Very good talk Marcus. > > In the next weeks I will finally have some time to try Reflectivity out! > > Thanks a lot for all your effort! > > Cheers, > Roberto > > > On 31 Jul 2015, at 13:23, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > > > > >> On 15 Jul 2015, at 10:15, Marcus Denker <marcus.denker(a)inria.fr> wrote: > >> > >> Hi, > >> > >> the slides for my ESUG talk are online: > >> > >> http://www.slideshare.net/MarcusDenker/reflection-in-pharo5 > >> > >> > > > > Video is online, too: > > > > https://www.youtube.com/watch?v=Ik539CtjtTI > > > > > > > > Marcus > > > > > > > -- > -- > Marcus Denker -- denker(a)acm.org > http://www.marcusdenker.de

Sept. 22, 2015

[pharo-project/pharo-core]

by GitHub

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

Sept. 22, 2015

[pharo-project/pharo-core] 88ba5f: 50336

by GitHub

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: 88ba5fe1e6c51e2b28e1b31811a3b77d5d2922cc https://github.com/pharo-project/pharo-core/commit/88ba5fe1e6c51e2b28e1b318… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2015-09-22 (Tue, 22 Sep 2015) Changed paths: M Collections-Unordered.package/Dictionary.class/instance/accessing/at_ifPresent_ifAbsent_.st M Collections-Unordered.package/SmallDictionary.class/instance/accessing - values/at_ifPresent_ifAbsent_.st M ContributingToTheCatalogHelp.package/ContributingToTheCatalogHelp.class/README.md M ContributingToTheCatalogHelp.package/ContributingToTheCatalogHelp.class/class/as yet unclassified/pages.st R ContributingToTheCatalogHelp.package/ContributingToTheCatalogHelp.class/class/pages/AddingYourProject.st A ContributingToTheCatalogHelp.package/ContributingToTheCatalogHelp.class/class/pages/addingYourProject.st M ContributingToTheCatalogHelp.package/ContributingToTheCatalogHelp.class/class/pages/introduction.st M Fuel.package/FLLargeIdentityDictionary.class/instance/accessing/at_ifPresent_ifAbsent_.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50335.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50336.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50335.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50336.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st A System-Announcements.package/ManifestSystemAnnouncements.class/class/meta-data - dependency analyser/ignoredDependencies.st M System-Hashing.package/SHA1.class/instance/private/initializeTotalsArray.st M System-Hashing.package/SHA1.class/instance/private/processBufferUsingPrimitives_.st M System-Hashing.package/SHA256.class/instance/private/initializeTotalsArray.st M System-OSEnvironments.package/OSEnvironment.class/instance/accessing/at_ifPresent_ifAbsent_.st Log Message: ----------- 50336 16603 System-Hashing should not depend on Graphics Primitives https://pharo.fogbugz.com/f/cases/16603 16615 Improve ContributingToTheCatalogHelp https://pharo.fogbugz.com/f/cases/16615 16614 To use at:ifPresent:ifAbsent:, ifPresent block argument should not be mandatory https://pharo.fogbugz.com/f/cases/16614 http://files.pharo.org/image/50/50336.zip

Sept. 22, 2015

Re: [Pharo-dev] Incorrect invalidation report

by Marcus Denker

Yes, something goes wrongâ¦ can you add an issue? > On 21 Sep 2015, at 14:58, Ben Coman <btc(a)openinworld.com> wrote: > > Before this report timesout, could someone knowing the CI backend > check this validation report... > > https://ci.inria.fr/pharo/job/Pharo-5.0-Issue-Validator/14283//artifact/val… > > The validation seems to have failed yet been reported as a success. > cheers -ben >

Sept. 22, 2015

Re: [Pharo-dev] TextAttributes in source code or class comment?

by phil＠highoctane.be

On Tue, Sep 22, 2015 at 9:13 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Hi, > > I think that having Pillar in comments is definitely the way to go. > > In: > > http://www.humane-assessment.com/blog/writing-pillar-books-with-the-gtinspe… > > I show also an extension that renders comments with PIllar highlighting. > This is working now in an inspector, but the same principle can be applied > to other browsers. > Yes, that's what I tried in the past. The ability to associate graphics explaining structures is really useful there. Phil > > Cheers, > Doru > > > > On Tue, Sep 22, 2015 at 8:47 AM, Christophe Demarey < > Christophe.Demarey(a)inria.fr> wrote: > >> >> Le 22 sept. 2015 Ã 07:49, philippe.back(a)highoctane.be a Ã©crit : >> >> >> Le 22 sept. 2015 07:40, "Sven Van Caekenberghe" <sven(a)stfx.eu> a Ã©crit : >> > >> > >> > > On 21 Sep 2015, at 23:53, stepharo <stepharo(a)free.fr> wrote: >> > > >> > > I think that having metadata (style) language and data (source code) >> mixed together is a bad idea. >> > > I never like the ]lang[ tag because it is a huge hack. It does not >> even exist in the Smalltalk syntax!!! >> > > We save code that the parser cannot parse. What we fun idea. >> > > So people are bashing for backward compatibility and we remove a bad >> way to encode >> > > metadata then suddenly it looks like we were doing something bad. >> > > >> > > Stef >> > >> > I am with Stef, it is a silly idea to mix the two. Nobody uses this in >> Pharo. Cleaning up means simplifying too. >> >> In the code no. But in the comments, that would be good to have back. In >> color form. As we can write pillar class comments, can't we render them ? >> Moose as an editor/viewer for pillar files >> >> >> Yes, it is where we want to go: use Pillar for styled comments. >> Once we have that, we can remove Text styling from source code / comments. >> >> > > > -- > www.tudorgirba.com > > "Every thing has its own flow" >

Sept. 22, 2015

Re: [Pharo-dev] TextAttributes in source code or class comment?

by Thierry Goubier

2015-09-22 9:10 GMT+02:00 Sven Van Caekenberghe <sven(a)stfx.eu>: > > > On 22 Sep 2015, at 08:47, Christophe Demarey < > Christophe.Demarey(a)inria.fr> wrote: > > > > > > Le 22 sept. 2015 Ã 07:49, philippe.back(a)highoctane.be a Ã©crit : > > > >> > >> Le 22 sept. 2015 07:40, "Sven Van Caekenberghe" <sven(a)stfx.eu> a Ã©crit > : > >> > > >> > > >> > > On 21 Sep 2015, at 23:53, stepharo <stepharo(a)free.fr> wrote: > >> > > > >> > > I think that having metadata (style) language and data (source > code) mixed together is a bad idea. > >> > > I never like the ]lang[ tag because it is a huge hack. It does not > even exist in the Smalltalk syntax!!! > >> > > We save code that the parser cannot parse. What we fun idea. > >> > > So people are bashing for backward compatibility and we remove a > bad way to encode > >> > > metadata then suddenly it looks like we were doing something bad. > >> > > > >> > > Stef > >> > > >> > I am with Stef, it is a silly idea to mix the two. Nobody uses this > in Pharo. Cleaning up means simplifying too. > >> > >> In the code no. But in the comments, that would be good to have back. > In color form. As we can write pillar class comments, can't we render them > ? Moose as an editor/viewer for pillar files > >> > >> > > > > Yes, it is where we want to go: use Pillar for styled comments. > > Once we have that, we can remove Text styling from source code / > comments. > > Yes, inside a comment, which should be totally opaque from a language > syntax standpoint, you can do whatever you want: HTML, Markdown, Pillar, > Pier, ... > But, if you want to integrate with IDE support for that extended syntax, then it would be nice to have an idea of the syntax used... Otherwise we're back at the special leading char to determine the format :( Side opinion to come to the point: I think that Pillar would make a better implementation than the ]style[ stuff. Thierry

Sept. 22, 2015

Re: [Pharo-dev] TextAttributes in source code or class comment?

by Tudor Girba

Hi, I think that having Pillar in comments is definitely the way to go. In: http://www.humane-assessment.com/blog/writing-pillar-books-with-the-gtinspe… I show also an extension that renders comments with PIllar highlighting. This is working now in an inspector, but the same principle can be applied to other browsers. Cheers, Doru On Tue, Sep 22, 2015 at 8:47 AM, Christophe Demarey < Christophe.Demarey(a)inria.fr> wrote: > > Le 22 sept. 2015 Ã 07:49, philippe.back(a)highoctane.be a Ã©crit : > > > Le 22 sept. 2015 07:40, "Sven Van Caekenberghe" <sven(a)stfx.eu> a Ã©crit : > > > > > > > On 21 Sep 2015, at 23:53, stepharo <stepharo(a)free.fr> wrote: > > > > > > I think that having metadata (style) language and data (source code) > mixed together is a bad idea. > > > I never like the ]lang[ tag because it is a huge hack. It does not > even exist in the Smalltalk syntax!!! > > > We save code that the parser cannot parse. What we fun idea. > > > So people are bashing for backward compatibility and we remove a bad > way to encode > > > metadata then suddenly it looks like we were doing something bad. > > > > > > Stef > > > > I am with Stef, it is a silly idea to mix the two. Nobody uses this in > Pharo. Cleaning up means simplifying too. > > In the code no. But in the comments, that would be good to have back. In > color form. As we can write pillar class comments, can't we render them ? > Moose as an editor/viewer for pillar files > > > Yes, it is where we want to go: use Pillar for styled comments. > Once we have that, we can remove Text styling from source code / comments. > > -- www.tudorgirba.com "Every thing has its own flow"

Sept. 22, 2015

Re: [Pharo-dev] TextAttributes in source code or class comment?

by Sven Van Caekenberghe

> On 22 Sep 2015, at 08:47, Christophe Demarey <Christophe.Demarey(a)inria.fr> wrote: > > > Le 22 sept. 2015 Ã 07:49, philippe.back(a)highoctane.be a Ã©crit : > >> >> Le 22 sept. 2015 07:40, "Sven Van Caekenberghe" <sven(a)stfx.eu> a Ã©crit : >> > >> > >> > > On 21 Sep 2015, at 23:53, stepharo <stepharo(a)free.fr> wrote: >> > > >> > > I think that having metadata (style) language and data (source code) mixed together is a bad idea. >> > > I never like the ]lang[ tag because it is a huge hack. It does not even exist in the Smalltalk syntax!!! >> > > We save code that the parser cannot parse. What we fun idea. >> > > So people are bashing for backward compatibility and we remove a bad way to encode >> > > metadata then suddenly it looks like we were doing something bad. >> > > >> > > Stef >> > >> > I am with Stef, it is a silly idea to mix the two. Nobody uses this in Pharo. Cleaning up means simplifying too. >> >> In the code no. But in the comments, that would be good to have back. In color form. As we can write pillar class comments, can't we render them ? Moose as an editor/viewer for pillar files >> >> > > Yes, it is where we want to go: use Pillar for styled comments. > Once we have that, we can remove Text styling from source code / comments. Yes, inside a comment, which should be totally opaque from a language syntax standpoint, you can do whatever you want: HTML, Markdown, Pillar, Pier, ...

Sept. 22, 2015

Re: [Pharo-dev] TextAttributes in source code or class comment?

by Christophe Demarey

Le 22 sept. 2015 Ã 07:49, philippe.back(a)highoctane.be a Ã©crit : > > Le 22 sept. 2015 07:40, "Sven Van Caekenberghe" <sven(a)stfx.eu> a Ã©crit : > > > > > > > On 21 Sep 2015, at 23:53, stepharo <stepharo(a)free.fr> wrote: > > > > > > I think that having metadata (style) language and data (source code) mixed together is a bad idea. > > > I never like the ]lang[ tag because it is a huge hack. It does not even exist in the Smalltalk syntax!!! > > > We save code that the parser cannot parse. What we fun idea. > > > So people are bashing for backward compatibility and we remove a bad way to encode > > > metadata then suddenly it looks like we were doing something bad. > > > > > > Stef > > > > I am with Stef, it is a silly idea to mix the two. Nobody uses this in Pharo. Cleaning up means simplifying too. > > In the code no. But in the comments, that would be good to have back. In color form. As we can write pillar class comments, can't we render them ? Moose as an editor/viewer for pillar files > > Yes, it is where we want to go: use Pillar for styled comments. Once we have that, we can remove Text styling from source code / comments.

Sept. 22, 2015

Re: [Pharo-dev] TextAttributes in source code or class comment?

by philippe.back＠highoctane.be

Le 22 sept. 2015 07:40, "Sven Van Caekenberghe" <sven(a)stfx.eu> a Ã©crit : > > > > On 21 Sep 2015, at 23:53, stepharo <stepharo(a)free.fr> wrote: > > > > I think that having metadata (style) language and data (source code) mixed together is a bad idea. > > I never like the ]lang[ tag because it is a huge hack. It does not even exist in the Smalltalk syntax!!! > > We save code that the parser cannot parse. What we fun idea. > > So people are bashing for backward compatibility and we remove a bad way to encode > > metadata then suddenly it looks like we were doing something bad. > > > > Stef > > I am with Stef, it is a silly idea to mix the two. Nobody uses this in Pharo. Cleaning up means simplifying too. In the code no. But in the comments, that would be good to have back. In color form. As we can write pillar class comments, can't we render them ? Moose as an editor/viewer for pillar files. Phil > >

Sept. 22, 2015

Re: [Pharo-dev] TextAttributes in source code or class comment?

by Sven Van Caekenberghe

> On 21 Sep 2015, at 23:53, stepharo <stepharo(a)free.fr> wrote: > > I think that having metadata (style) language and data (source code) mixed together is a bad idea. > I never like the ]lang[ tag because it is a huge hack. It does not even exist in the Smalltalk syntax!!! > We save code that the parser cannot parse. What we fun idea. > So people are bashing for backward compatibility and we remove a bad way to encode > metadata then suddenly it looks like we were doing something bad. > > Stef I am with Stef, it is a silly idea to mix the two. Nobody uses this in Pharo. Cleaning up means simplifying too.

Sept. 22, 2015

Re: [Pharo-dev] [ANN]: AconcaguaAddOns

by HernÃ¡n Morales Durand

Someone can confirm Aconcagua is loadable through Metacello Configurations under Windows? Cheers, HernÃ¡n 2015-09-18 17:22 GMT-03:00 HernÃ¡n Morales Durand <hernan.morales(a)gmail.com>: > Hi Sean, > > First thanks for sharing this. > > Now I suppose this was AconcaguaDeluxe before? > Do you have a ConfigurationOf for AconcaguaAddOns? > > I want to use it but don't have idea what to load. > > HernÃ¡n > > > 2015-04-21 13:21 GMT-03:00 Sean P. DeNigris <sean(a)clipperadams.com>: > >> I pushed some Aconcagua extensions to >> http://smalltalkhub.com/mc/SeanDeNigris/AconcaguaAddOns/main/ >> >> One part consists of tiny (so far) Aconcagua models of various domains - >> Time*, Money, and Weight at the moment. >> >> The other is the Aconcagua-Magritte package. This gives you >> MAMeasureDescription, which represents an Aconcagua Measure. It mostly >> acts >> like a number field mapped to its amount. You just have to tell it which >> unit to use to convert the amount number into a Measure. >> >> Example usage: >> MAMeasureDescription new >> accessor: #replacementPrice; >> label: 'Replacement Price'; >> unit: AmDollar new; >> yourself >> >> Then, you can type 100 in a Magritte form and "100 dollars" will be saved >> to >> the model. Enjoy! >> >> * Yes, I know Chalten has months and years, but (I think when Chalten was >> extended to handle non-Gregorian calendars) months and year units are no >> longer derived from each other, and so can not be compared. >> >> >> >> ----- >> Cheers, >> Sean >> -- >> View this message in context: >> http://forum.world.st/ANN-AconcaguaAddOns-tp4820940.html >> Sent from the Pharo Smalltalk Developers mailing list archive at >> Nabble.com. >> >> >

Sept. 22, 2015

Re: [Pharo-dev] TextAttributes in source code or class comment?

by Craig Latta

(autocorrect-unmangled version... ;) Eliot writes: > ...I was pragmatic and made sure Cog supported the existing > requirements, not some platonic ideal. I wish you would adopt as a > principle that functionality be retained as you are cleaning up > Pharo. Instead I see useful functionality is discarded because of > scruples and I find it "unpleasant". -C -- Craig Latta netjam.org +31 6 2757 7177 (SMS ok) + 1 415 287 3547 (no SMS)

Sept. 22, 2015

Re: [Pharo-dev] TextAttributes in source code or class comment?

by Eliot Miranda

Hi Stef, > On Sep 21, 2015, at 2:53 PM, stepharo <stepharo(a)free.fr> wrote: > > I think that having metadata (style) language and data (source code) mixed together is a bad idea. > I never like the ]lang[ tag because it is a huge hack. It does not even exist in the Smalltalk syntax!!! > We save code that the parser cannot parse. What we fun idea. > So people are bashing for backward compatibility and we remove a bad way to encode > metadata then suddenly it looks like we were doing something bad. It seems to me you are confusing functionality and implementation. Just because you don't like the implementation is no reason to lose the functionality. No implementation is perfect, so this path leads to a denuded system. The onus is on the community to reimplement things well, not throw things away just because the implementation is problematic. If I had chosen to implement Cog with a much nicer substrate then neither Squeak, nor Pharo nor Newspeak would have been able to benefit. Instead I was pragmatic and made sure Cig supported the existing requirements, not done platonic ideal. I wish you would adopt as a principle that functionality be retained as you are cleaning up Pharo. Instead I see useful fictional its discarded because if scruples and I find it "unpleasant". _,,,^..^,,,_ (phone) > > Stef >

Sept. 22, 2015

Re: [Pharo-dev] TextAttributes in source code or class comment?

by stepharo

I think that having metadata (style) language and data (source code) mixed together is a bad idea. I never like the ]lang[ tag because it is a huge hack. It does not even exist in the Smalltalk syntax!!! We save code that the parser cannot parse. What we fun idea. So people are bashing for backward compatibility and we remove a bad way to encode metadata then suddenly it looks like we were doing something bad. Stef

Sept. 21, 2015

Re: [Pharo-dev] WhatsUp from: 2015-09-21 until: 2015-09-30

by phil＠highoctane.be

> On 21-09-15 07:00, seaside(a)rmod.lille.inria.fr wrote: >Hi! We're sending this automatic email twice a month, to give the community an opportunity to easily know what's happening and to coordinate efforts. Just answer informally, and feel free to spawn discussions thereafter! > > ### Here's what I've been up to since the last WhatsUp: - Finished up Seaside app with Datatables and some nice jQuery - Worked on making TilingWindowManager work in Pharo 5.0 - Started Pharo livecoding on https://www.livecoding.tv/philippeback/ for the TWM port - Started some code to access JIRA from Pharo : queries working - Started some code to access Google Sheets from Pharo (using Zn-SSO) : queries working - Reported bugs > ### What's next, until 2015-09-30 (*): > - Finishing the TWM port and integrating it with DesktopManager - More work on the JIRA/GoogleSheets - (later - next livecoding project): getting PyBridge to work in Pharo 5.0 Phil

Sept. 21, 2015

Re: [Pharo-dev] WhatsUp from: 2015-09-21 until: 2015-09-30

by Stephan Eggermont

On 21-09-15 07:00, seaside(a)rmod.lille.inria.fr wrote: > Hi! We're sending this automatic email twice a month, to give the community an opportunity to easily know what's happening and to coordinate efforts. Just answer informally, and feel free to spawn discussions thereafter! > > ### Here's what I've been up to since the last WhatsUp: - Build a prototype of a keyboard-controlled editor and created a video - Updated some Seaside configurations - Found annoying bug in Rubric (that combined well with my own) - Made some updates in PlanBoard: adding/(re)moving columns > ### What's next, until 2015-09-30 (*): > > - $NEXT_STEPS_TOWARDS_WORLD_DOMINATION - Fix keyboard based editor bug, add some functionality

Sept. 21, 2015

Re: [Pharo-dev] WhatsUp from: 2015-09-21 until: 2015-09-30

by Damien Cassou

seaside(a)rmod.lille.inria.fr writes: ### Here's what I've been up to since the last WhatsUp: - release Pharo code to inspect Jenkins server (https://github.com/DamienCassou/pharo-jenkins) ### What's next, until 2015-09-30 (*): - work on the Launcher -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill

Sept. 21, 2015

Incorrect invalidation report

by Ben Coman

Before this report timesout, could someone knowing the CI backend check this validation report... https://ci.inria.fr/pharo/job/Pharo-5.0-Issue-Validator/14283//artifact/val… The validation seems to have failed yet been reported as a success. cheers -ben

Sept. 21, 2015

[pharo-project/pharo-core] dba9f7: 50335

by GitHub

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: dba9f777d4ec753832db8fe81c3f81df5aa5a0be https://github.com/pharo-project/pharo-core/commit/dba9f777d4ec753832db8fe8… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2015-09-21 (Mon, 21 Sep 2015) Changed paths: R Announcements-Core.package/WeakSubscriptionBuilder.class/instance/wrapped protocol/on_do_.st R Announcements-Core.package/WeakSubscriptionBuilder.class/instance/wrapped protocol/on_send_to_.st A Deprecated50.package/extension/PragmaCollector/instance/subscribe_send_to_.st A Deprecated50.package/extension/WeakSubscriptionBuilder/instance/on_do_.st A Deprecated50.package/extension/WeakSubscriptionBuilder/instance/on_send_to_.st M Morphic-Widgets-Tree.package/FilteredMorphTreeModel.class/instance/initialization/initialize.st M Morphic-Widgets-Tree.package/FilteredMorphTreeModel.class/instance/view/defaultMorphIn_.st R PragmaCollector.package/PragmaCollector.class/instance/subscription/subscribe_send_to_.st M PragmaCollector.package/PragmaCollector.class/instance/subscription/whenChangedSend_to_.st M PragmaCollector.package/PragmaCollector.class/instance/subscription/whenResetSend_to_.st A PragmaCollector.package/PragmaCollector.class/instance/subscription/when_send_to_.st M SUnit-UITesting.package/SimulateMouseSpecification.class/instance/helpers/waitForMorphThat_.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50334.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50335.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50334.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50335.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 50335 16519 Deprecate WeakSubscriptionBuilder>>#on:send:to: and #on:do: https://pharo.fogbugz.com/f/cases/16519 16613 add timeout for SimulateMouseSpecification https://pharo.fogbugz.com/f/cases/16613 16565 Remove senders of subscribe:send:to: in PragmaCollector https://pharo.fogbugz.com/f/cases/16565 16563 Remove senders of Announcer>>#subscribe:send:to: in Morphic-Widgets-Tree https://pharo.fogbugz.com/f/cases/16563 http://files.pharo.org/image/50/50335.zip

Sept. 21, 2015

[pharo-project/pharo-core]

by GitHub

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

Sept. 21, 2015

[pharo-project/pharo-core]

by GitHub

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

Sept. 21, 2015

[pharo-project/pharo-core] 436b56: 40622

by GitHub

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: 436b56db239a8618a4533b43d0abc8180c4a2710 https://github.com/pharo-project/pharo-core/commit/436b56db239a8618a4533b43… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2015-09-21 (Mon, 21 Sep 2015) Changed paths: M Compression.package/extension/StandardFileStream/instance/compressFile.st M Files.package/StandardFileStream.class/instance/-- all --/compressFile.st M ScriptLoader40.package/ScriptLoader.class/instance/-- all --/commentForCurrentUpdate.st R ScriptLoader40.package/ScriptLoader.class/instance/-- all --/script621.st A ScriptLoader40.package/ScriptLoader.class/instance/-- all --/script622.st R ScriptLoader40.package/ScriptLoader.class/instance/-- all --/update40621.st A ScriptLoader40.package/ScriptLoader.class/instance/-- all --/update40622.st R ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script621.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script622.st R ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40621.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40622.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 40622 10235 StandardFileStream>>compressFile cant create new compressed file https://pharo.fogbugz.com/f/cases/10235 http://files.pharo.org/image/40/40622.zip

Sept. 21, 2015

Re: [Pharo-dev] WhatsUp from: 2015-09-21 until: 2015-09-30

by stepharo

Le 21/9/15 05:00, seaside(a)rmod.lille.inria.fr a Ã©crit : > Hi! We're sending this automatic email twice a month, to give the community an opportunity to easily know what's happening and to coordinate efforts. Just answer informally, and feel free to spawn discussions thereafter! > > ### Here's what I've been up to since the last WhatsUp: - Working on Pharo starter kit - Working on Mooc - Helping on bootstrap > > ### What's next, until 2015-09-30 (*): > - Publish Pharo Starter Kit - Finish design Slide - For the next iteration after finish to update the Magritte tutorial

Sept. 21, 2015

WhatsUp from: 2015-09-21 until: 2015-09-30

by seaside＠rmod.lille.inria.fr

Hi! We're sending this automatic email twice a month, to give the community an opportunity to easily know what's happening and to coordinate efforts. Just answer informally, and feel free to spawn discussions thereafter! ### Here's what I've been up to since the last WhatsUp: - $HEROIC_ACHIEVEMENTS_OR_DISMAL_FAILURES_OR_SIMPLE_BORING_NECESSARY_TASKS ### What's next, until 2015-09-30 (*): - $NEXT_STEPS_TOWARDS_WORLD_DOMINATION (*) we'll be expecting results by then ;)

Sept. 21, 2015

Re: [Pharo-dev] Contribution scheme confusing ...

by Torsten Bergmann

https://pharo.fogbugz.com/f/cases/16611 > Gesendet: Sonntag, 20. September 2015 um 16:30 Uhr > Von: "Marcus Denker" <marcus.denker(a)inria.fr> > An: "Pharo Development List" <pharo-dev(a)lists.pharo.org> > Betreff: Re: [Pharo-dev] Contribution scheme confusing ... > > Yes, this is good to put it in the imageâ¦ I will update the website later, too. > > can you make an issue? > > > On 17 Sep 2015, at 17:35, Torsten Bergmann <astares(a)gmx.de> wrote: > > > > Hi Marcus, > > > > Could work - but is a fragile rule. We should document it somewhere. > > > > What about providing this info directly in the image. Alexandre has already added a help topic on how > > to contribute (but yet only for the slice process). > > > > I changed it so we can have the differences of config managed ones described as well and > > we can list the configs there. See the attached changeset that you can file in into the latest > > Pharo5.0 Latest update: #50329 > > > > File in and check "How to contribute to Pharo base code" topic in Help -> Help Browser > > > > I guess this would be more clear to us and the users and we can simply point to > > the help info is someone asks. And look up ourself when we forgot. > > > > Thx > > T. > > > >> Gesendet: Donnerstag, 17. September 2015 um 15:40 Uhr > >> Von: "Marcus Denker" <marcus.denker(a)inria.fr> > >> An: "Pharo Development List" <pharo-dev(a)lists.pharo.org> > >> Betreff: Re: [Pharo-dev] Contribution scheme confusing ... > >> > >>>> > >>>> Also: > >>>> I did a simple fix on NautilusGroupAutoBuilder package - there is > >>>> a ConfigurationOfNautilusGroupAutoBuilder. But is it managed internally > >>>> or externally now? > >>>> > >>> Even I can not tell you. > >>> > >> > >> I think the rule we should adopt: if there is a dedicated repository defined in the image for a package, people should commit > >> there. If there is non (just the inbox), then this should be used (with the Slice mechanism). > >> > >> The repositories in the image should be already up to date, I think. > >> > >> Marcus > >> > >> > > <HowToContributeHelp class.TorstenBergmann.cs> > > >

Sept. 20, 2015

Re: [Pharo-dev] Need a decision on subString: vs substring:

by Esteban Lorenzano

> On 20 Sep 2015, at 19:14, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > > > What is the decision? > The consensus seemed to be #substrings:, and a compatibility package if necessary. â¦ because substring is real english while subString is not, AFAIK :) > Cheers, > Sean > > View this message in context: Re: Need a decision on subString: vs substring: <http://forum.world.st/Need-a-decision-on-subString-vs-substring-tp4847932p4…> > Sent from the Pharo Smalltalk Developers mailing list archive <http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html> at Nabble.com.

Sept. 20, 2015

ConfigurationOfRoassal2 broken

by Stephan Eggermont

Can anyone explain ConfigurationOfRoassal2? Where does that work? stable: spec <symbolicVersion: #'stable'> spec for: #'common' version: '1.11'. spec for: #'pharo4.x' version: '1.13'. spec for: #'pharo3.x' version: '1.6'. development: spec <symbolicVersion: #'development'> spec for: #'common' version: '1.4-baseline'. spec for: #'pharo4.x' version: '1.5-baseline'.

Sept. 20, 2015

Re: [Pharo-dev] Need a decision on subString: vs substring:

by Sean P. DeNigris

> What is the decision? The consensus seemed to be #substrings:, and a compatibility package if necessary. ----- Cheers, Sean -- View this message in context: http://forum.world.st/Need-a-decision-on-subString-vs-substring-tp4847932p4… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Sept. 20, 2015

[pharo-project/pharo-core]

by GitHub

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

Sept. 20, 2015