May 2016 - Pharo-dev - lists.pharo.org

[pharo-project/pharo-core]

by GitHub

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

May 16, 2016

[pharo-project/pharo-core] 4143a8: 60007

by GitHub

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: 4143a804695fe19dac6bb81c0738e0ca0721a9e5 https://github.com/pharo-project/pharo-core/commit/4143a804695fe19dac6bb81c… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-05-16 (Mon, 16 May 2016) Changed paths: A Graphics-Primitives.package/Color.class/instance/conversions/contrastingColorAdjustment.st A Morphic-Widgets-Tree.package/MorphTreeMorph.class/instance/updating/themeChanged.st M Morphic-Widgets-Tree.package/MorphTreeNodeMorph.class/instance/updating/themeChanged.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60006.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60007.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60006.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60007.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 60007 17896 MorphTreeMorph have trouble to update his theme https://pharo.fogbugz.com/f/cases/17896 http://files.pharo.org/image/60/60007.zip

May 16, 2016

Re: [Pharo-dev] Moving fogbugz entries from Pharo 5 to Pharo 6

by Peter UhnÃ¡k

Is there a problem in simply adding Inbox50 repo and clicking on the "Copy" button to put it to Inbox60? Or am I missing something? Peter On Mon, May 16, 2016 at 2:12 PM, ClÃ©ment Bera <bera.clement(a)gmail.com> wrote: > Hello, > > I have a problem in several bugs I opened on the bug tracker. When I > opened them, Pharo 6 development has not started, so the slices were > committed in the Pharo 5 inbox. As Pharo 5 was in stabilization phasis for > release, my slices were not integrated but postponed to Pharo 6 (which I > understand and accept). But since now the development is in Pharo 6, the > monkey checks the slice in Pharo 6 inbox and can't find my slices because > they are in Pharo 5 inbox. See for example 18039 or 17451. > > What is the right way to move the slices from Pharo 5 inbox to Pharo 6 > inbox ? I don't want to end up in a situation where it is not possible to > integrate my slice because of a "Missing ancestor", so how can I move the > slices from Pharo 5 inbox to Pharo 6 inbox without having that problem ? > > Thanks. >

May 16, 2016

OSSubprocess for Windows discussion [WAS] Re: [Pharo-users] OSProcess in Pharo 5?

by Mariano Martinez Peck

On Mon, May 16, 2016 at 9:25 AM, Mariano Martinez Peck < marianopeck(a)gmail.com> wrote: > > > On Sun, May 15, 2016 at 11:19 AM, Ben Coman <btc(a)openinworld.com> wrote: > >> On Sat, May 14, 2016 at 8:06 AM, Mariano Martinez Peck >> <marianopeck(a)gmail.com> wrote: >> > If you are only interested in Unix / Linux / OSX, >> >> What is the plan for Windows support? >> > > I am not planning to add that. What I have found, is that tools that try > to provide the same API for all platforms do not end up doing well or they > limit the specific benefits of each custom platform. I > > Sorry...shortcut sent email before I finished it. I am not planning to add that. What I have found, is that tools that try to provide the same API for all platforms do not end up doing well or they limit the specific benefits of each custom platform. I very much prefer the approach used by GitFileTree and others. That is... AT YOUR APPLICATION level, you check wether you are on windows or not. If you are under Linux/OSX, then you may want to use OSProcess / OSSubprocess. And if you are in windows, then you may want to use ProcessWrapper. A simple IF or a strategy or whatever that calls the right API. That way you can customize the code for each platform better. Finally, again, if someone wants a unified API, then I don't think it should be at OSProcess / OSSubprocess level. I would write an API that internally calls either ProcessWrapper or OS(Sub)Process. But I wouldn't use that API as mentioned above. Cheers, > cheers -ben >> >> > then you may want to try >> > OSSubprocess (it does work correctly in Pharo 5.0) >> > >> > https://github.com/marianopeck/OSSubprocess >> > >> > Cheers, >> > >> > >> > >> > On Fri, May 13, 2016 at 8:03 PM, PAUL DEBRUICKER <pdebruic(a)gmail.com> >> wrote: >> >> >> >> Hi - >> >> >> >> >> >> Is OSProcess the thing to use in Pharo 5 if you want to run a bash >> command >> >> and then bring the result into a running image? >> >> >> >> >> >> It seems to be locking up an image I've got with code that previously >> >> worked in Pharo 4. >> >> >> >> >> >> Thanks >> >> >> >> >> >> Paul >> > >> > >> > >> > >> > -- >> > Mariano >> > http://marianopeck.wordpress.com >> >> > > > -- > Mariano > http://marianopeck.wordpress.com > -- Mariano http://marianopeck.wordpress.com

May 16, 2016

Moving fogbugz entries from Pharo 5 to Pharo 6

by ClÃ©ment Bera

Hello, I have a problem in several bugs I opened on the bug tracker. When I opened them, Pharo 6 development has not started, so the slices were committed in the Pharo 5 inbox. As Pharo 5 was in stabilization phasis for release, my slices were not integrated but postponed to Pharo 6 (which I understand and accept). But since now the development is in Pharo 6, the monkey checks the slice in Pharo 6 inbox and can't find my slices because they are in Pharo 5 inbox. See for example 18039 or 17451. What is the right way to move the slices from Pharo 5 inbox to Pharo 6 inbox ? I don't want to end up in a situation where it is not possible to integrate my slice because of a "Missing ancestor", so how can I move the slices from Pharo 5 inbox to Pharo 6 inbox without having that problem ? Thanks.

May 16, 2016

Re: [Pharo-dev] IWST16 deadline extension

by Peter UhnÃ¡k

As a note, the deadline on the website hasn't been updated http://www.esug.org/wiki/pier/Conferences/2016/International-Workshop-IWST_… Peter On Mon, May 9, 2016 at 2:17 PM, Anne Etien <anne.etien(a)univ-lille1.fr> wrote: > [Please accept our apologies if you receive multiple copies of this call] > [Please send to interested colleagues / mailing-lists] > > ************************************************************************************************************ > CALL FOR PAPERS > > IWST16 â International Workshop on Smalltalk Technologies > > Prague, Czech Republic; August 23th, 2016 > > http://www.esug.org/wiki/pier/Conferences/2016/International-Workshop-IWST_… > > ************************************************************************************************************ > > ------------------- > Goals and scopes > ------------------- > > The goals of the workshop is to create a forum around advances or > experience in Smalltalk and to trigger discussions and exchanges of ideas. > The topics of your paper can be on all aspect of Smalltalk, theoretical as > well as practical. Participants are invited to submit research articles or > industrial papers. This year we want to open two different tracks: one > research track and one industrial track with less scientific constraints. > > We expect papers of three kinds: > > - Short position papers describing emerging ideas > - Long research papers with deeper description of experiments and of > research results. > - Industrial papers with presentation of real and innovative Smalltalk > applications; this kind of paper should enlighten why Smalltalk is really > appropriate for your application. > > *We will not enforce any length restriction.* > > -------------------- > Important Dates > -------------------- > > Submission deadline: *May 22th, 2016 (firm date)* > Notification deadline: June 20th, 2016 > Camera-ready : July 13th, 2016 > Workshop : August 23th, 2016 > *All accepted papers will be published in ACM DL (To be confirmed)* > *Best papers would be extended in an International Journal* > > ------------------- > Topics > ------------------- > > We welcome contributions on all aspects, theoretical as well as practical, > of Smalltalk related topics such as: > > -Aspect-oriented programming, > -Design patterns, > -Experience reports, > -Frameworks, > -Implementation, new dialects or languages implemented in Smalltalk, > -Interaction with other languages, > -Meta-programming and Meta-modeling, > -Tools > > ------------------- > Best Paper Award > ------------------- > > To encourage the submission of high-quality papers, the IWST organizing > committee is very proud to announce a Best Paper Award for this edition of > IWST. > > We thank the Lam Research Corporation for its financial contribution which > makes it possible for prizes for the three best papers: 1000 USD for first > place, 600 USD for second place and 400 USD for third place. > > The ranking will be decided by the program committee during the review > process. The awards will be given during the ESUG conference social event. > > The Best Paper Award will take place only with a minimum of six > submissions. Notice also that to be illegible, a paper must be presented at > the workshop by one of the author and that the presenting author must be > registered at the ESUG conference. > > ------------------- > Publication > ------------------- > > Both submissions and final papers must be prepared using the ACM SIGPLAN > 10 point format. Templates for Word and LaTeX are available at > http://www.acm.org/sigs/sigplan/authorInformation.htm. This site also > contains links to useful informations on how to write effective submissions. > > ------------------- > Submission > ------------------- > > All submissions must be sent via easychair: > https://easychair.org/conferences/?conf=iwst20160 > > ------------------- > Program chairs > ------------------- > > Anne Etien (UniversitÃ© de Lille 1, France) > Jannik Laval (UniversitÃ© Lyon 2 LumiÃ¨re, France) >

May 16, 2016

[pharo-project/pharo-core]

by GitHub

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

May 16, 2016

[pharo-project/pharo-core] cbee24: 60006

by GitHub

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: cbee242d058b3b437d58865a186ff175a111e4d1 https://github.com/pharo-project/pharo-core/commit/cbee242d058b3b437d58865a… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-05-16 (Mon, 16 May 2016) Changed paths: R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60005.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60006.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60005.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60006.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st A Tool-CriticBrowser.package/CriticBrowser.class/instance/api/defaultTitle.st M Tool-CriticBrowser.package/CriticBrowser.class/instance/api/setTitle_.st M Tool-CriticBrowser.package/CriticBrowser.class/instance/initialization/initializePresenter.st M Tool-CriticBrowser.package/CriticBrowser.class/instance/initialization/initializeWidgets.st M Tool-CriticBrowser.package/CriticBrowser.class/instance/private/applyRules.st M Tool-CriticBrowser.package/CriticBrowser.class/instance/private/reapplyAllRules.st Log Message: ----------- 60006 18230 Critic Browser window title set to nil after deselecting a rule https://pharo.fogbugz.com/f/cases/18230 http://files.pharo.org/image/60/60006.zip

May 16, 2016

Re: [Pharo-dev] call for cleaning ideas around Spec

by stepharo

Since the array is recursively performing its nested elements the expression row newColumn: [ :col | col add: #topToolbar height: self toolbarHeight ] was probably to get #columSpec addHeight: #(itemSpec topToolBar #toolbarheight) which would lead to aColumn perform: addHeight withArguments: (anItemSpec perform: topToolBar with: (model/presenter toolbarheight) The trick is to see who should be the receiver In visualWorks a windowSpec contains only literals like in Spec and I do not know how they can make such difference. Stef

May 16, 2016

Re: [Pharo-dev] call for cleaning ideas around Spec

by stepharo

Denis this is the same. at the end we get an array and from this array we should get widgets. Stef Le 9/5/16 Ã 13:22, Denis Kudriashov a Ã©crit : > > 2016-05-09 11:38 GMT+02:00 Peter UhnÃ¡k <i.uhnak(a)gmail.com > <mailto:i.uhnak@gmail.com>>: > > No. Morphs are created by Adapters, Spec interpreter instantiates > glues everything together. > Regardless, there's no parsing involvedâ¦ what is there to parse? > There are no literal arrays anywhere. > The SpecLayout (that we called array last week), is not an array, > it's a composition of real objects > > defaultSpec > ^ SpecLayout composed > newRow: [ :row | row newColumn: [ :col | col add: #topToolbar > height: self toolbarHeight ] ] > height: self toolbarHeight; > newRow: [ :row | > row > newColumn: [ :col | col add: #navigatorModel ] origin: 0 @ 0 > corner: 0.2 @ 1; > addSplitter; > newColumn: [ :col | col add: #tabManager ] origin: 0.2 @ 0 corner: > 0.85 @ 1; > addSplitter; > newColumn: [ :col | col add: #formModel ] origin: 0.85 @ 0 corner: > 1 @ 1 ] > top: self toolbarHeight; > yourself > > > Maybe array approach deprecated? But in first demos of Spec it was > like this: > > CheckBoxExample class>>defaultSpec > > ^ { #ContainerModel. > #add:.{ self topSpec. #layout:. #(#SpecLayoutFrame > bottomFraction: 0 > bottomOffset: 20) }. > #add:.{{#model . #container } . #layout: . #(#SpecLayoutFrame > topOffset: 22) } > } > > (Actually it is from Pharo 5 image).

May 16, 2016