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

Re: [Pharo-dev] [Experiment] Automatic rewriting of sends to deprecated methods

by stepharo

We could ship a specific package with rules for each version of Pharo. We did it with andre's work and we should continue. Le 1/9/15 10:23, Stephan Eggermont a Ã©crit : > On 01-09-15 08:35, Marcus Denker wrote: >> But just think how much this simplifies the experience of people >> loading old code into a new >> Pharo version: it just keeps running and fixes itself! Itâs that kind >> of things we need to be >> able to evolve the system. > > This is a crucial step to support continuous improvement indeed. > Just-in-time repeatable refactoring, reducing the cost of change > > Stephan > > >

Sept. 1, 2015

Re: [Pharo-dev] [Experiment] Automatic rewriting of sends to deprecated methods

by stepharo

>> >> It can be made pluggable, of course. I donât want to have that there in a way that it requires >> the refactoring engine to be present all the time. >> >> If itâs there â> transform. If not â> do what it does now. >> >> But just think how much this simplifies the experience of people loading old code into a new >> Pharo version: it just keeps running and fixes itself! Itâs that kind of things we need to be >> able to evolve the system. >> >> Imagine, this is a functionality (I think) no other system has! Yes but we should make it pluggable. I would like something that says before all the tests were green and after these automatic changes they are also green :) > I will not like a feature where it transforms my code without asking. > I would prefer that a diff browser pops up and asks me if changes are ok. Automatic rewrite of code often forgot to check some specific cases and you end with bugs in your code if there is no review. > The idea is great but the choice of changing the code or not has to be in the user hands.

Sept. 1, 2015

Re: [Pharo-dev] Pharo CI Validation Timeout

by stepharo

Ben can you open a bug entry because we should really try your change now. And probably remove after the Experimental from the name. Stef Le 1/9/15 19:15, Ben Coman a Ã©crit : > Do you want to try a post-load... > Delay delaySchedulerClass: DelayExperimentalSemaphoreScheduler > > which fixes the "super fast delay" on virtual machines reported here... > http://comments.gmane.org/gmane.comp.lang.smalltalk.pharo.devel/100873 > > Its named "experimental" only since it was integrated just before > Pharo 4 release and did not have wide spread community testing, but > its complete and working. There is some further overall streamlining > of the DelayScheduler hierarchy I'd like to do later, but it would be > good to give this one a run as the default for a while to see how it > impacts the issue. (It would be good to get rough "CIAndRule: Timeout" > before and after statistics.) > > btw, is that CI error indicating it times out after one hour? Are > there any other timestamps present in the log that indicate if 1 hour > really passed? > > cheers -ben > > On Tue, Sep 1, 2015 at 11:23 PM, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: >> This is different issue, same problem >> https://ci.inria.fr/pharo/job/Pharo-5.0-Issue-Validator/12442//artifact/val… >> >> I'm blaming CI. >> >> On Tue, Sep 1, 2015 at 5:22 PM, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: >>> Hi, >>> >>> CI is failing on >>> >>> a CIAndRule: Timeout (after 0:01:00:00) occured >>> >>> >>> https://ci.inria.fr/pharo/job/Pharo-5.0-Issue-Validator/12440//artifact/val… >>> >>> Because the validation before it was ok and I just changed a protocol. >>> Is this my problem? Is this issue in CI? >>> >>> Thanks, >>> Peter >> >

Sept. 1, 2015

Removing name from Object

by stepharo

Hi guys I would love to see name removed from Object. It brings more problems than anything else. Any taker? Stef

Sept. 1, 2015

Re: [Pharo-dev] Pharo CI Validation Timeout

by Ben Coman

Do you want to try a post-load... Delay delaySchedulerClass: DelayExperimentalSemaphoreScheduler which fixes the "super fast delay" on virtual machines reported here... http://comments.gmane.org/gmane.comp.lang.smalltalk.pharo.devel/100873 Its named "experimental" only since it was integrated just before Pharo 4 release and did not have wide spread community testing, but its complete and working. There is some further overall streamlining of the DelayScheduler hierarchy I'd like to do later, but it would be good to give this one a run as the default for a while to see how it impacts the issue. (It would be good to get rough "CIAndRule: Timeout" before and after statistics.) btw, is that CI error indicating it times out after one hour? Are there any other timestamps present in the log that indicate if 1 hour really passed? cheers -ben On Tue, Sep 1, 2015 at 11:23 PM, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > This is different issue, same problem > https://ci.inria.fr/pharo/job/Pharo-5.0-Issue-Validator/12442//artifact/val… > > I'm blaming CI. > > On Tue, Sep 1, 2015 at 5:22 PM, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: >> >> Hi, >> >> CI is failing on >> >> a CIAndRule: Timeout (after 0:01:00:00) occured >> >> >> https://ci.inria.fr/pharo/job/Pharo-5.0-Issue-Validator/12440//artifact/val… >> >> Because the validation before it was ok and I just changed a protocol. >> Is this my problem? Is this issue in CI? >> >> Thanks, >> Peter > >

Sept. 1, 2015

[pharo-project/pharo-core]

by GitHub

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

Sept. 1, 2015

[pharo-project/pharo-core] cd1fb7: 50297

by GitHub

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: cd1fb747933fa128ad8283286ef8ecd0b4b82f18 https://github.com/pharo-project/pharo-core/commit/cd1fb747933fa128ad828328… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2015-09-01 (Tue, 01 Sep 2015) Changed paths: M ConfigurationOfGTInspectorCore.package/ConfigurationOfGTInspectorCore.class/instance/symbolic versions/stable_.st A ConfigurationOfGTInspectorCore.package/ConfigurationOfGTInspectorCore.class/instance/versions/version2019_.st M ConfigurationOfGTPlaygroundCore.package/ConfigurationOfGTPlaygroundCore.class/instance/symbolic versions/stable_.st A ConfigurationOfGTPlaygroundCore.package/ConfigurationOfGTPlaygroundCore.class/instance/versions/version219_.st M ConfigurationOfGTSpotter.package/ConfigurationOfGTSpotter.class/instance/symbolic versions/stable_.st A ConfigurationOfGTSpotter.package/ConfigurationOfGTSpotter.class/instance/versions/version1210_.st M ConfigurationOfGToolkitCore.package/ConfigurationOfGToolkitCore.class/instance/symbolic versions/stable_.st A ConfigurationOfGToolkitCore.package/ConfigurationOfGToolkitCore.class/instance/versions/version306_.st M ConfigurationOfGlamourCore.package/ConfigurationOfGlamourCore.class/instance/symbolic versions/stable_.st A ConfigurationOfGlamourCore.package/ConfigurationOfGlamourCore.class/instance/versions/version3110_.st A ConfigurationOfGlamourCore.package/ConfigurationOfGlamourCore.class/instance/versions/version320_.st M GT-Inspector.package/extension/Object/instance/gtInspectorPresentationsIn_inContext_.st M GT-Spotter-EventRecorder.package/GTSpotterEventRecorder.class/instance/events/recordAccouncement_.st A GT-Spotter-EventRecorder.package/extension/GTSpotterActOn/instance/asRecorderEvent.st A GT-Spotter-EventRecorder.package/extension/GTSpotterCategorySelected/instance/asRecorderEvent.st A GT-Spotter-EventRecorder.package/extension/GTSpotterContextChanged/instance/asRecorderEvent.st A GT-Spotter-EventRecorder.package/extension/GTSpotterDiveInCategory/instance/asRecorderEvent.st A GT-Spotter-EventRecorder.package/extension/GTSpotterDiveInElement/instance/asRecorderEvent.st A GT-Spotter-EventRecorder.package/extension/GTSpotterDiveOut/instance/asRecorderEvent.st A GT-Spotter-EventRecorder.package/extension/GTSpotterExitAnnouncement/instance/asRecorderEvent.st A GT-Spotter-EventRecorder.package/extension/GTSpotterHidePreview/instance/asRecorderEvent.st A GT-Spotter-EventRecorder.package/extension/GTSpotterSearchFinished/instance/asRecorderEvent.st A GT-Spotter-EventRecorder.package/extension/GTSpotterSelectedCandidateChanged/instance/asRecorderEvent.st A GT-Spotter-EventRecorder.package/extension/GTSpotterShowPreview/instance/asRecorderEvent.st M GT-SpotterExtensions-Core.package/extension/AbstractCompiler/instance/silentlyDo_exceptionDo_.st M GT-SpotterExtensions-Core.package/extension/MCWorkingCopy/instance/versionInfo.st M GT-Tests-Inspector.package/GTInspectorExamplesTest.class/instance/tests/checkAllPresentationsOf_.st A Glamour-Core.package/GLMPresentation.class/instance/testing/hasTransformation.st M Glamour-Morphic-Renderer.package/GLMMorphicListingRenderer.class/instance/private/textInputFor_withHelpMessage_.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50296.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50297.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50296.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50297.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 50297 ConfigurationOfRubric http://files.pharo.org/image/50/50297.zip

Sept. 1, 2015

Re: [Pharo-dev] [ANN] Pillar 1.0.0.

by Sven Van Caekenberghe

Thank you for your contributions, Cyril, we can only hope that you stick around. > On 01 Sep 2015, at 15:45, Ferlicot D. Cyril <cyril.ferlicot(a)gmail.com> wrote: > > Hello guys! > > I finished 5 months of internship into the RMoD team. I worked on Pillar > and I am glad to announce the version 1.0.0! > You can find an updated documentation of this version here : > https://ci.inria.fr/pharo-contribution/view/Books/job/EnterprisePharoBook/l…. > > We decided with Damien Cassou to use Semetic Versioning from now (see: > http://semver.org/) > > I will now explain the main changes I did on Pillar during my internship. > > For each new feature I added tests and documentation. > > I will begin with the changes of Pillar's structure > > - The configuration system is now manage by Cocoon > (http://www.smalltalkhub.com/#!/~PharoExtras/Cocoon) > -- We now use Magritte in Cocoon > > - I added Annotations : A syntax extension point > > - I added Transformers : A way to transform a document model before an > export (to add a section structure in HTML for example) > > - Some small refactoring. > -- Improvement of the template management > -- Improvement of the Pillar model parameters > > - Improvement of the document model > -- Now the figures and links are two different entity > > - I begun a PetitPillar (with PetitParser) in order to replace the old > parser too complicated. > > Now I will talk about new features for the users > > - Improvement of the usability of Pillar under Windows > > - Beamer and Deck.js exporters > > - Annotations : > -- To include a Pillar file into an other (${inputFile:path}$) (Example: > https://github.com/SquareBracketAssociates/EnterprisePharo/blob/master/Ente…) > -- To create new slides in Beamer and Deck.js (${slide:My > Title|label=optional}$) > -- To create columns into a Pillar document (currently works in Beamer, > Deck.js and HTML) > -- â¦ > > - Transformers > -- You can now add a parameter "lineNumber=true" to a script and Pillar > will transform them to add the line numbers > -- You can now import a script from an other file (see the documentation > of the scripts) > -- â¦ > > - Improvement of the errors raised by Pillar > > - Addition of the inter-files links > > - Improvement of the title configuration for numbering > > - No need to make scripts anymore to use Pillar ! > -- You can used "defaultExporters" in your configuration to do multiple > export (see documentation) > -- Pillar generate a script for LaTeX compilation (only for Unix for now) > > - Possibility to export everything into a different folder (simpler to > clean after) > -- And possibility to copy some support files > > For the two previous point you can take example on Enterprise Pharo > (https://github.com/SquareBracketAssociates/EnterprisePharo) and Pharo > Mooc (https://github.com/SquareBracketAssociates/PharoMooc) > > This was a really cool internship :) > > If you have some questions do not hesitate! > > -- > Cyril >

Sept. 1, 2015

Re: [Pharo-dev] [ANN] Pillar 1.0.0.

by Damien Cassou

Ferlicot D. Cyril <cyril.ferlicot(a)gmail.com> writes: > I finished 5 months of internship into the RMoD team. I worked on Pillar > and I am glad to announce the version 1.0.0! > You can find an updated documentation of this version here : > https://ci.inria.fr/pharo-contribution/view/Books/job/EnterprisePharoBook/l…. Cyril has been a great student. His contributions to Pillar are all important. Now that Pillar 1.0.0 is released, we should try to move to PetitPillar (done at 90%). There might be some compatibility problems with existing documents but the great test suite (2100 tests covering 94% of the code) should limit them. The TODO list is now much larger but I guess that's a good sign: http://www.smalltalkhub.com/#!/~Pier/Pillar. Please contribute! -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill

Sept. 1, 2015

Re: [Pharo-dev] Pharo CI Validation Timeout

by Marcus Denker

Yes, for now just restart.. I will try to find time to look into this. > On 01 Sep 2015, at 17:31, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > > So do I wait, or do I keeping pushing the monkey until it succeeds? > > On Tue, Sep 1, 2015 at 5:23 PM, Marcus Denker <marcus.denker(a)inria.fr <mailto:marcus.denker@inria.fr>> wrote: > >> On 01 Sep 2015, at 17:22, Peter UhnÃ¡k <i.uhnak(a)gmail.com <mailto:i.uhnak@gmail.com>> wrote: >> >> Hi, >> >> CI is failing on >> a CIAndRule: Timeout (after 0:01:00:00) occured >> https://ci.inria.fr/pharo/job/Pharo-5.0-Issue-Validator/12440//artifact/val… <https://ci.inria.fr/pharo/job/Pharo-5.0-Issue-Validator/12440//artifact/val…> >> >> Because the validation before it was ok and I just changed a protocol. >> Is this my problem? Is this issue in CI? >> > > This is an issue with, I think, the virtual server belowâ¦ it is strange: some times the run takes > very very very long. I have not yet found out why (there is an issue tracker entry for it). > > Marcus > >

Sept. 1, 2015