- Pharo-dev - lists.pharo.org

Image format not recognized

by Hilaire

Hi, Anyone knows why the former code snippet fail but the later deprecated one succeed? PNGReadWriterÂ formFromStream: ('/home/hilaire/Travaux/Developpement/DrGeoII/Dev-pharo7/drgeo/build/examples/wheel.png' asFileReference binaryReadStream). PNGReadWriter formFromStream: (FileStream readOnlyFileNamed:'/home/hilaire/Travaux/Developpement/DrGeoII/Dev-pharo7/drgeo/build/examples/wheel.png' ). Thanks Hilaire -- Dr. Geo http://drgeo.eu

May 31, 2018

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

by Francisco Ortiz PeÃ±aloza

Great work, thanks! On Tue, 29 May 2018 at 06:31 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 > > -- Sent from the past

May 31, 2018

Re: [Pharo-dev] Pharo 10th Anniversary

by Ben Coman

On 30 May 2018 at 16:10, Sven Van Caekenberghe <sven(a)stfx.eu> 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… cheers -ben

May 30, 2018

[Pharo 7.0-dev] Build #992: 22005-Breakpoints-do-not-stop-the-execution

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #992 was: FAILURE. The Pull Request #1463 was integrated: "22005-Breakpoints-do-not-stop-the-execution" Pull request url: https://github.com/pharo-project/pharo/pull/1463 Issue Url: https://pharo.fogbugz.com/f/cases/22005 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

May 30, 2018

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

by 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" <norbert(a)hartl.name> > An: "Pharo Dev" <pharo-dev(a)lists.pharo.org> > Cc: "Pharo users users" <pharo-users(a)lists.pharo.org> > 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 <sven(a)stfx.eu>: > > > > 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 > > > > > > > > > > > > >

May 30, 2018

Load Epicea project as external project?

by Martin Dias

Hi, some weeks ago I created a PR to integrate a new version of Epicea where the changes are: - packages are renamed EpiceaTest->Epicea-Test, etc. - code migrated from sthub->github - load it in BaselineOfIDE as external project as LibGit Here: https://github.com/pharo-project/pharo/pull/1366 Do you agree? is 3rd point problematic? I didn't understand last error. Regards, Martin

May 30, 2018

Re: [Pharo-dev] Pharo 10th Anniversary

by Norbert Hartl

Happy saphire deprecation day!!! Norbert > Am 30.05.2018 um 10:10 schrieb Sven Van Caekenberghe <sven(a)stfx.eu>: > > 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 > > > > >

May 30, 2018

[Pharo 7.0-dev] Build #991: 21999-New-taskbar-design-proposal

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #991 was: FAILURE. The Pull Request #1443 was integrated: "21999-New-taskbar-design-proposal" Pull request url: https://github.com/pharo-project/pharo/pull/1443 Issue Url: https://pharo.fogbugz.com/f/cases/21999 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

May 30, 2018

[Pharo 7.0-dev] Build #990: 21928-Remove-PluggableButtonMorph-option-to-use-gradient-since-its-not-used-and-style-it-decided-by-the-theme

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #990 was: SUCCESS. The Pull Request #1384 was integrated: "21928-Remove-PluggableButtonMorph-option-to-use-gradient-since-its-not-used-and-style-it-decided-by-the-theme" Pull request url: https://github.com/pharo-project/pharo/pull/1384 Issue Url: https://pharo.fogbugz.com/f/cases/21928 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

May 30, 2018

Re: [Pharo-dev] [ANN] VM for Pharo 6.1 updated

by Esteban Lorenzano

yes > On 30 May 2018, at 12:52, Norbert Hartl <norbert(a)hartl.name> wrote: > > Meaning we can get it via get.pharo.org <http://get.pharo.org/> ?? > > Norbert > >> Am 30.05.2018 um 11:54 schrieb Esteban Lorenzano <estebanlm(a)gmail.com <mailto:estebanlm@gmail.com>>: >> >> Hello, >> >> I backported stable VM from Pharo 7 to Pharo 6.1. >> It should fix some issues (not listed, because I really donât know them). >> >> Let me know if something is wrong. >> >> Cheers, >> Esteban >

May 30, 2018