July 2013 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] [Pharo-users] [ANN] Pharo Launcher

by Damien Cassou

On Mon, Jul 8, 2013 at 11:00 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > I noticed two issues when playing with it: > - there is no feedback while downloading the image. This can be confusing. > Normally, the status bar should display "Downloading...", but I'm not sure it works all the time and it is a bit hidden :-). - the launcher quits when launching another image (I am on Mac). This is > actually interesting, but it was surprising. I am not sure what is the > right solution here. > I think a right solution would be to ask the first time you open image an image: "Do you want to quit?", with a checkbox to save the setting. > And a question: How can we get more images available through this > interface? if you are talking about adding more servers (called template groups) to get more templates in the right pane: you currently must add a line in PhLTemplateGroupRepository class>>all. Eventually, I would like that users can specify their list of template groups (e.g., pharo-contribution, moose-ci, yourcompany-jenkins...) in a preference file. if you are talking about finding images that are already on the hard disk but didn't get created by the launcher: it is not possible without changing quite some code in PhLDirectoryBasedImageGroup. -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill

July 9, 2013

Jenkins build became unstable: Pharo-2.0-Tests Â» run 1,vm,win #258

by no-reply＠ci.inria.fr

See <https://ci.inria.fr/pharo/job/Pharo-2.0-Tests/Run=run%201,VM=vm,label=win/2…>

July 9, 2013

[regression reporter]regression occurred

by no-reply＠ci.inria.fr

https://ci.inria.fr/pharo/job/Pharo-2.0-Tests/Run=run%201,VM=vm,label=win/2… 1 regressions found. Zinc.Zodiac.ZnHTTPSTests.testTransfers

July 9, 2013

Jenkins build is back to stable : Pharo-2.0-Tests Â» run 1,vm,linux #258

by no-reply＠ci.inria.fr

See <https://ci.inria.fr/pharo/job/Pharo-2.0-Tests/Run=run%201,VM=vm,label=linux…>

July 9, 2013

[update 3.0] #30259

by Marcus Denker

30259 ----- 10848 Problems with parenthesis in TraitComposition https://pharo.fogbugz.com/f/cases/10848 10859 Monticello freezing the image https://pharo.fogbugz.com/f/cases/10859 Diff information: http://smalltalkhub.com/mc/Pharo/Pharo30/main/Traits-MarcusDenker.539.diff http://smalltalkhub.com/mc/Pharo/Pharo30/main/Tests-MarcusDenker.580.diff http://smalltalkhub.com/mc/Pharo/Pharo30/main/Ring-Core-Kernel-MarcusDenker… http://smalltalkhub.com/mc/Pharo/Pharo30/main/Monticello-MarcusDenker.828.d…

July 9, 2013

[update 2.0] #20611

by Marcus Denker

20611 ----- 10978 Backport 20: ZipArchive utf8 handling https://pharo.fogbugz.com/f/cases/10978 11125 backport 2.0: 10859 Monticello freezing the image https://pharo.fogbugz.com/f/cases/11125 Diff information: http://ss3.gemstone.com/ss/Pharo20/Multilingual-TextConversion-MarcusDenker… http://ss3.gemstone.com/ss/Pharo20/Monticello-MarcusDenker.781.diff http://ss3.gemstone.com/ss/Pharo20/Compression-MarcusDenker.124.diff

July 9, 2013

Re: [Pharo-dev] [Pharo-users] [ANN] Pharo Launcher

by Sebastian Tleye

Great, for me, that i am touching kernel classes, it will be very useful have something to manage images quickly!! 2013/7/8 Tudor Girba <tudor(a)tudorgirba.com> > Hi Damien, > > Nice :). > > I noticed two issues when playing with it: > - there is no feedback while downloading the image. This can be confusing. > - the launcher quits when launching another image (I am on Mac). This is > actually interesting, but it was surprising. I am not sure what is the > right solution here. > > And a question: How can we get more images available through this > interface? > > Cheers, > Doru > > > On Jul 8, 2013, at 10:11 AM, Damien Cassou <damien.cassou(a)gmail.com> > wrote: > > > Dear list, > > > > Erwan and I are proud to announce the first release of the Pharo > > Launcher, a cross-platform application that > > > > - lets you manage your Pharo images (launch, rename, copy and delete); > > - lets you download image templates (i.e., zip archives) from many > > different sources (Jenkins, files.pharo.org, and your local cache); > > - lets you create new images from any template. > > > > A screenshot is attached to this email. > > > > The idea behind the Pharo Launcher is that you should be able to > > access it very rapidly from your OS application launcher. As a result, > > launching any image is never more than 3 clicks away. > > > > Download: > https://ci.inria.fr/pharo-contribution/job/PharoLauncher/PHARO=30,VERSION=b… > > > > Please report bugs on the 'Launcher' project at > https://pharo.fogbugz.org > > > > You can contribute to this project. All classes and most methods are > > commented. There are unit tests. Please contribute! > > > > Source code: http://www.smalltalkhub.com/#!/~Pharo/PharoLauncher > > CI: https://ci.inria.fr/pharo-contribution/job/PharoLauncher > > > > Things you can do to improve the system: > > > > - check if a template is already downloaded before downloading it > > - add a preference mechanism (for, e.g., quit after launch, definition > > of your own template groups, location of downloaded templates and > > images) > > - put the launcher in the Pharo Ubuntu package so that the launcher > > becomes a registered appliation of the system > > (https://launchpad.net/~pharo/+archive/stable) > > - make sure the pharo launcher does not load your personal scripts > > (like fonts and MC configuration) > > - add a toolbar to enhance the discoverability of the features > > (currently everything is in contextual menus) > > - make sure rename and copy actions propose default values > > - make sure no debugger pops up when a user press cancels or enter an > > invalid name > > - propose multiple kinds of sorting (last used, most frequently used, > > alphabetically on the name) > > - give some information about each template (build date, pharo version) > > > > -- > > Damien Cassou > > http://damiencassou.seasidehosting.st > > > > "Success is the ability to go from one failure to another without > > losing enthusiasm." > > Winston Churchill > > <screenshot.png> > > -- > www.tudorgirba.com > > "To utilize feedback, you first have to acquire it." > > >

July 9, 2013

Re: [Pharo-dev] thisContext usecases

by Stefan Marr

Hi ClÃ©ment: On 09 Jul 2013, at 11:19, ClÃ©ment Bera <bera.clement(a)gmail.com> wrote: > Sounds cool, nice idea. What VM did you extend ? Vanilla, Stack ? If i remember correctly you implemented Roar VM so maybe you extended this one ? It is an extension to the RoarVM, but for all intents and purposes I use it like a classic interpreter. Thus, no context-to-stack mapping is used. Probably not very useful without all the context, but the relevant code looks often like this: https://github.com/smarr/OmniVM/blob/master/vm/src/interpreter/squeak_inter… Best regards Stefan -- Stefan Marr Software Languages Lab Vrije Universiteit Brussel Pleinlaan 2 / B-1050 Brussels / Belgium http://soft.vub.ac.be/~smarr Phone: +32 2 629 2974 Fax: +32 2 629 3525

July 9, 2013

Re: [Pharo-dev] thisContext usecases

by ClÃ©ment Bera

2013/7/9 Stefan Marr <smalltalk(a)stefan-marr.de> > Hi ClÃ©ment: > > On 09 Jul 2013, at 10:15, ClÃ©ment Bera <bera.clement(a)gmail.com> wrote: > > > Now I'd like to know what context's state do we modify, and what states > are just internal representations ? > > I extended my VM with additional information that is kept in the context. > My contexts can be 'owned' by a certain metaobject, and they indicate with > a boolean whether the execution should regard that metaobject or not, for > instance to delegate certain operations to it. > Sounds cool, nice idea. What VM did you extend ? Vanilla, Stack ? If i remember correctly you implemented Roar VM so maybe you extended this one ? > > So, that's all not exactly 'Pharo' but, I wanted to point out that there > are use cases where additional fields and mutability of those is desirable. > Yeah this feature is nice. And an efficient implementation should be doable. Thanks for your answer. > > Best regards > Stefan > > -- > Stefan Marr > Software Languages Lab > Vrije Universiteit Brussel > Pleinlaan 2 / B-1050 Brussels / Belgium > http://soft.vub.ac.be/~smarr > Phone: +32 2 629 2974 > Fax: +32 2 629 3525 > > >

July 9, 2013

Re: [Pharo-dev] thisContext usecases

by ClÃ©ment Bera

2013/7/9 Igor Stasenko <siguctua(a)gmail.com> > > To my thinking playing with pc is awfully evil, it should be > read-only, only to allow debugger > to map it to source code. Same goes for stack pointer. > For stack pointer I don't know use cases so I have to agree. Now for pc in a smalltalk debugger you can select a place in code and execute 'run to here without executing code'. It is hidden in Pharo (right menu on stack) but it is a button in Visual works. So even if evil, it is required for some functionalities. I don't know if it could be deleted like that. > > Setting receiver is less evil and it may work, if receiver belongs to > same inheritance chain > as compiled method's class. But it should not be set without checking this. > Setting receiver fails in Cog and no one complains so .. > > And for method's temps, it is fine. > > > Thanks for answering, > > > > -- > Best regards, > Igor Stasenko. > >

July 9, 2013