- Pharo-users - lists.pharo.org

Looking for names for the booklet collection
by Stephane Ducasse March 4, 2018

March 4, 2018

Hi I would like to make a distinction between booklet on Pharo technologies (Smacc, Voyage, Scraping ...) and the booklets more oriented towards teaching something with pharo (building an interpreter, a reflective language...) Right now we have The Pharo Booklet Collection. And I'm looking for two names the Pharo academic booklet collection ? and the Pharo technology booklet collection ? Stef

4 3

Re: [Pharo-users] Ever growing image
by Stephane Ducasse March 4, 2018

March 4, 2018

I think that vendors did not go the bootstrap way because it is a lot more difficult to implement than a bunch of scripts to unload packages. On Sun, Mar 4, 2018 at 11:53 AM, Benoit St-Jean via Pharo-users <pharo-users(a)lists.pharo.org> wrote: > > > ---------- Forwarded message ---------- > From: Benoit St-Jean <bstjean(a)yahoo.com> > To: Any question about pharo is welcome <pharo-users(a)lists.pharo.org>, Esteban Lorenzano <estebanlm(a)gmail.com> > Cc: Hilaire <hilaire(a)drgeo.eu> > Bcc: > Date: Sun, 4 Mar 2018 10:53:04 +0000 (UTC) > Subject: Re: [Pharo-users] Ever growing image > Estaban, > > I understand the difference between the 2 approaches my point was just to mention that I guess there are some advantages to shrink the image (as compared to bootstrapping from a minimal image) since all major vendors used that approach (and are still using it). It's just that I was curious to know if anyone knows any paper/document/study comparing the 2 approaches or explaining in detail both of them. I googled for a few hours but couldn't find anything... > > > ----------------- > BenoÃ®t St-Jean > Yahoo! Messenger: bstjean > Twitter: @BenLeChialeux > Pinterest: benoitstjean > Instagram: Chef_Benito > IRC: lamneth > Blogue: endormitoire.wordpress.com > "A standpoint is an intellectual horizon of radius zero". (A. Einstein) > > > On Sunday, March 4, 2018, 5:13:30 AM EST, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > > > > On 3 Mar 2018, at 16:35, Benoit St-Jean via Pharo-users <pharo-users(a)lists.pharo.org> wrote: > > > From: Benoit St-Jean <bstjean(a)yahoo.com> > Subject: Re: [Pharo-users] Ever growing image > Date: 3 March 2018 at 16:35:19 CET > To: pharo-users(a)lists.pharo.org, Hilaire <hilaire(a)drgeo.eu> > Reply-To: Benoit St-Jean <bstjean(a)yahoo.com> > > > On a side note, being a long-time VW & VAST user, I've always felt the Image Stripper & Runtime Packager did a fairly good job at removing crap from the resulting image. > > I don't recall ready anything substantial comparing the Pharo way (bootstrapping from a minimal image and adding stuff) to the VW & VAST way (removing unreferenced stuff) but this would definitely be an interesting topic to read about. > > > > No idea if any âsubstantial" thing has been written (there are some phds around that may talk about), but main difference is very simple to explain: first approach (which was the same for Pharo before) is non-deterministic while the second is. Then, for purpose of repeatability of process (and testing, etc.) bootstrapping is better. > You would not know the amount of effort made to make this possible, it required at least 2 phd works and a considerable amount of engineering effort. > In our community, Pavel is the person that has the bigger experience on shrinking process images. I followed his work for years and I know the fragility of the process. Basically each new addition/removal was breaking it and needing dependency tracking, etc. Now is the opposite: you just add what you want, and you are sure the resulting image is a) healthy and b) identical when running. > > Esteban > > > ----------------- > BenoÃ®t St-Jean > Yahoo! Messenger: bstjean > Twitter: @BenLeChialeux > Pinterest: benoitstjean > Instagram: Chef_Benito > IRC: lamneth > Blogue: endormitoire.wordpress.com > "A standpoint is an intellectual horizon of radius zero". (A. Einstein) > > > On Saturday, March 3, 2018, 9:22:06 AM EST, Hilaire <hilaire(a)drgeo.eu> wrote: > > > Le 02/03/2018 Ã 22:52, Marcus Denker a Ã©crit : >> >> we should again do some analysis where space is goingâ¦ the Pharo7 download >> is now 38MB (the image, decompressed). > > Situation improved :) Remember P3 was just above 20 MB > > > >

1 0

[Issue Tracker] lots of "auto close" happening
by Marcus Denker March 3, 2018

March 3, 2018

Hello, As you might now, we automatically close issue tracker entries after 1 year of in-activity. Due to two factors (the job doing it not working since 1 month *and* now being 1 year after we started to sort issues for âhas to be fixed for pharo6 yes or noâ, we enter a period where *a lot* of issue get auto-closed. Everyone subscribed to the issue gets a mail and (of course!!) you should re-opne the issue tracker entry if the case still is relevant. Marcus

2 1

depending on a group of a BaselineOf
by Peter UhnÃ¡k March 3, 2018

March 3, 2018

Hi, I'm trying to define a dependency on a group of BaselineOf. specifically #core of github://pharo-graphics/Bloc/src. I've looked at this https://github.com/Metacello/metacello/blob/master/docs/GettingStartedWithG… which recommends using import:provides: baseline: spec <baseline> spec for: #common do: [ "Sample defines the group 'default'" spec baseline: 'Sample' with: [ spec repository: 'github://dalehenrich/Sample:master' ]. spec import: 'Sample' provides: #('default'). "OtherSample *also* defines the group 'default'" spec baseline: 'OtherSample' with: [ spec repository: 'github://dalehenrich/Sample:master' ]. spec import: 'OtherSample' provides: #('default'). "'default' can now be successfully resolved, even though both projects define the same name" spec package: 'OtherProject-Core with: [ spec requires: 'default' ] ]. However this code is confusing... both Sample & OtherSample provide `default`, so on what does `OtherProject-Core` actually depend? In the examples here https://github.com/Metacello/metacello/blob/master/docs/LockCommandReferenc… there are groups with the name of the project in them ('External Core' 'External Tests'), but this won't work if I don't control the project I am loading, plus it feels like a hackish workaround. Also, can it be unified with the way ConfigurationOf works? Thanks, Peter

3 3

[Isssue tracker] Name change: Manuscript
by Marcus Denker March 2, 2018

March 2, 2018

Hello, Many of you are already wondering why you get spammed by âmanuscript.comâ. The reason is that Fog Creek Software changed the name of FogBugz to âManuscriptâ. The old URLs are still valid, *but* they started to send all emails with the manuscript name instead some time ago. We have started to change all websites that mention the domain, too, but for sure there will be cases where the old name will be used for quite some timeâ¦ Marcus

1 0

[ANN] ba-st Web Stack new versions available
by Gabriel Cotelli March 1, 2018

March 1, 2018

Hi, We're happy to announce a new version of the Web Stack hosted at https://github.com/ba-st/. This is a multi-release announcement of the following related project versions: - Willow <https://github.com/ba-st/Willow> v6.0.0. Changes since latest announcement: - Added interaction on document load - Improved temporarily disabling command - Added identification support to unordered lists - Improved new location opening commands - Improved interaction fuctions to always include the event as a parameter - Improved asynchronic links to auto-configure a script doing preventDefault - Refactored the link support - Willow-Bootstrap <https://github.com/ba-st/Willow-Bootstrap> v6.0.0 - Updated Willow base support to v6.0.0 - Improved Split Button support to allow triggering actions on the main button only - Willow-JQueryUI <https://github.com/ba-st/Willow-JQueryUI> v5.0.0 - Updated Willow base support to v6.0.0 - Willow-SpinKit <https://github.com/ba-st/Willow-SpinKit> v3.0.0 - Updated Willow base support to v6.0.0 - Willow-Playground <https://github.com/ba-st/Willow-Playground/> v2.0.0 - Updated dependencies to the latest versions - RenoirSt <https://github.com/ba-st/RenoirSt> v4.0.0 - Removed Pharo 4 support - Updated dependencies SemanticUI <https://github.com/ba-st/Willow-SemanticUI> integration is still a work in progress. There's a new Materialize CSS <https://github.com/fortizpenaloza/Willow-Materialize> integration being worked on by Francisco Ortiz. Find a more detailed changelog and migration instructions on the release pages of each repository. Anyone interested in joining our ba-st projects <https://github.com/ba-st/> is welcomed, and you can also start following our new tech blog @ mercap <https://medium.com/mercap-tech-blog> for Smalltalk and Pharo related posts and experience reports. Regards, Gabriel Cotelli, Maxi Tabacman and all the contributors.

2 1

Re: [Pharo-users] Dynamically updating the inspector window
by Andy Burnett March 1, 2018

March 1, 2018

Andrei said >>> Are you in Pharo 6.1? There is a setting to enable automatic refresh in the inspector. I think it's called Step Refresh in the settings browser.Should be enabled by default in Pharo 7. Just now all presentations from the inspector have the automatic refresh implemented. <<<< Thatâs great! Thanks very much.

1 0

Ever growing image
by Hilaire March 1, 2018

March 1, 2018

Hi, Does the current 64bits VM suffers of the ever growing image syndrom? Thanks Hilaire -- Dr. Geo http://drgeo.eu

4 6

GTInspector globally configuring visible tags
by Peter UhnÃ¡k March 1, 2018

March 1, 2018

Hi, is it possible to globally configure GTInspector to show only certain tags (<gtInspectorTag: ...>) ? Thanks, Peter

1 0

[ANN] 900 pull requests closed for Pharo7!
by Marcus Denker March 1, 2018

March 1, 2018

Hi, March 11, we passed 800. Today (just now) we closed 900 full requests! https://github.com/pharo-project/pharo/pulls <https://github.com/pharo-project/pharo/pulls> Marcus

5 5