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

[Francisco Ortiz Peñaloza]

Great work, thanks!

On Tue, 29 May 2018 at 06:31 Guillermo Polito 
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
>
> --
Sent from the past

Re: [Pharo-users] [Pharo-dev] Pharo 10th Anniversary

[Ben Coman]

On 30 May 2018 at 16:10, Sven Van Caekenberghe  wrote:

> Hi,
>
> This short post by Stéphane Ducasse is worth sharing:
>
>   https://pharoweekly.wordpress.com/2018/05/29/pharo-got-10-years/
>
> Congratulation !
>


Happy birthday Pharo.

Good software takes 10 years...
https://www.joelonsoftware.com/2001/07/21/good-software-takes-ten-years-get-used-to-it/


cheers -ben

Re: [Pharo-users] ESUG 2018

[Marten Feldtmann]

Am 30.05.2018 um 18:19 schrieb Norbert Hartl:
> https://esug.github.io/2018-Conference/conf2018.html
> 
> says the registration is open. Did I miss an announcement. It is quite
> important, no?
> 
> Norbert
> 
Its not open ... I tried to register

-- 
Marten Feldtmann

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

[Sean P. DeNigris]

EstebanLM wrote
>> - How do I check the version of Iceberg
> 
> not much way this days, since iceberg is installed outside iceberg.

How about putting this info in the about text for the tool's GUI?



-
Cheers,
Sean
--
Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Re: [Pharo-users] Pharo 10th Anniversary

[Offray Vladimir Luna Cárdenas]

Thanks to the Pharo communities for all the creativity, tools, momentum,
laugh, flame war, collaboration and the long etcetera that make us.

Cheers to the next 10 years!

Offray


On 30/05/18 03:10, Sven Van Caekenberghe wrote:
> Hi,
>
> This short post by Stéphane Ducasse is worth sharing:
>
>   https://pharoweekly.wordpress.com/2018/05/29/pharo-got-10-years/
>
> Congratulation !
>
> Sven
>
> --
> Sven Van Caekenberghe
> Proudly supporting Pharo
> http://pharo.org
> http://association.pharo.org
> http://consortium.pharo.org
>
>
>
>
>
>

[Pharo-users] ESUG 2018

[Norbert Hartl]

https://esug.github.io/2018-Conference/conf2018.html 


says the registration is open. Did I miss an announcement. It is quite 
important, no?

Norbert

Re: [Pharo-users] Pharo 10th Anniversary

[b w]

I get zero ads under Brave and Chrome, and two fairly modest ads on IE,
FWIW.

On Wed, May 30, 2018 at 1:45 AM, john pfersich  wrote:

> I don’t know what others see when they go to
> https://pharoweekly.wordpress.com/, but I encountered 7 ads on one page.
> Talk about off putting. A wordpress site without ads costs $3 a month. At
> least it would put forth a better image.
>
> //
> Encrypted email at jgpfers...@protonmail.com
> Web: www.objectnets.net and www.objectnets.org
>
> On May 30, 2018, at 01:10, Sven Van Caekenberghe  wrote:
>
> Hi,
>
> This short post by Stéphane Ducasse is worth sharing:
>
>  https://pharoweekly.wordpress.com/2018/05/29/pharo-got-10-years/
>
> Congratulation !
>
> Sven
>
> --
> Sven Van Caekenberghe
> Proudly supporting Pharo
> http://pharo.org
> http://association.pharo.org
> http://consortium.pharo.org
>
>
>
>
>
>

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

[Andrei Stebakov]

Hi Esteban

The reason I was asking how to update from 0.7.? is because if I take the
same script and execute it after plugging in the 1.0.1 version my Pharo
image freezes. I can try from a fresh Pharo 6.1 image and see if I get the
same problem.

On Wed, May 30, 2018, 01:52 Esteban Lorenzano  wrote:

> hi,
>
> On 30 May 2018, at 01:59, Andrei Stebakov  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) 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 <
> guillermopol...@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
>>
>>
>
>

Re: [Pharo-users] [Pharo-dev] Pharo 10th Anniversary

[Torsten Bergmann]

Yes - we should be happy to have left behind ugly "saphire". It would have 
never 
been our future - just look at it now. Not much progress till today - 
especially 
compared to Pharo. ;)

And happy anniversary Pharo :)

Each day another little step - I'm impatient to see where Pharo will be in 2028 
and especially in 2058 ...

Bye
T.

> Gesendet: Mittwoch, 30. Mai 2018 um 15:14 Uhr
> Von: "Norbert Hartl" 
> An: "Pharo Dev" 
> Cc: "Pharo users users" 
> Betreff: Re: [Pharo-users] [Pharo-dev] Pharo 10th Anniversary
>
> Happy saphire deprecation day!!!
> 
> Norbert
> 
> > Am 30.05.2018 um 10:10 schrieb Sven Van Caekenberghe :
> > 
> > Hi,
> > 
> > This short post by Stéphane Ducasse is worth sharing:
> > 
> >  https://pharoweekly.wordpress.com/2018/05/29/pharo-got-10-years/
> > 
> > Congratulation !
> > 
> > Sven
> > 
> > --
> > Sven Van Caekenberghe
> > Proudly supporting Pharo
> > http://pharo.org
> > http://association.pharo.org
> > http://consortium.pharo.org
> > 
> > 
> > 
> > 
> > 
> 
> 
>

Re: [Pharo-users] Is there a compatibility package for migrating Spec application from Pharo 6.1 to Pharo 7 ?

[Esteban Lorenzano]

https://github.com/pharo-contributions/Spec70Compatibility 


> On 30 May 2018, at 15:48, Peter Uhnák  wrote:
> 
> ComposableModel withAllSubclasses do: [ :cls | cls subclass: ((cls name 
> withoutSuffix: 'Model'), 'Presenter') asSymbol ] + move all the classes in 
> Undeclared package.
> 
> Haven't run it... but it should work more or less.
> 
> A backport might not be a bad idea.
> 
> Peter
> 
> On Wed, May 30, 2018 at 2:44 PM, Julien  > wrote:
> Hello,
> 
> In Pharo 7, Spec’s *Model classes were renamed following the pattern 
> *Presenter, which is better.
> 
> The original classes names (*Model) are still usable but their usage is 
> deprecated in Pharo 7.
> 
> I wonder if someone did a package for Pharo 6.1 that does the opposite: 
> provide *Presenter classes in
> Pharo 6.1 to allow to prepare applications for the migration to Pharo 7 *but* 
> allowing to keep them compatible
> with Pharo 6.1 until Pharo 7 is released (and eventually after...)? The 
> implementation would be quite easy :
> create an empty subclass using the pattern *Presenter for the name for each 
> *Model class of spec.
> 
> Thanks in advance,
> 
> Julien
> 
> ---
> Julien Delplanque
> Doctorant à l’Université de Lille
> http://juliendelplanque.be/phd.html 
> Equipe Rmod, Inria
> Bâtiment B 40, Avenue Halley 59650 
> 
>  Villeneuve 
> 
>  d'Ascq 
> 
> Numéro de téléphone: +333 59 35 86 40
> 
> 

Re: [Pharo-users] Is there a compatibility package for migrating Spec application from Pharo 6.1 to Pharo 7 ?

[Peter Uhnák]

ComposableModel withAllSubclasses do: [ :cls | cls subclass: ((cls name
withoutSuffix: 'Model'), 'Presenter') asSymbol ] + move all the classes in
Undeclared package.

Haven't run it... but it should work more or less.

A backport might not be a bad idea.

Peter

On Wed, May 30, 2018 at 2:44 PM, Julien  wrote:

> Hello,
>
> In Pharo 7, Spec’s *Model classes were renamed following the pattern
> *Presenter, which is better.
>
> The original classes names (*Model) are still usable but their usage is
> deprecated in Pharo 7.
>
> I wonder if someone did a package for Pharo 6.1 that does the opposite:
> provide *Presenter classes in
> Pharo 6.1 to allow to prepare applications for the migration to Pharo 7
> *but* allowing to keep them compatible
> with Pharo 6.1 until Pharo 7 is released (and eventually after...)? The
> implementation would be quite easy :
> create an empty subclass using the pattern *Presenter for the name for
> each *Model class of spec.
>
> Thanks in advance,
>
> Julien
>
> ---
> Julien Delplanque
> Doctorant à l’Université de Lille
> http://juliendelplanque.be/phd.html
> Equipe Rmod, Inria
> Bâtiment B 40, Avenue Halley 59650
> 
>  Villeneuve
> 
>  d'Ascq
> 
> Numéro de téléphone: +333 59 35 86 40
>
>

Re: [Pharo-users] [Pharo-dev] Pharo 10th Anniversary

[Norbert Hartl]

Happy saphire deprecation day!!!

Norbert

> Am 30.05.2018 um 10:10 schrieb Sven Van Caekenberghe :
> 
> Hi,
> 
> This short post by Stéphane Ducasse is worth sharing:
> 
>  https://pharoweekly.wordpress.com/2018/05/29/pharo-got-10-years/
> 
> Congratulation !
> 
> Sven
> 
> --
> Sven Van Caekenberghe
> Proudly supporting Pharo
> http://pharo.org
> http://association.pharo.org
> http://consortium.pharo.org
> 
> 
> 
> 
> 

Re: [Pharo-users] [Pharo-dev] Pharo 10th Anniversary

[Tudor Girba]

+1

Happy anniversary! :)

Doru


> On May 30, 2018, at 10:10 AM, Sven Van Caekenberghe  wrote:
> 
> Hi,
> 
> This short post by Stéphane Ducasse is worth sharing:
> 
>  https://pharoweekly.wordpress.com/2018/05/29/pharo-got-10-years/
> 
> Congratulation !
> 
> Sven
> 
> --
> Sven Van Caekenberghe
> Proudly supporting Pharo
> http://pharo.org
> http://association.pharo.org
> http://consortium.pharo.org
> 
> 
> 
> 
> 

--
www.tudorgirba.com
www.feenk.com

"Every thing should have the right to be different."

Re: [Pharo-users] Pharo 10th Anniversary

[john pfersich]

I don’t know what others see when they go to 
https://pharoweekly.wordpress.com/, but I encountered 7 ads on one page. Talk 
about off putting. A wordpress site without ads costs $3 a month. At least it 
would put forth a better image. 

//
Encrypted email at jgpfers...@protonmail.com
Web: www.objectnets.net and www.objectnets.org

> On May 30, 2018, at 01:10, Sven Van Caekenberghe  wrote:
> 
> Hi,
> 
> This short post by Stéphane Ducasse is worth sharing:
> 
>  https://pharoweekly.wordpress.com/2018/05/29/pharo-got-10-years/
> 
> Congratulation !
> 
> Sven
> 
> --
> Sven Van Caekenberghe
> Proudly supporting Pharo
> http://pharo.org
> http://association.pharo.org
> http://consortium.pharo.org
> 
> 
> 
> 
> 

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

[teso...@gmail.com]

Thanks a lot!!

On Wed, May 30, 2018 at 10:42 AM, Esteban Lorenzano 
wrote:

> yep… I will backport VM to 6.1 now.
>
> cheers,
> Esteban
>
>
> On 30 May 2018, at 09:58, teso...@gmail.com wrote:
>
> I am talking about the long paths issue.
>
> On Wed, May 30, 2018 at 9:57 AM, teso...@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 <
>> guillermopol...@gmail.com> wrote:
>>
>>> Hi!
>>>
>>> On Wed, May 30, 2018 at 7:51 AM, Esteban Lorenzano 
>>> wrote:
>>>
 hi,

 On 30 May 2018, at 01:59, Andrei Stebakov  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 <
 guillermopol...@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 

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

[Esteban Lorenzano]

yep… I will backport VM to 6.1 now.

cheers, 
Esteban

> On 30 May 2018, at 09:58, teso...@gmail.com wrote:
> 
> I am talking about the long paths issue.
> 
> On Wed, May 30, 2018 at 9:57 AM, teso...@gmail.com  
> mailto:teso...@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  > wrote:
> Hi!
> 
> On Wed, May 30, 2018 at 7:51 AM, Esteban Lorenzano  > wrote:
> hi,
> 
>> On 30 May 2018, at 01:59, Andrei Stebakov > > 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/acd66a0b5cc22ffe1317434f9bc41b809b70571c
>  
> 
>  
> 
> Esteban
> 
>> 
>> Thanks!
>> Andrei
>> 
>> On Tue, May 29, 2018 at 5:30 AM, Guillermo Polito > > 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 

[Pharo-users] Pharo 10th Anniversary

[Sven Van Caekenberghe]

Hi,

This short post by Stéphane Ducasse is worth sharing:

  https://pharoweekly.wordpress.com/2018/05/29/pharo-got-10-years/

Congratulation !

Sven

--
Sven Van Caekenberghe
Proudly supporting Pharo
http://pharo.org
http://association.pharo.org
http://consortium.pharo.org

Re: [Pharo-users] Lazy vs eager initialization

[Norbert Hartl]

+1

Norbert

> Am 30.05.2018 um 05:20 schrieb 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  > 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 

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

[teso...@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  wrote:

> Hi!
>
> On Wed, May 30, 2018 at 7:51 AM, Esteban Lorenzano 
> wrote:
>
>> hi,
>>
>> On 30 May 2018, at 01:59, Andrei Stebakov  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 <
>> guillermopol...@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
> *
>
>
> *Web:* *http://guillep.github.io* 
>
> *Phone: *+33 06 52 70 66 13
>



-- 
Pablo Tesone.

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

[teso...@gmail.com]

I am talking about the long paths issue.

On Wed, May 30, 2018 at 9:57 AM, teso...@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 <
> guillermopol...@gmail.com> wrote:
>
>> Hi!
>>
>> On Wed, May 30, 2018 at 7:51 AM, Esteban Lorenzano 
>> wrote:
>>
>>> hi,
>>>
>>> On 30 May 2018, at 01:59, Andrei Stebakov  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 <
>>> guillermopol...@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 

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

[Guillermo Polito]

Hi!

On Wed, May 30, 2018 at 7:51 AM, Esteban Lorenzano 
wrote:

> hi,
>
> On 30 May 2018, at 01:59, Andrei Stebakov  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/acd66a0b5cc22ffe1317434f9bc41b809b70571c


>
> Esteban
>
>
> Thanks!
> Andrei
>
> On Tue, May 29, 2018 at 5:30 AM, Guillermo Polito <
> guillermopol...@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
*


*Web:* *http://guillep.github.io* 

*Phone: *+33 06 52 70 66 13