- Pharo-users - lists.pharo.org

Re: [Pharo-users] Minimizing an Application

by Esteban A. Maringolo

VAST provided such image deployment tool, where you could save the deployment instructions, as whether to include/exclude certain packages, classes, methods, etc. It was great, although it wasn't "easy" to work with. Dolphin Smalltalk has an Image Stripper, that does something like that, but by "removing" stuff from a copy of the image, it worked really well in practice and was super easy to use. Also, you can decide what "SessionManager" will be used in the deployed image, for a normal development image, it is DevelopmentSessionManger, but for a web app it could be a CommandLineSessionManager, or if you have a GUI desktop app, it could be your own session manager class. But what I liked the most was VisualSmalltalk's SLL (Smalltalk's Linked Library), where you could "link" your application with true modules, that were binary. You explicitly specify its contents (classes, methods, pools, etc.) when building (compiling), and could be replaced without having to redeploy everything. It could lead to some dependency hell if done wrong, but not more than any other module solution. And they were very compact. In my Pharo deployments, since they are web applications, I always deployed the whole image in the server, built from a vanilla one, but without stripping anything. Regards, Esteban A. Maringolo 2017-08-22 0:22 GMT-03:00 Richard Sargent <richard.sargent(a)gemtalksystems.com>: > VA Smalltalk doesn't strip an image; it builds a new image based on > application dependencies. With VA's packaging functionality, you are more > likely to get a packaging error that reports you are trying to use something > that isn't reachable according to the defined dependencies. > > I admit that except for the first few years, most of my early Smalltalk > experience involved ENVY and VA/VisualAge Smalltalk. Still, I prefer it's > practice of building an image based on what you have told it to include. > > On Aug 21, 2017 15:22, "Tim Mackinnon" <tim(a)testit.works> wrote: >> >> There has been a lot of great work on this front on the Pharo side from >> the "team" and PharoLambda has made use of it (although it's a tiny >> project). >> >> My footprint is ~22mb including vm & image. And leaving out sources. >> >> The ./scripts directory has the example of how to do it, along side the >> .gitlab-ci.yml file. >> >> Unlike the commercial distributions (and this may have changed recently), >> there is a minimal image you can have download, which has enough to >> bootstrap loading your project via metacello. There are no browser tools or >> morphic things in the starting image I have chosen. >> >> You can potentially get smaller - but it's a decent result. The only bit I >> added was to remove testcases (optional), and clear down metacello. >> >> It's probably worthy of a blog post - but honestly the running example is >> pretty straight forward. >> >> The commercial tools all have a decent "strip dead code" tool, that does a >> similar thing in reverse - which is equally a decent way of approaching the >> problem and can lead to even tinier results. >> >> Tim >> >> Sent from my iPhone >> >> On 21 Aug 2017, at 21:25, horrido <horrido.hobbies(a)gmail.com> wrote: >> >> I received this comment on Facebook: >> >> Smalltalk is a fantastic language and its development environment can't be >> beat... But the documentation for the many open source implementations is >> contradictory or confusing or missing. I can't speak for the commercial >> versions. Without an experienced mentor it is not possible to create a >> complex app. And even when you have done so, *I know no way to strip out >> the >> unused part of the image as well as the embedded source code*. >> ----- >> >> This issue of stripping out unused code seems to recur a lot. And truth be >> told, I've never seen a clear explanation of how to do this. Can someone >> provide clear direction? Is this documented anywhere? I'd like to use the >> information in future to assuage other people's concerns. >> >> Thanks. >> >> >> >> -- >> View this message in context: >> http://forum.world.st/Minimizing-an-Application-tp4963262.html >> Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. >> >

Aug. 22, 2017

Re: [Pharo-users] [Pharo-dev] TechTalk Dates for the rest of 2017

by Marcus Denker

> On 22 Aug 2017, at 13:02, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > >>> I'm not sure Pharo tech talk is the good place but would love to see such a presentation. >>> >> Why not? I am sure Alex will have some code in there.. " programming, from scratch, a small artificial intelligenceâ >> if done with Pharo would be a very nice thing todo for the tech talk. > > Yes, that is the plan. It could be a very practical lecture, with a lot of coding (but not many lines of code). > I added it for October 17th: https://association.pharo.org/event-2642664 Marcus

Aug. 22, 2017

Re: [Pharo-users] [Pharo-dev] [ANN] Pharo 6.1 (summer) released!

by Marcus Denker

> On 18 Aug 2017, at 09:56, Marcus Denker <marcus.denker(a)inria.fr> wrote: > >> >> What I think would have been good is to list all the updates that where done between >> releasing 6.0 and 6.1 *as part of the changelog* of 6.1 (even though they were already >> in the image that you got a minute before Pharo6.1 was released, as they where released as >> hot fixes before). >> > > The changelog of things done between releasing 6.0 and the release of 6.1: > I added a link to the complete changeling to http://pharo.org/news/pharo6.1-released <http://pharo.org/news/pharo6.1-released> Marcus

Aug. 22, 2017

Re: [Pharo-users] [Pillar] Installed the Pillar document preparation system into 6.1, how do I start using it?

by Stephane Ducasse

Yes we need input (but most importantly time). I will allocate time because Pillar is important for me. On Fri, Aug 18, 2017 at 10:18 PM, Cyril Ferlicot <cyril.ferlicot(a)gmail.com> wrote: > > On ven. 18 aoÃ»t 2017 at 22:09, H. Hirzel <hannes.hirzel(a)gmail.com> wrote: >> >> Exactly. >> >> Section 7 of >> >> https://ci.inria.fr/pharo-contribution/job/EnterprisePharoBook/lastSuccessf… >> >> has an example >> >> >> | wiki | >> wiki := '!My Document'. >> PRPillarParser parse: wiki >> >> >> Or >> >> PRPillarParser parse: (FileSystem workingDirectory / 'foo.pillar') >> readStream >> >> >> and then >> >> >> PRHTMLWriter write: document >> >> >> This put together gives >> >> PRHTMLWriter write: ( >> PRPillarParser parse: (FileSystem workingDirectory / >> 'welcome.pillar') >> ) >> >> >> If I inspect the result of this expression I get the HTML string. >> >> Thank you Cyril. This is what I was looking for. >> >> --Hannes > > > > Happy to see it still works :) > > I know there was work on Pillar after I wrote this. Maybe there is some > functionalities that will need more than those simple examples. By I am not > sure and I know that Stephane want to simplify it further. > -- > Cyril Ferlicot > https://ferlicot.fr > > http://www.synectique.eu > 2 rue Jacques PrÃ©vert 01, > 59650 Villeneuve d'ascq France

Aug. 22, 2017

Re: [Pharo-users] YAML parser (2017)

by Stephane Ducasse

Hi Hannes you should report this to doru. Stef On Sat, Aug 19, 2017 at 8:36 PM, H. Hirzel <hannes.hirzel(a)gmail.com> wrote: > On 8/19/17, Peter Uhnak <i.uhnak(a)gmail.com> wrote: >> On Sat, Aug 19, 2017 at 02:45:28PM +0200, H. Hirzel wrote: >>> Peter, thanks for the confirmation that in your installation of the >>> PetitYAML grammar all tests are green. >>> >>> I wonder how you did it. >> >> As I've said, you need to update PetitParser; if there's no appropriate >> catalog entry, then ConfigurationOfPetitParser loadBleeding edge, or >> manually via Monticello Browser (the same way you loaded PetitYAML). >> >> Peter > > Thanks, loading ConfigurationOfPetitParser-TudorGirba.80 through the > Monticello Browser (not the catalog) into Pharo 6 and then > > ConfigurationOfPetitParser load > > did the job. Now all PetitYAML grammar tests are grenen. > > --Hannes

Aug. 22, 2017

Re: [Pharo-users] Minimizing an Application

by Stephane Ducasse

Hi Richard, If you make sure that you have a seed and maps of dependencies for all the packages you use then you can build daily your project with a integration farm. I worked with Envy and I was used to load in one click a working or deployed image. And it worked. Then working on the granularity of your packages and their dependencies you can control what you deploy. We are going in that direction for Pharo because we believe it is the way for most projects. So in the future we will get PharoSeed and Pharo as two images we maintain and deploy but people will build their own based on PharoSeed. Now guillermo is his PhD developed also a shrinking system that can produce hyper specialised image (and quite small we got up to 11k image for 2 + 3). We could produce a WebCounter Seaside app in 500 k. Now such scenarios are more for advanced and specific use. Stef On Tue, Aug 22, 2017 at 12:46 PM, horrido <horrido.hobbies(a)gmail.com> wrote: > If you start with a minimal imaqe, it's not obvious to me how you'd add a > missing class and pull in all of its dependencies (which can be voluminous). > And for a large application, there could be many, many missing classes. This > sounds rather arduous. > > > Tim Mackinnon wrote >> There has been a lot of great work on this front on the Pharo side from >> the "team" and PharoLambda has made use of it (although it's a tiny >> project). >> >> My footprint is ~22mb including vm & image. And leaving out sources. >> >> The ./scripts directory has the example of how to do it, along side the >> .gitlab-ci.yml file. >> >> Unlike the commercial distributions (and this may have changed recently), >> there is a minimal image you can have download, which has enough to >> bootstrap loading your project via metacello. There are no browser tools >> or morphic things in the starting image I have chosen. >> >> You can potentially get smaller - but it's a decent result. The only bit I >> added was to remove testcases (optional), and clear down metacello. >> >> It's probably worthy of a blog post - but honestly the running example is >> pretty straight forward. >> >> The commercial tools all have a decent "strip dead code" tool, that does a >> similar thing in reverse - which is equally a decent way of approaching >> the problem and can lead to even tinier results. >> >> Tim >> >> Sent from my iPhone >> >>> On 21 Aug 2017, at 21:25, horrido < > >> horrido.hobbies@ > >> > wrote: >>> >>> I received this comment on Facebook: >>> >>> Smalltalk is a fantastic language and its development environment can't >>> be >>> beat... But the documentation for the many open source implementations is >>> contradictory or confusing or missing. I can't speak for the commercial >>> versions. Without an experienced mentor it is not possible to create a >>> complex app. And even when you have done so, *I know no way to strip out >>> the >>> unused part of the image as well as the embedded source code*. >>> ----- >>> >>> This issue of stripping out unused code seems to recur a lot. And truth >>> be >>> told, I've never seen a clear explanation of how to do this. Can someone >>> provide clear direction? Is this documented anywhere? I'd like to use the >>> information in future to assuage other people's concerns. >>> >>> Thanks. >>> >>> >>> >>> -- >>> View this message in context: >>> http://forum.world.st/Minimizing-an-Application-tp4963262.html >>> Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. >>> > > > > > > -- > View this message in context: http://forum.world.st/Minimizing-an-Application-tp4963262p4963349.html > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. >

Aug. 22, 2017

Re: [Pharo-users] Where do I find a Pillar syntax summary?

by Stephane Ducasse

Cyril I imagine that you refer to link ref with *@...* Yes we should probably produce a stylesheet. Now I'm busy finishing the new lecture. Since we could not reproduce the Pillar image for Pharo 40 (because of a bug in metacello) luc pushed the Pharo mooc to Pharo 50. Luc created a makefile producer from the pillar.conf and friday we will do a day with damien on having the new makefile on all the booklets + travis. So that I can have one way to do things for all the project. I want to deprecate all the postBuild.sh creation in all the projects. But lecture first Stef On Tue, Aug 22, 2017 at 12:56 PM, Cyril Ferlicot D. <cyril.ferlicot(a)gmail.com> wrote: > Le 22/08/2017 Ã 09:25, H. Hirzel a Ã©crit : >> Hello >> >> There is a tutorial for the Pillar document writing system [1]. The >> Pharo 6 catalog entry shows that the Pillar syntax goes back to the >> Pier CMS syntax of Lukas Renggli [2]. >> >> There is a syntax summary for the Pier CMS >> >> http://www.piercms.com/doc/syntax [3] >> >> I assume that most this still applies for Pillar? >> But I can imagine that there have here been updates / changes / extensions. >> >> I am looking for a Pillar syntax summary ("cheat sheet"). >> Is this available somewhere? >> >> Kind regards >> >> Hannes >> >> > > Hi! > > For everything before 2015 there is this one: > > https://www.cheatography.com/benjaminvanryseghem/cheat-sheets/pillar/ > > But everything added after 2015 there is none :( Also there was a change > of syntax on the links but I don't remember which one. The correct > syntax should be in the PDF you referenced in [1]. > > I'll add an issue to the Pillar repo to create such a sheet but I will > not have the time to do it. (At least not now) > >> >> >> [1] https://ci.inria.fr/pharo-contribution/job/EnterprisePharoBook/lastSuccessf… >> >> [2] Pharo 6.1 catalog entry for Pillar >> >> Pillar is a wiki-like syntax, its document model, a parser for it, and >> a set of exporters (e.g., HTML, LaTeX, Markdown...). Pillar is >> primarily used as the wiki syntax behind the *Pier >> CMS>http://piercms.com*. Pillar is also being used to write books: >> e.g., *the Enterprise Pharo book>http://books.pharo.org/*. >> >> The original creator of Pillar (formerly known as ''the syntax behind >> the Pier CMS'') is Lukas Renggli. Nevertheless, *Damien >> Cassou>damien.cassou(a)inria.fr* is now the maintainer. The website is >> at *http://www.smalltalkhub.com/#!/~Pier/Pillar*. Issues should be >> reported to *https://github.com/pillar-markup/pillar/issues* >> >> >> [3] http://wiki.squeak.org/squeak/3700 has some information about Pier. >> It refers to a Smallwiki mailing list which is active. >> >> https://www.list.inf.unibe.ch/pipermail/smallwiki/ >> >> e.g. https://www.list.inf.unibe.ch/pipermail/smallwiki/2016-November/008051.html >> with an announcment 'Pier3 with latest Pillar' >> > > > -- > Cyril Ferlicot > https://ferlicot.fr > > http://www.synectique.eu > 2 rue Jacques PrÃ©vert 01, > 59650 Villeneuve d'ascq France >

Aug. 22, 2017

Re: [Pharo-users] [Pharo-dev] TechTalk Dates for the rest of 2017

by Alexandre Bergel

>> I'm not sure Pharo tech talk is the good place but would love to see such a presentation. >> > Why not? I am sure Alex will have some code in there.. " programming, from scratch, a small artificial intelligenceâ > if done with Pharo would be a very nice thing todo for the tech talk. Yes, that is the plan. It could be a very practical lecture, with a lot of coding (but not many lines of code). Alexandre > >> Maybe you can do a Google or Twitch live video about that ? >> > Yes, that at one of the pre-defined tech talk dates. > > Marcus > >

Aug. 22, 2017

Re: [Pharo-users] Where do I find a Pillar syntax summary?

by Cyril Ferlicot D.

Le 22/08/2017 Ã 09:25, H. Hirzel a Ã©crit : > Hello > > There is a tutorial for the Pillar document writing system [1]. The > Pharo 6 catalog entry shows that the Pillar syntax goes back to the > Pier CMS syntax of Lukas Renggli [2]. > > There is a syntax summary for the Pier CMS > > http://www.piercms.com/doc/syntax [3] > > I assume that most this still applies for Pillar? > But I can imagine that there have here been updates / changes / extensions. > > I am looking for a Pillar syntax summary ("cheat sheet"). > Is this available somewhere? > > Kind regards > > Hannes > > Hi! For everything before 2015 there is this one: https://www.cheatography.com/benjaminvanryseghem/cheat-sheets/pillar/ But everything added after 2015 there is none :( Also there was a change of syntax on the links but I don't remember which one. The correct syntax should be in the PDF you referenced in [1]. I'll add an issue to the Pillar repo to create such a sheet but I will not have the time to do it. (At least not now) > > > [1] https://ci.inria.fr/pharo-contribution/job/EnterprisePharoBook/lastSuccessf… > > [2] Pharo 6.1 catalog entry for Pillar > > Pillar is a wiki-like syntax, its document model, a parser for it, and > a set of exporters (e.g., HTML, LaTeX, Markdown...). Pillar is > primarily used as the wiki syntax behind the *Pier > CMS>http://piercms.com*. Pillar is also being used to write books: > e.g., *the Enterprise Pharo book>http://books.pharo.org/*. > > The original creator of Pillar (formerly known as ''the syntax behind > the Pier CMS'') is Lukas Renggli. Nevertheless, *Damien > Cassou>damien.cassou(a)inria.fr* is now the maintainer. The website is > at *http://www.smalltalkhub.com/#!/~Pier/Pillar*. Issues should be > reported to *https://github.com/pillar-markup/pillar/issues* > > > [3] http://wiki.squeak.org/squeak/3700 has some information about Pier. > It refers to a Smallwiki mailing list which is active. > > https://www.list.inf.unibe.ch/pipermail/smallwiki/ > > e.g. https://www.list.inf.unibe.ch/pipermail/smallwiki/2016-November/008051.html > with an announcment 'Pier3 with latest Pillar' > -- Cyril Ferlicot https://ferlicot.fr http://www.synectique.eu 2 rue Jacques PrÃ©vert 01, 59650 Villeneuve d'ascq France

Aug. 22, 2017

Re: [Pharo-users] Minimizing an Application

by horrido

If you start with a minimal imaqe, it's not obvious to me how you'd add a missing class and pull in all of its dependencies (which can be voluminous). And for a large application, there could be many, many missing classes. This sounds rather arduous. Tim Mackinnon wrote > There has been a lot of great work on this front on the Pharo side from > the "team" and PharoLambda has made use of it (although it's a tiny > project). > > My footprint is ~22mb including vm & image. And leaving out sources. > > The ./scripts directory has the example of how to do it, along side the > .gitlab-ci.yml file. > > Unlike the commercial distributions (and this may have changed recently), > there is a minimal image you can have download, which has enough to > bootstrap loading your project via metacello. There are no browser tools > or morphic things in the starting image I have chosen. > > You can potentially get smaller - but it's a decent result. The only bit I > added was to remove testcases (optional), and clear down metacello. > > It's probably worthy of a blog post - but honestly the running example is > pretty straight forward. > > The commercial tools all have a decent "strip dead code" tool, that does a > similar thing in reverse - which is equally a decent way of approaching > the problem and can lead to even tinier results. > > Tim > > Sent from my iPhone > >> On 21 Aug 2017, at 21:25, horrido < > horrido.hobbies@ > > wrote: >> >> I received this comment on Facebook: >> >> Smalltalk is a fantastic language and its development environment can't >> be >> beat... But the documentation for the many open source implementations is >> contradictory or confusing or missing. I can't speak for the commercial >> versions. Without an experienced mentor it is not possible to create a >> complex app. And even when you have done so, *I know no way to strip out >> the >> unused part of the image as well as the embedded source code*. >> ----- >> >> This issue of stripping out unused code seems to recur a lot. And truth >> be >> told, I've never seen a clear explanation of how to do this. Can someone >> provide clear direction? Is this documented anywhere? I'd like to use the >> information in future to assuage other people's concerns. >> >> Thanks. >> >> >> >> -- >> View this message in context: >> http://forum.world.st/Minimizing-an-Application-tp4963262.html >> Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. >> -- View this message in context: http://forum.world.st/Minimizing-an-Application-tp4963262p4963349.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Aug. 22, 2017