May 2018 - Pharo-users - lists.pharo.org

Re: [Pharo-users] Lazy vs eager initialization

by Norbert Hartl

+1 Norbert > Am 30.05.2018 um 05:20 schrieb Ben Coman <btc(a)openinworld.com>: > > While protoyping in a "live" system like Pharo, you often may add a new instance variable to existing object, > the value of which is "nil" and may break the associated behaviour you next add. > To deal with that you either have to sprinkle ifNils: around your code, > or alternatively do it in one location with lazy initialization. > > So in general, lazy initialization is good for prototyping. > Once you're past prototyping there might be some advantage to refactoring away from lazy initialization. > > cheers -ben > > > > > On 29 May 2018 at 23:49, sergio ruiz <sergio.rrd(a)gmail.com <mailto:sergio.rrd@gmail.com>> wrote: > If a model has a list of things.. such as a user that can/may have lots of pets, are there any real benefits to initializing the list of pets lazily? > > like: > > self pets := OrderedCollection new. > > vs. > > pets > pets ifNil: [self pets: OrderedCollection new] > ^ pets > > thanks! > > ---- > peace, > sergio > photographer, journalist, visionary > > Public Key: http://bit.ly/29z9fG0 <http://bit.ly/29z9fG0> > #BitMessage BM-NBaswViL21xqgg9STRJjaJaUoyiNe2dV > http://www.codeandmusic.com <http://www.codeandmusic.com/> > http://www.twitter.com/sergio_101 <http://www.twitter.com/sergio_101> > http://www.facebook.com/sergio101 <http://www.facebook.com/sergio101>

May 30, 2018

Re: [Pharo-users] [ANN] Iceberg v1.0.0

by tesonep＠gmail.com

I am talking about the long paths issue. On Wed, May 30, 2018 at 9:57 AM, tesonep(a)gmail.com <tesonep(a)gmail.com> wrote: > Hello, > Esteban maybe you can correct me, but in the new Pharo7 VM this issue > with the long paths is not partially corrected? > Maybe Andrei you can try with the Pharo 7 VM, even though it is not still > marked as stable for Pharo 6. > > Cheers, > > On Wed, May 30, 2018 at 9:52 AM, Guillermo Polito < > guillermopolito(a)gmail.com> wrote: > >> Hi! >> >> On Wed, May 30, 2018 at 7:51 AM, Esteban Lorenzano <estebanlm(a)gmail.com> >> wrote: >> >>> hi, >>> >>> On 30 May 2018, at 01:59, Andrei Stebakov <lispercat(a)gmail.com> wrote: >>> >>> On Pharo 7.0, Windows 10 when I try to clone from pillar-markup/pillar >>> on Windows 10, it gives me an error "the filename or extension is too longâ >>> >>> >>> this is more a problem of pillar being in filetree format than iceberg. >>> there is no clear way to fix that other than migrate to tonel. >>> >>> but you can try to get smaller paths, like putting your sources in >>> C:\pillar >>> >> >> I've opened an issue in pillar. I'll try to do it later this morning. >> >> https://github.com/pillar-markup/pillar/issues/300 >> >> >>> >>> Also I got a couple of questions: >>> - How do I check the version of Iceberg >>> >>> >>> not much way this days, since iceberg is installed outside iceberg. >>> >> >> I've opened an issue in Iceberg. I believe we should be able to retrieve >> the current installed version. Otherwise it will be far too difficult to >> ask users for good feedback. >> We already ask: What OS are you on? What pharo version are you on? We >> should ask them "What Iceberg version are you on"? >> >> https://github.com/pharo-vcs/iceberg/issues/824 >> >> >>> >>> - How can I update from Iceberg 0.7.1 on Pharo 6.1 (installed using >>> instructions from https://github.com/pharo-vcs/iceberg) to latest >>> Iceberg 1.0.1? >>> >>> >>> The instructions there are titled âupdating icebergâ and âfor Pharo 6.1â >>> so yes :) >>> the only difference is you have to change â0.7.?â with â1.0.?â (I need >>> to update that). >>> >> >> Done >> >> https://github.com/pharo-vcs/iceberg/commit/acd66a0b5cc22ffe >> 1317434f9bc41b809b70571c >> >> >>> >>> Esteban >>> >>> >>> Thanks! >>> Andrei >>> >>> On Tue, May 29, 2018 at 5:30 AM, Guillermo Polito < >>> guillermopolito(a)gmail.com> wrote: >>> >>>> Hi all, >>>> >>>> Time for a new Iceberg update, that will be available in the next Pharo >>>> build. This time, there are lots of cleanups and enhancements. On the big >>>> highlights: >>>> >>>> - Tonel migration plugin is available in the "Other menu item" >>>> - Tests are green on 64 bits! (meaning iceberg can be safely used in 64 >>>> bits). >>>> >>>> Thanks to everybody that participated in reviewing, opening/closing >>>> issues or even fixing a typo! >>>> >>>> # Documentation >>>> >>>> Just as a reminder, here you have a link to iceberg's wiki, convering >>>> some info like terminology, how to help us, and so on... >>>> >>>> https://github.com/pharo-vcs/iceberg/wiki >>>> >>>> # And some videos ;) >>>> >>>> - Branching and merging https://www.youtube.com/watch?v=DBzkjwABPEI >>>> - Loading a Baseline https://youtu.be/brUHEOr-p_E >>>> - Contributing to Iceberg https://youtu.be/yGr5HvVWM0M >>>> >>>> # Changes Log >>>> >>>> https://github.com/pharo-vcs/iceberg/releases/tag/v1.0.0 >>>> >>>> Enjoy, Guille >>>> >>>> PS, detailed changes log below: >>>> >>>> # Cleanups >>>> >>>> #819 Fix tooltip typo in settings >>>> #800 Iceberg should be removed from the catalogue >>>> #801 Remove not referenced packages >>>> #803 Correct some lints in tests >>>> #806 Bad repair options when local repository is missing >>>> #725 Remove and clean old UI >>>> #794 Some classes should use category "utilities" instead of "utility" >>>> #791 Begin to remove old UI >>>> #734 Begin to remove old UI >>>> #576 Add link to github/gitlab ssh instructions >>>> >>>> # Enhancements >>>> >>>> #776 Upgrade to Commander 0.6.2 dependencies >>>> #765 Add command to copy SHA from history window >>>> #793 Add the commit message to history window >>>> #785 Metacello conflicts are not handled Metacello Integration >>>> >>>> # Bug fixes >>>> >>>> #771 IceTipRemoveFromRepositoryPackageCommand >> execute is not >>>> implemented >>>> #748 Code subdirectory in empty repository >>>> #767 Error while pulling with renamed packages >>>> #814 Moving extension from a package removes extended class >>>> #807 When we do not have the right to push on a report we get an Error >>>> instead of the pop up! >>>> #768 Inverse merge preview shows wrong diff >>>> #784 Pulling from a non existing remote branch fails#810 >>>> #removePackage: should recursively delete files >>>> >>>> # Documentation >>>> >>>> #702 Create screencast - How to contribute to iceberg >>>> #774 Copy Wiki contribution page to pharo-project/pharo wiki >>>> >>>> # Infrastructure >>>> >>>> #761 Make tests run in 64 bits Pharo 7 >>>> >>>> >>> >>> >> >> >> -- >> >> >> >> Guille Polito >> >> Research Engineer >> >> Centre de Recherche en Informatique, Signal et Automatique de Lille >> >> CRIStAL - UMR 9189 >> >> French National Center for Scientific Research - *http://www.cnrs.fr >> <http://www.cnrs.fr>* >> >> >> *Web:* *http://guillep.github.io* <http://guillep.github.io> >> >> *Phone: *+33 06 52 70 66 13 >> > > > > -- > Pablo Tesone. > tesonep(a)gmail.com > -- Pablo Tesone. tesonep(a)gmail.com

May 30, 2018

Re: [Pharo-users] [ANN] Iceberg v1.0.0

by tesonep＠gmail.com

Hello, Esteban maybe you can correct me, but in the new Pharo7 VM this issue with the long paths is not partially corrected? Maybe Andrei you can try with the Pharo 7 VM, even though it is not still marked as stable for Pharo 6. Cheers, On Wed, May 30, 2018 at 9:52 AM, Guillermo Polito <guillermopolito(a)gmail.com > wrote: > Hi! > > On Wed, May 30, 2018 at 7:51 AM, Esteban Lorenzano <estebanlm(a)gmail.com> > wrote: > >> hi, >> >> On 30 May 2018, at 01:59, Andrei Stebakov <lispercat(a)gmail.com> wrote: >> >> On Pharo 7.0, Windows 10 when I try to clone from pillar-markup/pillar on >> Windows 10, it gives me an error "the filename or extension is too longâ >> >> >> this is more a problem of pillar being in filetree format than iceberg. >> there is no clear way to fix that other than migrate to tonel. >> >> but you can try to get smaller paths, like putting your sources in >> C:\pillar >> > > I've opened an issue in pillar. I'll try to do it later this morning. > > https://github.com/pillar-markup/pillar/issues/300 > > >> >> Also I got a couple of questions: >> - How do I check the version of Iceberg >> >> >> not much way this days, since iceberg is installed outside iceberg. >> > > I've opened an issue in Iceberg. I believe we should be able to retrieve > the current installed version. Otherwise it will be far too difficult to > ask users for good feedback. > We already ask: What OS are you on? What pharo version are you on? We > should ask them "What Iceberg version are you on"? > > https://github.com/pharo-vcs/iceberg/issues/824 > > >> >> - How can I update from Iceberg 0.7.1 on Pharo 6.1 (installed using >> instructions from https://github.com/pharo-vcs/iceberg) to latest >> Iceberg 1.0.1? >> >> >> The instructions there are titled âupdating icebergâ and âfor Pharo 6.1â >> so yes :) >> the only difference is you have to change â0.7.?â with â1.0.?â (I need to >> update that). >> > > Done > > https://github.com/pharo-vcs/iceberg/commit/acd66a0b5cc22ffe1317434f9bc41b > 809b70571c > > >> >> Esteban >> >> >> Thanks! >> Andrei >> >> On Tue, May 29, 2018 at 5:30 AM, Guillermo Polito < >> guillermopolito(a)gmail.com> wrote: >> >>> Hi all, >>> >>> Time for a new Iceberg update, that will be available in the next Pharo >>> build. This time, there are lots of cleanups and enhancements. On the big >>> highlights: >>> >>> - Tonel migration plugin is available in the "Other menu item" >>> - Tests are green on 64 bits! (meaning iceberg can be safely used in 64 >>> bits). >>> >>> Thanks to everybody that participated in reviewing, opening/closing >>> issues or even fixing a typo! >>> >>> # Documentation >>> >>> Just as a reminder, here you have a link to iceberg's wiki, convering >>> some info like terminology, how to help us, and so on... >>> >>> https://github.com/pharo-vcs/iceberg/wiki >>> >>> # And some videos ;) >>> >>> - Branching and merging https://www.youtube.com/watch?v=DBzkjwABPEI >>> - Loading a Baseline https://youtu.be/brUHEOr-p_E >>> - Contributing to Iceberg https://youtu.be/yGr5HvVWM0M >>> >>> # Changes Log >>> >>> https://github.com/pharo-vcs/iceberg/releases/tag/v1.0.0 >>> >>> Enjoy, Guille >>> >>> PS, detailed changes log below: >>> >>> # Cleanups >>> >>> #819 Fix tooltip typo in settings >>> #800 Iceberg should be removed from the catalogue >>> #801 Remove not referenced packages >>> #803 Correct some lints in tests >>> #806 Bad repair options when local repository is missing >>> #725 Remove and clean old UI >>> #794 Some classes should use category "utilities" instead of "utility" >>> #791 Begin to remove old UI >>> #734 Begin to remove old UI >>> #576 Add link to github/gitlab ssh instructions >>> >>> # Enhancements >>> >>> #776 Upgrade to Commander 0.6.2 dependencies >>> #765 Add command to copy SHA from history window >>> #793 Add the commit message to history window >>> #785 Metacello conflicts are not handled Metacello Integration >>> >>> # Bug fixes >>> >>> #771 IceTipRemoveFromRepositoryPackageCommand >> execute is not >>> implemented >>> #748 Code subdirectory in empty repository >>> #767 Error while pulling with renamed packages >>> #814 Moving extension from a package removes extended class >>> #807 When we do not have the right to push on a report we get an Error >>> instead of the pop up! >>> #768 Inverse merge preview shows wrong diff >>> #784 Pulling from a non existing remote branch fails#810 #removePackage: >>> should recursively delete files >>> >>> # Documentation >>> >>> #702 Create screencast - How to contribute to iceberg >>> #774 Copy Wiki contribution page to pharo-project/pharo wiki >>> >>> # Infrastructure >>> >>> #761 Make tests run in 64 bits Pharo 7 >>> >>> >> >> > > > -- > > > > Guille Polito > > Research Engineer > > Centre de Recherche en Informatique, Signal et Automatique de Lille > > CRIStAL - UMR 9189 > > French National Center for Scientific Research - *http://www.cnrs.fr > <http://www.cnrs.fr>* > > > *Web:* *http://guillep.github.io* <http://guillep.github.io> > > *Phone: *+33 06 52 70 66 13 > -- Pablo Tesone. tesonep(a)gmail.com

May 30, 2018

Re: [Pharo-users] [ANN] Iceberg v1.0.0

by Guillermo Polito

Hi! On Wed, May 30, 2018 at 7:51 AM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > hi, > > On 30 May 2018, at 01:59, Andrei Stebakov <lispercat(a)gmail.com> wrote: > > On Pharo 7.0, Windows 10 when I try to clone from pillar-markup/pillar on > Windows 10, it gives me an error "the filename or extension is too longâ > > > this is more a problem of pillar being in filetree format than iceberg. > there is no clear way to fix that other than migrate to tonel. > > but you can try to get smaller paths, like putting your sources in > C:\pillar > I've opened an issue in pillar. I'll try to do it later this morning. https://github.com/pillar-markup/pillar/issues/300 > > Also I got a couple of questions: > - How do I check the version of Iceberg > > > not much way this days, since iceberg is installed outside iceberg. > I've opened an issue in Iceberg. I believe we should be able to retrieve the current installed version. Otherwise it will be far too difficult to ask users for good feedback. We already ask: What OS are you on? What pharo version are you on? We should ask them "What Iceberg version are you on"? https://github.com/pharo-vcs/iceberg/issues/824 > > - How can I update from Iceberg 0.7.1 on Pharo 6.1 (installed using > instructions from https://github.com/pharo-vcs/iceberg) to latest Iceberg > 1.0.1? > > > The instructions there are titled âupdating icebergâ and âfor Pharo 6.1â > so yes :) > the only difference is you have to change â0.7.?â with â1.0.?â (I need to > update that). > Done https://github.com/pharo-vcs/iceberg/commit/acd66a0b5cc22ffe1317434f9bc41b8… > > Esteban > > > Thanks! > Andrei > > On Tue, May 29, 2018 at 5:30 AM, Guillermo Polito < > guillermopolito(a)gmail.com> wrote: > >> Hi all, >> >> Time for a new Iceberg update, that will be available in the next Pharo >> build. This time, there are lots of cleanups and enhancements. On the big >> highlights: >> >> - Tonel migration plugin is available in the "Other menu item" >> - Tests are green on 64 bits! (meaning iceberg can be safely used in 64 >> bits). >> >> Thanks to everybody that participated in reviewing, opening/closing >> issues or even fixing a typo! >> >> # Documentation >> >> Just as a reminder, here you have a link to iceberg's wiki, convering >> some info like terminology, how to help us, and so on... >> >> https://github.com/pharo-vcs/iceberg/wiki >> >> # And some videos ;) >> >> - Branching and merging https://www.youtube.com/watch?v=DBzkjwABPEI >> - Loading a Baseline https://youtu.be/brUHEOr-p_E >> - Contributing to Iceberg https://youtu.be/yGr5HvVWM0M >> >> # Changes Log >> >> https://github.com/pharo-vcs/iceberg/releases/tag/v1.0.0 >> >> Enjoy, Guille >> >> PS, detailed changes log below: >> >> # Cleanups >> >> #819 Fix tooltip typo in settings >> #800 Iceberg should be removed from the catalogue >> #801 Remove not referenced packages >> #803 Correct some lints in tests >> #806 Bad repair options when local repository is missing >> #725 Remove and clean old UI >> #794 Some classes should use category "utilities" instead of "utility" >> #791 Begin to remove old UI >> #734 Begin to remove old UI >> #576 Add link to github/gitlab ssh instructions >> >> # Enhancements >> >> #776 Upgrade to Commander 0.6.2 dependencies >> #765 Add command to copy SHA from history window >> #793 Add the commit message to history window >> #785 Metacello conflicts are not handled Metacello Integration >> >> # Bug fixes >> >> #771 IceTipRemoveFromRepositoryPackageCommand >> execute is not >> implemented >> #748 Code subdirectory in empty repository >> #767 Error while pulling with renamed packages >> #814 Moving extension from a package removes extended class >> #807 When we do not have the right to push on a report we get an Error >> instead of the pop up! >> #768 Inverse merge preview shows wrong diff >> #784 Pulling from a non existing remote branch fails#810 #removePackage: >> should recursively delete files >> >> # Documentation >> >> #702 Create screencast - How to contribute to iceberg >> #774 Copy Wiki contribution page to pharo-project/pharo wiki >> >> # Infrastructure >> >> #761 Make tests run in 64 bits Pharo 7 >> >> > > -- Guille Polito Research Engineer Centre de Recherche en Informatique, Signal et Automatique de Lille CRIStAL - UMR 9189 French National Center for Scientific Research - *http://www.cnrs.fr <http://www.cnrs.fr>* *Web:* *http://guillep.github.io* <http://guillep.github.io> *Phone: *+33 06 52 70 66 13

May 30, 2018

Re: [Pharo-users] [ANN] Iceberg v1.0.0

by Esteban Lorenzano

hi, > On 30 May 2018, at 01:59, Andrei Stebakov <lispercat(a)gmail.com> wrote: > > On Pharo 7.0, Windows 10 when I try to clone from pillar-markup/pillar on Windows 10, it gives me an error "the filename or extension is too longâ this is more a problem of pillar being in filetree format than iceberg. there is no clear way to fix that other than migrate to tonel. but you can try to get smaller paths, like putting your sources in C:\pillar > Also I got a couple of questions: > - How do I check the version of Iceberg not much way this days, since iceberg is installed outside iceberg. > - How can I update from Iceberg 0.7.1 on Pharo 6.1 (installed using instructions from https://github.com/pharo-vcs/iceberg <https://github.com/pharo-vcs/iceberg>) to latest Iceberg 1.0.1? The instructions there are titled âupdating icebergâ and âfor Pharo 6.1â so yes :) the only difference is you have to change â0.7.?â with â1.0.?â (I need to update that). Esteban > > Thanks! > Andrei > > On Tue, May 29, 2018 at 5:30 AM, Guillermo Polito <guillermopolito(a)gmail.com <mailto:guillermopolito@gmail.com>> wrote: > Hi all, > > Time for a new Iceberg update, that will be available in the next Pharo build. This time, there are lots of cleanups and enhancements. On the big highlights: > > - Tonel migration plugin is available in the "Other menu item" > - Tests are green on 64 bits! (meaning iceberg can be safely used in 64 bits). > > Thanks to everybody that participated in reviewing, opening/closing issues or even fixing a typo! > > # Documentation > > Just as a reminder, here you have a link to iceberg's wiki, convering some info like terminology, how to help us, and so on... > > https://github.com/pharo-vcs/iceberg/wiki <https://github.com/pharo-vcs/iceberg/wiki> > > # And some videos ;) > > - Branching and merging https://www.youtube.com/watch?v=DBzkjwABPEI <https://www.youtube.com/watch?v=DBzkjwABPEI> > - Loading a Baseline https://youtu.be/brUHEOr-p_E <https://youtu.be/brUHEOr-p_E> > - Contributing to Iceberg https://youtu.be/yGr5HvVWM0M <https://youtu.be/yGr5HvVWM0M> > > # Changes Log > > https://github.com/pharo-vcs/iceberg/releases/tag/v1.0.0 <https://github.com/pharo-vcs/iceberg/releases/tag/v1.0.0> > > Enjoy, Guille > > PS, detailed changes log below: > > # Cleanups > > #819 Fix tooltip typo in settings > #800 Iceberg should be removed from the catalogue > #801 Remove not referenced packages > #803 Correct some lints in tests > #806 Bad repair options when local repository is missing > #725 Remove and clean old UI > #794 Some classes should use category "utilities" instead of "utility" > #791 Begin to remove old UI > #734 Begin to remove old UI > #576 Add link to github/gitlab ssh instructions > > # Enhancements > > #776 Upgrade to Commander 0.6.2 dependencies > #765 Add command to copy SHA from history window > #793 Add the commit message to history window > #785 Metacello conflicts are not handled Metacello Integration > > # Bug fixes > > #771 IceTipRemoveFromRepositoryPackageCommand >> execute is not implemented > #748 Code subdirectory in empty repository > #767 Error while pulling with renamed packages > #814 Moving extension from a package removes extended class > #807 When we do not have the right to push on a report we get an Error instead of the pop up! > #768 Inverse merge preview shows wrong diff > #784 Pulling from a non existing remote branch fails#810 #removePackage: should recursively delete files > > # Documentation > > #702 Create screencast - How to contribute to iceberg > #774 Copy Wiki contribution page to pharo-project/pharo wiki > > # Infrastructure > > #761 Make tests run in 64 bits Pharo 7 > >

May 30, 2018

Re: [Pharo-users] Lazy vs eager initialization

by Ben Coman

While protoyping in a "live" system like Pharo, you often may add a new instance variable to existing object, the value of which is "nil" and may break the associated behaviour you next add. To deal with that you either have to sprinkle ifNils: around your code, or alternatively do it in one location with lazy initialization. So in general, lazy initialization is good for prototyping. Once you're past prototyping there might be some advantage to refactoring away from lazy initialization. cheers -ben On 29 May 2018 at 23:49, sergio ruiz <sergio.rrd(a)gmail.com> wrote: > If a model has a list of things.. such as a user that can/may have lots of > pets, are there any real benefits to initializing the list of pets lazily? > > like: > > self pets := OrderedCollection new. > > vs. > > pets > pets ifNil: [self pets: OrderedCollection new] > ^ pets > > thanks! > > ---- > peace, > sergio > photographer, journalist, visionary > > Public Key: http://bit.ly/29z9fG0 > #BitMessage BM-NBaswViL21xqgg9STRJjaJaUoyiNe2dV > http://www.codeandmusic.com > http://www.twitter.com/sergio_101 > http://www.facebook.com/sergio101 >

May 30, 2018

Re: [Pharo-users] [ANN] Iceberg v1.0.0

by Andrei Stebakov

On Pharo 7.0, Windows 10 when I try to clone from pillar-markup/pillar on Windows 10, it gives me an error "the filename or extension is too long" Also I got a couple of questions: - How do I check the version of Iceberg - How can I update from Iceberg 0.7.1 on Pharo 6.1 (installed using instructions from https://github.com/pharo-vcs/iceberg) to latest Iceberg 1.0.1? Thanks! Andrei On Tue, May 29, 2018 at 5:30 AM, Guillermo Polito <guillermopolito(a)gmail.com > wrote: > Hi all, > > Time for a new Iceberg update, that will be available in the next Pharo > build. This time, there are lots of cleanups and enhancements. On the big > highlights: > > - Tonel migration plugin is available in the "Other menu item" > - Tests are green on 64 bits! (meaning iceberg can be safely used in 64 > bits). > > Thanks to everybody that participated in reviewing, opening/closing issues > or even fixing a typo! > > # Documentation > > Just as a reminder, here you have a link to iceberg's wiki, convering some > info like terminology, how to help us, and so on... > > https://github.com/pharo-vcs/iceberg/wiki > > # And some videos ;) > > - Branching and merging https://www.youtube.com/watch?v=DBzkjwABPEI > - Loading a Baseline https://youtu.be/brUHEOr-p_E > - Contributing to Iceberg https://youtu.be/yGr5HvVWM0M > > # Changes Log > > https://github.com/pharo-vcs/iceberg/releases/tag/v1.0.0 > > Enjoy, Guille > > PS, detailed changes log below: > > # Cleanups > > #819 Fix tooltip typo in settings > #800 Iceberg should be removed from the catalogue > #801 Remove not referenced packages > #803 Correct some lints in tests > #806 Bad repair options when local repository is missing > #725 Remove and clean old UI > #794 Some classes should use category "utilities" instead of "utility" > #791 Begin to remove old UI > #734 Begin to remove old UI > #576 Add link to github/gitlab ssh instructions > > # Enhancements > > #776 Upgrade to Commander 0.6.2 dependencies > #765 Add command to copy SHA from history window > #793 Add the commit message to history window > #785 Metacello conflicts are not handled Metacello Integration > > # Bug fixes > > #771 IceTipRemoveFromRepositoryPackageCommand >> execute is not > implemented > #748 Code subdirectory in empty repository > #767 Error while pulling with renamed packages > #814 Moving extension from a package removes extended class > #807 When we do not have the right to push on a report we get an Error > instead of the pop up! > #768 Inverse merge preview shows wrong diff > #784 Pulling from a non existing remote branch fails#810 #removePackage: > should recursively delete files > > # Documentation > > #702 Create screencast - How to contribute to iceberg > #774 Copy Wiki contribution page to pharo-project/pharo wiki > > # Infrastructure > > #761 Make tests run in 64 bits Pharo 7 > >

May 29, 2018

Re: [Pharo-users] [ANN] Iceberg v1.0.0

by Andrei Stebakov

Is there support for HTTPS on Windows (or any plans to get it to work)? On Tue, May 29, 2018 at 5:30 AM, Guillermo Polito <guillermopolito(a)gmail.com > wrote: > Hi all, > > Time for a new Iceberg update, that will be available in the next Pharo > build. This time, there are lots of cleanups and enhancements. On the big > highlights: > > - Tonel migration plugin is available in the "Other menu item" > - Tests are green on 64 bits! (meaning iceberg can be safely used in 64 > bits). > > Thanks to everybody that participated in reviewing, opening/closing issues > or even fixing a typo! > > # Documentation > > Just as a reminder, here you have a link to iceberg's wiki, convering some > info like terminology, how to help us, and so on... > > https://github.com/pharo-vcs/iceberg/wiki > > # And some videos ;) > > - Branching and merging https://www.youtube.com/watch?v=DBzkjwABPEI > - Loading a Baseline https://youtu.be/brUHEOr-p_E > - Contributing to Iceberg https://youtu.be/yGr5HvVWM0M > > # Changes Log > > https://github.com/pharo-vcs/iceberg/releases/tag/v1.0.0 > > Enjoy, Guille > > PS, detailed changes log below: > > # Cleanups > > #819 Fix tooltip typo in settings > #800 Iceberg should be removed from the catalogue > #801 Remove not referenced packages > #803 Correct some lints in tests > #806 Bad repair options when local repository is missing > #725 Remove and clean old UI > #794 Some classes should use category "utilities" instead of "utility" > #791 Begin to remove old UI > #734 Begin to remove old UI > #576 Add link to github/gitlab ssh instructions > > # Enhancements > > #776 Upgrade to Commander 0.6.2 dependencies > #765 Add command to copy SHA from history window > #793 Add the commit message to history window > #785 Metacello conflicts are not handled Metacello Integration > > # Bug fixes > > #771 IceTipRemoveFromRepositoryPackageCommand >> execute is not > implemented > #748 Code subdirectory in empty repository > #767 Error while pulling with renamed packages > #814 Moving extension from a package removes extended class > #807 When we do not have the right to push on a report we get an Error > instead of the pop up! > #768 Inverse merge preview shows wrong diff > #784 Pulling from a non existing remote branch fails#810 #removePackage: > should recursively delete files > > # Documentation > > #702 Create screencast - How to contribute to iceberg > #774 Copy Wiki contribution page to pharo-project/pharo wiki > > # Infrastructure > > #761 Make tests run in 64 bits Pharo 7 > >

May 29, 2018

Second Call for Papers: 11th ACM SIGPLAN International Conference on Software Language Engineering (SLE 2018)

by Andrei Chis

------------------------------------------------------------------------ Call for Papers: 11th ACM SIGPLAN International Conference on Software Language Engineering (SLE 2018) co-located with SPLASH 2018 November 5-6, 2018 Boston, Massachusetts, United States https://conf.researchr.org/track/sle-2018/papers ------------------------------------------------------------------------ We are pleased to invite you to submit papers to the 11th ACM SIGPLAN International Conference on Software Language Engineering (SLE 2018), held in conjunction with SPLASH 2018 at Boston, Massachusetts on November 5-6, 2018. --------------------------- Scope --------------------------- With the ubiquity of computers, software has become the dominating intellectual asset of our time. In turn, this software depends on software languages, namely the languages it is written in, the languages used to describe its environment, and the languages driving its development process. Given that everything depends on software and that software depends on software languages, it seems fair to say that for many years to come, everything will depend on software languages. Software language engineering (SLE) is the discipline of engineering languages and their tools required for the creation of software. It abstracts from the differences between programming languages, modelling languages, and other software languages, and emphasizes the engineering facet of the creation of such languages, that is, the establishment of the scientific methods and practices that enable the best results. While SLE is certainly driven by its metacircular character (software languages are engineered using software languages), SLE is not self-satisfying: its scope extends to the engineering of languages for all and everything. Like its predecessors, the 11th edition of the SLE conference, SLE 2018, will bring together researchers from different areas united by their common interest in the creation, capture, and tooling of software languages. It overlaps with traditional conferences on the design and implementation of programming languages, model-driven engineering, and compiler construction, and emphasizes the fusion of their communities. To foster the latter, SLE traditionally fills a two-day program with a single track, with the only temporal overlap occurring between co-located events. --------------------------- Topics of Interest --------------------------- SLE 2018 solicits high-quality contributions in areas ranging from theoretical and conceptual contributions, to tools, techniques, and frameworks in the domain of software language engineering. Topics relevant to SLE cover generic aspects of software languages development rather than aspects of engineering a specific language. In particular, SLE is interested in contributions from the following areas: * Software Language Design and Implementation - Approaches to and methods for language design - Static semantics (e.g., design rules, well-formedness constraints) - Techniques for specifying behavioral / executable semantics - Generative approaches (incl. code synthesis, compilation) - Meta-languages, meta-tools, language workbenches * Software Language Validation - Verification and formal methods for languages - Testing techniques for languages - Simulation techniques for languages * Software Language Integration and Composition - Coordination of heterogeneous languages and tools - Mappings between languages (incl. transformation languages) - Traceability between languages - Deployment of languages to different platforms * Software Language Maintenance - Software language reuse - Language evolution - Language families and variability * Domain-specific approaches for any aspects of SLE (design, implementation, validation, maintenance) * Empirical evaluation and experience reports of language engineering tools - User studies evaluating usability - Performance benchmarks - Industrial applications --------------------------- Important Dates --------------------------- All dates are Anywhere on Earth. * Fri 29 June 2018 - Abstract Submission * Fri 6 July 2018 - Paper Submission * Fri 24 August 2018 - Author Notification * Fri 31 August 2018 - Artifact Submission * Fri 14 September 2018 - Artifact Kick-the-Tires Evaluation Author Response * Fri 5 October 2018 - Camera Ready Deadline * Wed 10 October 2018 - Artifact Notification * Fri 12 October 2018 - Deadline for Artifact-Related Paper Updates * Sun 4 Nov 2018 - SLE Workshops * Mon 5 Nov - Tue 6 Nov 2018 - SLE Conference --------------------------- Types of Submissions --------------------------- * Research papers These should report a substantial research contribution to SLE or successful application of SLE techniques or both. Full paper submissions must not exceed 12 pages excluding bibliography. * Tool papers Because of SLEâs interest in tools, we seek papers that present software tools related to the field of SLE. Selection criteria include originality of the tool, its innovative aspects, and relevance to SLE. Any of the SLE topics of interest are appropriate areas for tool demonstrations. Submissions must provide a tool description of 4 pages excluding bibliography, and a demonstration outline including screenshots of up to 6 pages. Tool demonstrations must have the keywords âTool Demoâ or âTool Demonstrationâ in the title. The 4-page tool description will, if the demonstration is accepted, be published in the proceedings. The 6-page demonstration outline will be used by the program committee only for evaluating the submission. * New ideas / vision papers New ideas papers should describe new, non-conventional SLE research approaches that depart from standard practice. They are intended to describe well-defined research ideas that are at an early stage of investigation. Vision papers are intended to present new unifying theories about existing SLE research that can lead to the development of new technologies or approaches. New ideas / vision papers must not exceed 4 pages excluding bibliography. --------------------------- Artifact Evaluation --------------------------- For the third year SLE will use an evaluation process for assessing the quality of the artifacts on which papers are based to foster the culture of experimental reproducibility. Authors of accepted papers are invited to submit artifacts. More information is provided on the conference Website. --------------------------- Submission --------------------------- Submissions have to use the ACM SIGPLAN Conference Format "acmart" ( http://sigplan.org/Resources/Author/#acmart-format) please make sure that you always use the latest ACM SIGPLAN acmart LaTeX template ( https://www.acm.org/binaries/content/assets/publications/consolidated-tex-t…) and that the document class definition is \documentclass[sigplan,screen]{acmart}. Do not make any changes to this format! Using the Word template is strongly discouraged. Ensure that your submission is legible when printed on a black and white printer. In particular, please check that colors remain distinct and font sizes in figures and tables are legible. SLE follows a single-blind review process. Thus, you do not have to blind your submission. All submissions must be in PDF format. Concurrent Submissions: Papers must describe unpublished work that is not currently submitted for publication elsewhere as described by SIGPLANâs Republication Policy ( http://www.sigplan.org/Resources/Policies/Republication) Submitters should also be aware of ACMâs Policy and Procedures on Plagiarism ( http://www.acm.org/publications/policies/plagiarism_policy) Submissions that violate these policies will be desk-rejected. Submission Site: Submissions will be accepted at https://sle18.hotcrp.com/. --------------------------- Reviewing Process --------------------------- All submitted papers will be reviewed by at least three members of the program committee. Research papers and tool papers will be evaluated concerning novelty, correctness, significance, readability, and alignment with the conference call. New ideas / vision papers will be evaluated primarily concerning novelty, significance, readability, and alignment with the conference call. For fairness reasons, all submitted papers must conform to the above instructions. Submissions that violate these instructions may be rejected without review, at the discretion of the PC chairs. --------------------------- Awards --------------------------- * Distinguished paper: Award for most notable paper, as determined by the PC chairs based on the recommendations of the programme committee. * Distinguished reviewer: Award for distinguished reviewer, as determined by the PC chairs. * Distinguished artifact: Award for the artifact most significantly exceeding expectations, as determined by the AEC chairs based on the recommendations of the artifact evaluation committee. --------------------------- Publication --------------------------- All accepted papers will be published in the ACM Digital Library. AUTHORS TAKE NOTE: The official publication date is the date the proceedings are made available in the ACM Digital Library. This date may be up to two weeks prior to the first day of the conference. The official publication date affects the deadline for any patent filings related to published work. --------------------------- Keynote --------------------------- We are very proud to announce that this yearâs SLE keynote will be given by Martin Rinard from the Massachusetts Institute of Technology. Martin Rinard is professor in the Department of Electrical Engineering and Computer Science at the Massachusetts Institute of Technology, and a member of the Computer Science and Artificial Intelligence Laboratory. His research focuses on software systems and related topics. The broad goal of his research is to obtain better software - making software more robust, resilient, and secure, improving the performance, verifying that the software satisfies important correctness, acceptability, reliability, or accuracy properties, or making systems (both software and hardware) easier to specify, build, maintain, or improve. More information on his research can be found at http://people.csail.mit.edu/rinard/. Details about his keynote at SLE will be announced soon on the conference Website. --------------------------- Program Committee --------------------------- Andrew Black, Portland State University, USA Anya Helene Bagge, University of Bergen, Norway Erwan Bousse, TU Wien, Austria Marco Brambilla, Politecnico di Milano, Italy Ruth Breu, University of Innsbruck, Austria Walter Cazzola, University of Milan, Italy Marsha Chechik, University of Toronto, Canada Tony Clark, Aston University, UK Juan de Lara, Universidad Autonoma de Madrid, Spain Thomas Degueule, CWI Amsterdam, Netherlands Juergen Dingel, Queen's University, Canada Tom Dinkelaker, Ericsson, Germany Sebastian Erdweg, Delft University of Technology, Netherlands Bernd Fischer, Stellenbosch University, South Africa Esther Guerra, Autonomous University of Madrid, Spain Daco Harkes, Delft University of Technology, Netherlands Robert Hirschfeld, University of Potsdam, Germany Michael Homer, Victoria University of Wellington, New Zealand Dimitris Kolovos, University of York, UK Ralf LÃ¤mmel, University of Koblenz-Landau, Germany Marjan Mernik, University of Maribor, Slovenia Gunter Mussbacher, McGill University, Canada James Noble, Victoria University of Wellington, New Zealand Bruno Oliveira, University of Hong Kong, China Christoph Reichenbach, Lund University, Sweden Jan Oliver Ringert, University of Leicester, UK Bernhard Rumpe, RWTH Aachen University, Germany Markus Schordan, Lawrence Livermore National Laboratory, USA Anthony Sloane, Macquarie University, Australia Emma SÃ¶derberg, Google, Denmark Mark van den Brand, TU Eindhoven, Netherlands Tijs van der Storm, CWI Amsterdam, Netherlands Eelco Visser, Delft University of Technology, Netherlands Eric Walkingshaw, Oregon State University, USA Andreas Wortmann, RWTH Aachen University, Germany Vadim Zaytsev, Rain Code, Belgium --------------------------- Artifact Evaluation Committee (tentative) --------------------------- Arvid Butting, RWTH Aachen University, Germany LuÃs Eduardo de Souza Amorim, Delft University of Technology, Netherlands Anna Maria Eilertsen, University of Bergen, Norway Abel GÃ³mez, Open University Catalonia, Spain Marcel Heinz, University of Koblenz-Landau, Germany Ludovico Iovino, GSSI, Italy Jesper Ãqvist, Lund University, Sweden --------------------------- Contact --------------------------- For additional information, clarification, or answers to questions, please contact the organizers by email: sle2018(a)googlegroups.com.

May 29, 2018

Re: [Pharo-users] Lazy vs eager initialization

by Ramon Leon

On 05/29/2018 08:49 AM, sergio ruiz wrote: > If a model has a list of things.. such as a user that can/may have lots > of pets, are there any real benefits to initializing the list of pets > lazily? Yes, there's a huge benefit to lazy initialization; it's more resilient to class changes in the face of deserilization of old class shapes. If you add new instance vars to a class, and then deserialize older version those instance variables will be nil. With lazy init, this is not a problem. Without lazy init, this is a null ref exception. These old versions could be from a cache of data from the previous version of the code. It's no fun to have to lose all cache data just because you push out a new version of the code. In of the face of persistence, i.e. serialized versions of your objects, lazy init is the way to go. -- Ramon Leon

May 29, 2018