March 2018 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Evaluate command handler broken because of AnObsoleteZnCrPortableWriteStream

by Sven Van Caekenberghe

> On 13 Mar 2018, at 10:06, Cyril Ferlicot <cyril.ferlicot(a)gmail.com> wrote: > > On Tue, Mar 13, 2018 at 7:23 AM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >> You probably loaded Zinc #stable which does not yet include ZnCrPortableWriteStream. Load #bleedingEdge instead. >> > Hi, > That's it. The project depends on Seaside which depends on Zinc > stable. It also explains why it happens to most of my projects since > most of them depend on Seaside. > >> This has bitten me as well a couple of times, I will promote a new stable Zinc later today. >> >> > It would be great. Thank you a lot! === Name: ConfigurationOfZincHTTPComponents-SvenVanCaekenberghe.108 Author: SvenVanCaekenberghe Time: 13 March 2018, 10:48:57.063827 am UUID: 85ac77e7-a923-0d00-b69e-eee909c39d78 Ancestors: ConfigurationOfZincHTTPComponents-SvenVanCaekenberghe.107 new stable 2.8.10 === Which includes the ZnCrPortableWriteStream addition and #asUrl as part of Zinc proper. Pharo 2.0 is no longer supported. > -- > Cyril Ferlicot > https://ferlicot.fr >

March 13, 2018

Re: [Pharo-dev] Using Metacello+git+tonel ?

by Thierry Goubier

Hi Cyril, Clement, 2018-03-13 10:19 GMT+01:00 Cyril Ferlicot <cyril.ferlicot(a)gmail.com>: > On Tue, Mar 13, 2018 at 10:06 AM, ClÃ©ment Bera <clement.bera(a)inria.fr> wrote: >> Hi, >> >> I am trying to write a Metacello configuration loading code from git in the >> tonel format. > > Hi ClÃ©ment. > > First of all: Currently it is possible to use Metacello to manage a > project on github/gitlab(Saas)/bitbucket. Not a raw git on a personal > server. It should be possible in the future, but not now. in Tonel that is. Metacello, any Git private server and GitFileTree has been supported for a few years now. > Second: The fact that you use tonel or filetree does not change the > way you will build your configuration. For both of them it will be a > BaselineOf. Yes. >> I checked all the configurations present in the default Pharo image looking >> for examples, but it seems most of them load code with Monticello. > > Check BaselineOf instead of ConfigurationOf > >> >> I found ConfigurationOfPharoMetacello which loads code from github, however, >> it loads code using the file tree format and not tonel format. >> >> Can someone point me to a configuration loading code from git using tonel so >> I can use it as an example? > > https://github.com/DuneSt/MaterialDesignLite/blob/migrate-sources-to-tonel/… > > This one is not with the tonel format but it will still work: > https://github.com/pharo-vcs/iceberg/tree/master/BaselineOfIceberg.package/… > >> >> Thanks >> >> -- >> ClÃ©ment BÃ©ra >> https://clementbera.github.io/ >> https://clementbera.wordpress.com/ >> BÃ¢timent B 40, avenue Halley 59650 Villeneuve d'Ascq > > > > -- > Cyril Ferlicot > https://ferlicot.fr >

March 13, 2018

Re: [Pharo-dev] Using Metacello+git+tonel ?

by Cyril Ferlicot

On Tue, Mar 13, 2018 at 10:06 AM, ClÃ©ment Bera <clement.bera(a)inria.fr> wrote: > Hi, > > I am trying to write a Metacello configuration loading code from git in the > tonel format. Hi ClÃ©ment. First of all: Currently it is possible to use Metacello to manage a project on github/gitlab(Saas)/bitbucket. Not a raw git on a personal server. It should be possible in the future, but not now. Second: The fact that you use tonel or filetree does not change the way you will build your configuration. For both of them it will be a BaselineOf. > > I checked all the configurations present in the default Pharo image looking > for examples, but it seems most of them load code with Monticello. Check BaselineOf instead of ConfigurationOf > > I found ConfigurationOfPharoMetacello which loads code from github, however, > it loads code using the file tree format and not tonel format. > > Can someone point me to a configuration loading code from git using tonel so > I can use it as an example? https://github.com/DuneSt/MaterialDesignLite/blob/migrate-sources-to-tonel/… This one is not with the tonel format but it will still work: https://github.com/pharo-vcs/iceberg/tree/master/BaselineOfIceberg.package/… > > Thanks > > -- > ClÃ©ment BÃ©ra > https://clementbera.github.io/ > https://clementbera.wordpress.com/ > BÃ¢timent B 40, avenue Halley 59650 Villeneuve d'Ascq -- Cyril Ferlicot https://ferlicot.fr

March 13, 2018

Re: [Pharo-dev] Evaluate command handler broken because of AnObsoleteZnCrPortableWriteStream

by Cyril Ferlicot

On Tue, Mar 13, 2018 at 7:23 AM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > You probably loaded Zinc #stable which does not yet include ZnCrPortableWriteStream. Load #bleedingEdge instead. > Hi, That's it. The project depends on Seaside which depends on Zinc stable. It also explains why it happens to most of my projects since most of them depend on Seaside. > This has bitten me as well a couple of times, I will promote a new stable Zinc later today. > > It would be great. Thank you a lot! -- Cyril Ferlicot https://ferlicot.fr

March 13, 2018

Using Metacello+git+tonel ?

by ClÃ©ment Bera

Hi, I am trying to write a Metacello configuration loading code from git in the tonel format. I checked all the configurations present in the default Pharo image looking for examples, but it seems most of them load code with Monticello. I found ConfigurationOfPharoMetacello which loads code from github, however, it loads code using the file tree format and not tonel format. Can someone point me to a configuration loading code from git using tonel so I can use it as an example? Thanks -- ClÃ©ment BÃ©ra https://clementbera.github.io/ https://clementbera.wordpress.com/ BÃ¢timent B 40, avenue Halley 59650 *Villeneuve d'Ascq*

March 13, 2018

Re: [Pharo-dev] [Pharo-users] Something is happening...

by Tudor Girba

This might be how super linear growth feels like once you pass the bending point. Doru > On Mar 13, 2018, at 8:27 AM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > Hi, > > There is something odd happeningâ¦ or better: There is *a lot* happening. > > Just one example: for the Newsletter, the original idea was to send out once a month a post with 3 things, some of them recycled (e.g. pointers to existing projects, re-use âsuccess storiesâ, things like that. > > Now already some months ago I had to add âand here are some other interesting announcements, blog posts, videosâ. > > But this month, the list of things for the newsletter TODO list contains over 60 entries. With the exception of maybe 5, these are just things that happened between sending the February newsletter and today. > > Newsletter March should be ready till this thursday, I hope, subscribe or read the oder ones here: http://newsletter.pharo.org > > Marcus -- www.tudorgirba.com www.feenk.com "Value is always contextual."

March 13, 2018

Re: [Pharo-dev] Evaluate command handler broken because of AnObsoleteZnCrPortableWriteStream

by Marcus Denker

> On 13 Mar 2018, at 08:40, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > > >> On 13 Mar 2018, at 08:17, Marcus Denker <marcus.denker(a)inria.fr> wrote: >> >> >> >>> On 13 Mar 2018, at 07:23, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >>> >>> You probably loaded Zinc #stable which does not yet include ZnCrPortableWriteStream. Load #bleedingEdge instead. >>> >>> This has bitten me as well a couple of times, I will promote a new stable Zinc later today. >>> >> we need to really see how to get synced in Pharo7. >> >> Marcus > > Yes, but the sync has to happen both ways: I first have to pick up all the changes that we done directly in Pharo 7 as not to overwrite anybody's work. That is tedious, delicate work. We need to find a way that porting is not neededâ¦ that the changes are done directly in Zinc. Marcus

March 13, 2018

Re: [Pharo-dev] Evaluate command handler broken because of AnObsoleteZnCrPortableWriteStream

by Marcus Denker

> On 13 Mar 2018, at 08:40, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > > >> On 13 Mar 2018, at 08:17, Marcus Denker <marcus.denker(a)inria.fr> wrote: >> >> >> >>> On 13 Mar 2018, at 07:23, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >>> >>> You probably loaded Zinc #stable which does not yet include ZnCrPortableWriteStream. Load #bleedingEdge instead. >>> >>> This has bitten me as well a couple of times, I will promote a new stable Zinc later today. >>> >> we need to really see how to get synced in Pharo7. >> >> Marcus > > Yes, but the sync has to happen both ways: I first have to pick up all the changes that we done directly in Pharo 7 as not to overwrite anybody's work. That is tedious, delicate work. Indeedâ¦ I just saw that one change I wanted to do since years (moving #asUrl to Zinc) has been done. (we had a whole package just for these extension methods). This was a change I wanted to do since years, but as Zinc is backward compatible, doing cleanups like this are very very difficultâ¦ and in the end, as a single change this is of course not importantâ¦ but the mistake is to therefore conclude to never do these tiny changesâ¦ as it is a number game: for 1 itâs not important, but if you manage to do 10000 or 20000 of these tiny changes, where the trivial later cleanups depend on the earlierâ¦ and are only trivial because the earlier were doneâ¦ Marcus

March 13, 2018

Re: [Pharo-dev] Evaluate command handler broken because of AnObsoleteZnCrPortableWriteStream

by Sven Van Caekenberghe

> On 13 Mar 2018, at 08:17, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > > >> On 13 Mar 2018, at 07:23, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >> >> You probably loaded Zinc #stable which does not yet include ZnCrPortableWriteStream. Load #bleedingEdge instead. >> >> This has bitten me as well a couple of times, I will promote a new stable Zinc later today. >> > we need to really see how to get synced in Pharo7. > > Marcus Yes, but the sync has to happen both ways: I first have to pick up all the changes that we done directly in Pharo 7 as not to overwrite anybody's work. That is tedious, delicate work.

March 13, 2018

Something is happening...

by Marcus Denker

Hi, There is something odd happeningâ¦ or better: There is *a lot* happening. Just one example: for the Newsletter, the original idea was to send out once a month a post with 3 things, some of them recycled (e.g. pointers to existing projects, re-use âsuccess storiesâ, things like that. Now already some months ago I had to add âand here are some other interesting announcements, blog posts, videosâ. But this month, the list of things for the newsletter TODO list contains over 60 entries. With the exception of maybe 5, these are just things that happened between sending the February newsletter and today. Newsletter March should be ready till this thursday, I hope, subscribe or read the oder ones here: http://newsletter.pharo.org <http://newsletter.pharo.org/> Marcus

March 13, 2018