January 2014 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Static File Server for Pharo Contribution

by Christophe Demarey

Le 19 janv. 2014 Ã 10:19, Marcus Denker a Ã©crit : > > On 18 Jan 2014, at 18:24, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > >> Marcus Denker-4 wrote >>> What do you want to store? An image? Documentation? >> >> Well I was recommending Phratch to a non-programmer (teacher) using Scratch. >> We went to the download page and found Metacello instructions, which baffled >> them. There is a CI build but IIRC we weren't linking to those artifacts as >> not to overload the CI server, so I was thinking it would be good to mirror >> them on a static server like we do with core. Then we could link to them on >> the project websitesâ¦ >> > In the long run, I think that images will become very much what Squeak Projects > used to be (but without the problemsâ¦). > > So yes, I think this would be nice. > > We where discussing on and off what to use for storage.. the inria server is free, > but a bit of a hassle (due to security restrictions). And of course, at some size > they will start to be less happy. > > I was thinking of Amazon S3â¦ we should look into it. What about using github to provide a website and store files (using github pages branch)? Free and easy to set up. Moreover, you can add documentation and edit it easily. Christophe.

Jan. 20, 2014

Re: [Pharo-dev] [Moose-dev] [ANN] MessageTally in GTInspector

by StÃ©phane Ducasse

On 19 Jan 2014, at 22:58, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > This is gorgeous. > The Moose distribution of Pharo looks like to be better suitable for code development than the vanilla one. This makes me remember the Development image of Damien. Do you really ***understand*** the implications? Because once people will start to put dependencies everytwhere on roassal and start to run smalllint on your code and â¦. that you will have to follow it and merge and â¦. you will look at the problem. Without unload process that is systematically exercised, tools to manage dependencies and a process to build and support modular images we will end up with a monolithic system. I just tried to unload ProfStef and it was full of left instance behind. I tried to unload Nautilus for example and RB. Stef > > Alexandre > > > On Jan 18, 2014, at 8:29 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > >> Hi, >> >> The GTInspector just became a performance analysis tool, too. You can simply inspect a MessageTally and you get several useful views that help you identify performance problems. >> >> You can read a more detailed description here: >> http://www.humane-assessment.com/blog/assessing-pharo-performance-with-gtin… >> >> As an appetizer, I attached a screenshot with a Graph-ET chart (thank you Daniel Aviv for developing this engine). >> >> <MessageTally-chart.png> >> >> To play with the code, you can just work in the latest Moose 5.0 image: >> https://ci.inria.fr/moose/job/moose-5.0/lastSuccessfulBuild/artifact/moose-… >> >> Please let me know what you think. >> >> Cheers, >> Doru >> >> -- >> www.tudorgirba.com >> >> "Every thing has its own flow" >> _______________________________________________ >> Moose-dev mailing list >> Moose-dev(a)iam.unibe.ch >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > >

Jan. 20, 2014

[pharo-project/pharo-core]

by GitHub

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

Jan. 20, 2014

[pharo-project/pharo-core] 6547d9: 30709

by GitHub

Branch: refs/heads/3.0 Home: https://github.com/pharo-project/pharo-core Commit: 6547d9481e9cfa17ab5c59899d3e8ca7aea7ae5f https://github.com/pharo-project/pharo-core/commit/6547d9481e9cfa17ab5c5989… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-01-19 (Sun, 19 Jan 2014) Changed paths: R Collections-Abstract.package/SequenceableCollection.class/instance/private/copyReplaceAll_with_asTokens_.st M Files.package/PharoFilesOpener.class/instance/open sources/openSources_forImage_.st M RPackage-Core.package/RPackage.class/instance/testing/includesClassNamed_.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - scripts/script362.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - updates/update30709.st M ScriptLoader30.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st A Spec-Tools.package/DiffMorphChangeRecordConverter.class/README.md A Spec-Tools.package/DiffMorphChangeRecordConverter.class/definition.st A Spec-Tools.package/DiffMorphChangeRecordConverter.class/instance/private/internalGetText.st A Spec-Tools.package/DiffMorphChangeRecordConverter.class/instance/private/priorVersionOfAMethod_.st A Spec-Tools.package/NewVersionBrowser.class/class/menu/versionsBrowserListMenu_.st M Spec-Tools.package/NewVersionBrowser.class/class/protocol/browseVersionsForClass_selector_.st A Spec-Tools.package/NewVersionBrowser.class/class/protocol/browseVersionsOf_.st A Spec-Tools.package/NewVersionBrowser.class/instance/accessing/browser.st M Spec-Tools.package/NewVersionBrowser.class/instance/copy and paste/scanVersionsOf_class_meta_category_selector_.st M Spec-Tools.package/NewVersionBrowser.class/instance/instance creation/browserForList_.st M Spec-Tools.package/NewVersionBrowser.class/instance/instance creation/buildBrowser.st M Spec-Tools.package/NewVersionBrowser.class/instance/instance creation/revert_.st A Spec-Tools.package/NewVersionBrowser.class/instance/instance creation/showDiffMorphWithConverter_.st A Spec-Tools.package/NewVersionBrowser.class/instance/instance creation/showSourceWithConverter_.st A Spec-Tools.package/NewVersionBrowser.class/instance/menu/browseImplementors.st A Spec-Tools.package/NewVersionBrowser.class/instance/menu/browseSenders.st A Spec-Tools.package/NewVersionBrowser.class/instance/menu/compareToCurrentVersion.st A Spec-Tools.package/NewVersionBrowser.class/instance/menu/compareToOtherVersion.st A Spec-Tools.package/NewVersionBrowser.class/instance/menu/compareTo_.st A Spec-Tools.package/extension/DiffModel/instance/aboutToStyle_.st A Spec-Tools.package/extension/DiffModel/instance/behavior.st A Spec-Tools.package/extension/DiffModel/instance/behavior_.st A Spec-Tools.package/extension/DiffModel/instance/doItReceiver_.st A Spec-Tools.package/extension/DiffModel/instance/getText.st A Spec-Tools.package/extension/DiffModel/instance/text_.st Log Message: ----------- 30709 11714 NewVersionBrowser needs to be finished https://pharo.fogbugz.com/f/cases/11714 12532 Unable to find sources file: blank image screen when starting Pharo30 and vm crash report https://pharo.fogbugz.com/f/cases/12532 12680 RPackage>>includesClassNamed: does not ensure that name is a Symbol https://pharo.fogbugz.com/f/cases/12680 12681 remove #copyReplaceAll:with:asTokens: from SquenceableCollection https://pharo.fogbugz.com/f/cases/12681 http://files.pharo.org/image/30/30709.zip

Jan. 20, 2014

WhatsUp from: 2014-01-20 until: 2014-01-31

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 2014-01-31 (*): - $NEXT_STEPS_TOWARDS_WORLD_DOMINATION (*) we'll be expecting results by then ;)

Jan. 20, 2014

Re: [Pharo-dev] [Moose-dev] [ANN] MessageTally in GTInspector

by Marcus Denker

On 19 Jan 2014, at 22:58, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > This is gorgeous. > The Moose distribution of Pharo looks like to be better suitable for code development than the vanilla one. This makes me remember the Development image of Damien. > Keep in mind that we need to take care: the problem back than was that we had actually not a good situation: we developed one image, but then people used other tools when they downloaded the final version. This means that details never got fixed and improved: why put a lot of effort into getting the details in the browser correct if everyone will use another browser? And that other browser did not see a lot of work, either, because it was not part of the development effort of Pharo itself. It was actually quite bad. We need to really take care to not have that again. And we do *not* have the manpower to manage two sets of tools anyway. Marcus

Jan. 19, 2014

Re: [Pharo-dev] [Moose-dev] [ANN] MessageTally in GTInspector

by Alexandre Bergel

This is gorgeous. The Moose distribution of Pharo looks like to be better suitable for code development than the vanilla one. This makes me remember the Development image of Damien. Alexandre On Jan 18, 2014, at 8:29 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Hi, > > The GTInspector just became a performance analysis tool, too. You can simply inspect a MessageTally and you get several useful views that help you identify performance problems. > > You can read a more detailed description here: > http://www.humane-assessment.com/blog/assessing-pharo-performance-with-gtin… > > As an appetizer, I attached a screenshot with a Graph-ET chart (thank you Daniel Aviv for developing this engine). > > <MessageTally-chart.png> > > To play with the code, you can just work in the latest Moose 5.0 image: > https://ci.inria.fr/moose/job/moose-5.0/lastSuccessfulBuild/artifact/moose-… > > Please let me know what you think. > > Cheers, > Doru > > -- > www.tudorgirba.com > > "Every thing has its own flow" > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)iam.unibe.ch > https://www.iam.unibe.ch/mailman/listinfo/moose-dev -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Jan. 19, 2014

[pharo-project/pharo-core] ffd649: 30708

by GitHub

Branch: refs/heads/3.0 Home: https://github.com/pharo-project/pharo-core Commit: ffd649b35faa7bb86e414e7e44dfec807ad0e078 https://github.com/pharo-project/pharo-core/commit/ffd649b35faa7bb86e414e7e… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-01-19 (Sun, 19 Jan 2014) Changed paths: A ScriptLoader30.package/ScriptLoader.class/instance/pharo - scripts/script361.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - updates/update30708.st M ScriptLoader30.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Spec-Tools.package/MessageBrowser.class/instance/announcements/methodAdded_.st M Spec-Tools.package/MessageBrowser.class/instance/announcements/methodModified_.st M Spec-Tools.package/MessageBrowser.class/instance/announcements/methodRemoved_.st Log Message: ----------- 30708 12547 In the messageBrowser the [package] -> [nil] https://pharo.fogbugz.com/f/cases/12547 http://files.pharo.org/image/30/30708.zip

Jan. 19, 2014

[pharo-project/pharo-core]

by GitHub

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

Jan. 19, 2014

Re: [Pharo-dev] unload all

by Alexandre Bergel

Impressive job! Alexandre > Le 18-01-2014 Ã 16:37, Pavel Krivanek <pavel.krivanek(a)gmail.com> a Ã©crit : > > Hi, > > I finally successfully created a script that is able to unload everything *by Monticello* except kernel packages, network, Monticello, Gofer and related packages. I will setup a job when Jenkins will be healthy again. > It uses several temporary patches that we need to solve properly: > - make NativeBoost optional > - make UserManager optional > - small super-easy issue https://pharo.fogbugz.com/f/cases/12679/change-package-of-ClassTrait-soleIn… > > The size of resultant image is about 6.6 MB, 4.9 MB without MC data and caches. BTW in the full image Monticello data have about 5MB. The image has no Undeclared nor obsolete classes and is really able to load something using Gofer. > > With some care we can make it usable base for the next remodularization effort. > > Cheers, > -- Pavel >

Jan. 19, 2014