- Pharo-users - lists.pharo.org

Re: [Pharo-users] Siren 9.0 Released

by StÃ©phane Ducasse

Ok still Iâm not sure that we can ship a full image. I could never understand fully what is a personal license and for me this is super simple I do not want to read any VisualWorks code under a License that is not MIT. This way laywers will never been able to tell me that I could have been influenced by protected code. S. > On 20 May 2020, at 10:19, Richard O'Keefe <raoknz(a)gmail.com> wrote: > > Cincom still has a "Personal Use Licence". > http://www.cincomsmalltalk.com/main/community/product-portal/trying-cincom-… <http://www.cincomsmalltalk.com/main/community/product-portal/trying-cincom-…> > I am running vw8.3pul, and > file ~/vw8.3pul/bin/linuxx86_64/visual > /home/ok/vw8.3pul/bin/linuxx86_64/visual: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 2.6.9, stripped > it is 64-bit. > The paid version of VW is up to 9.0, but 8.3 works for me. > > > On Fri, 15 May 2020 at 08:16, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr <mailto:stephane.ducasse@inria.fr>> wrote: > Thanks Steven this is cool to see that Siren is living and kicking. > Last year I was browsing the old site and I was sad because I thought it was dead. > Your OSC looks better than the one in Pharo even if we used it successfully to connect interactive tables with a HCI research group. > > If you need help to migrate from VW let us know because it would be great to have Siren working in Pharo. > I did not see any Unit tests and the tests saved us when we migrated Moose. Sometimes we even only kept them because they were > better than the implementation. It took us around six months and we got free :) > And we have some contacts that would be interested in London. We could put you in contact. > > Now just some questions and you may know the answer so I ask > > I was thinking but I may be totally wrong that it was forbidden to give VW images and that the current license > was for personal use only. Long time ago the shrink process was removing the compiler. Now I saw that your image is 42mb. > > Personally I do not want to download any VisualWorks distribution and sign their licenses because I want to stay cristal clear > on ANY license and possible issues. I did not look at Visualworks since 2008 and I feel clean and I will stay like that. > > So I imagine that Iâm not allowed to use your software. Iâm not good in music sadly so there is no frustration from my side. > > You mention that people can use a non-commercial version of VW but this license does not exist anymore. > > Is there a 64 bits version of VW because VW7.5 starts to show its age and on recent mac you only have 64 bits. > > > Some people may think that we are just over the top on open-source but this is not by accident that we took the responsibility to create Pharo. > We could not distribute Moose our open-source platform so after 10 years of hard work we had to do something. And we created Pharo. > And the problem we got were with the previous version (the non commercial) of the Cincom license and the new one is even more restrictive. > Some friends of mine told me that some lawyers were starting to get picky and send letters around. > So watch out. > > BTW I did not see the license of Siren on the git repo. If I may suggest one, > BSD/MIT are nice, avoid GPL because it means that nobody serious on Smalltalk will ever look at your system and contribute. > > S. > >> On 14 May 2020, at 01:40, stephen(a)heaveneverywhere.com <mailto:stephen@heaveneverywhere.com> wrote: >> >> >> Hello all, >> >> The Siren system is a general-purpose framework for music and sound composition, processing, performance, and analysis; it is a collection of about 350 classes written in Smalltalk-80 (40 kLOC or so). Siren 9.0 works on VisualWorks Smalltalk (though the bulk has been ported to other dialects as well); Siren supports streaming I/O via OpenSoundControl (OSC), MIDI, and multi-channel audio ports. The Siren release is available via the web from the URL http://FASTLabInc.com/Siren <http://fastlabinc.com/Siren>. >> >> Siren is a programming framework and tool kit; the intended audience is Smalltalk developers, or users willing to learn Smalltalk in order to write their own applications. The built-in applications are meant as demonstrations of the use of the libraries, rather than as end-user applications. Siren is not a MIDI sequencer, nor a score notation editor, through both of these applications would be easy to implement with the Siren framework. >> >> There are several elements to Siren: >> >> * the Smoke music representation language (music magnitudes, events, event lists, generators, functions, and sounds); >> >> * voices, schedulers and I/O drivers (real-time and file-based voices, sound, score file, OSC, and MIDI I/O); >> >> * user interface components for musical applications (UI framework, tools, and widgets); >> >> * several built-in applications (editors and browsers for Smoke objects); and >> >> * external library interfaces for streaming I/O and DSP math (sound/MIDI I/O, fast FFT, CSL & Loris sound analysis/resynthesis packages ) >> >> The best in-depth doc (book chapter) is in, >> http://FASTLabInc.com/Siren/Doc/SirenBookChapter.pdf <http://fastlabinc.com/Siren/Doc/SirenBookChapter.pdf> >> >> The read the demo code workbook (this text), go to, >> http://FASTLabInc.com/Siren/Siren7.5.Workbook.html <http://fastlabinc.com/Siren/Siren7.5.Workbook.html> >> or >> http://FASTLabInc.com/Siren/Siren7.5.Workbook.pdf <http://fastlabinc.com/Siren/Siren7.5.Workbook.pdf> >> >> If you like to read manuals, take a look at, >> http://FASTLabInc.com/Siren/Manual <http://fastlabinc.com/Siren/Manual> >> >> or watch the detailed Siren demo at, >> https://vimeo.com/120751122 <https://vimeo.com/120751122> >> >> The links to get Siren9 are, >> >> Web site: http://fastlabinc.com/Siren <http://fastlabinc.com/Siren> >> >> Package download: http://fastlabinc.com/Siren/Siren_9.0.zip <http://fastlabinc.com/Siren/Siren_9.0.zip> >> >> Github repo: https://github.com/stpope/Siren9 <https://github.com/stpope/Siren9> >> >> >> Comments solicited. >> >> Stephen Pope >> >> >> -- >> >> Stephen Travis Pope Santa Barbara, California, USA >> <pastedGraphic.tiff> http://HeavenEverywhere.com <http://heaveneverywhere.com/> http://FASTLabInc.com <http://fastlabinc.com/> >> https://vimeo.com/user19434036/videos <https://vimeo.com/user19434036/videos> http://heaveneverywhere.com/Reflections <http://heaveneverywhere.com/Reflections> >> >> -- >> >> >> > > -------------------------------------------- > StÃ©phane Ducasse > http://stephane.ducasse.free.fr <http://stephane.ducasse.free.fr/> / http://www.pharo.org <http://www.pharo.org/> > 03 59 35 87 52 > Assistant: Julie Jonas > FAX 03 59 57 78 50 > TEL 03 59 35 86 16 > S. Ducasse - Inria > 40, avenue Halley, > Parc Scientifique de la Haute Borne, BÃ¢t.A, Park Plaza > Villeneuve d'Ascq 59650 > France > -------------------------------------------- StÃ©phane Ducasse http://stephane.ducasse.free.fr / http://www.pharo.org 03 59 35 87 52 Assistant: Aurore Dalle FAX 03 59 57 78 50 TEL 03 59 35 86 16 S. Ducasse - Inria 40, avenue Halley, Parc Scientifique de la Haute Borne, BÃ¢t.A, Park Plaza Villeneuve d'Ascq 59650 France

May 22, 2020

Re: [Pharo-users] Cant add local git repo to Iceberg

by StÃ©phane Ducasse

> Importing repository from /Users/Michael/Development/gitRepos/FredsLunch-Pharo > >> [graphe:~/Development/gitRepos/FredsLunch-Pharo] Michael% git status >> On branch master >> Your branch is up-to-date with 'origin/master'. >> Changes to be committed: >> (use "git reset HEAD <file>..." to unstage) >> >> modified: FredsLunch.st >> new file: FredsLunchCSV.st >> new file: FredsLunchLunch.st >> new file: FredsLunchLunchData.st >> new file: FredsLunchLunchList.st >> new file: FredsLunchMain.st >> new file: FredsLunchMember.st >> new file: FredsLunchMemberList.st >> new file: FredsLunchParticipant.st >> new file: FredsLunchTest.st >> modified: FredsLunchTests.st >> new file: ManifestFredsLunch.st >> >> Untracked files: >> (use "git add <file>..." to include in what will be committed) >> >> pharo-local/ >> >> [graphe:~/Development/gitRepos/FredsLunch-Pharo] Michael% pwd >> /Users/Michael/Development/gitRepos/FredsLunch-Pharo >> [graphe:~/Development/gitRepos/FredsLunch-Pharo] Michael% >> > > > The files currently in that repo were the result of doing a fileOut of each of the classes in the package. You do not have to do the fileout by hand. Did you check the chapters in PBE80 books and section 10 of the attached pdf > Now, Iâm trying to register that local repository in Iceberg. > > After I supply the pathname for the repository and press OK I get an exception window. this is strange can you tell us your OS + version Pharo version > > Copy stack from debug window: > >> FFICallout>>loaderForArgNamed: >> FFICallout>>loaderForArgNamed:indirectIndex: >> FFIVariableArgument>>resolveUsing: >> [ :arg2 | arg2 resolveUsing: arg1 ] in FFIFunctionSpec>>resolveUsing: in Block: [ :arg2 | arg2 resolveUsing: arg1 ] >> OrderedCollection>>do: >> FFIFunctionSpec>>resolveUsing: >> FFICalloutMethodBuilder>>generateMethodFromSpec: >> FFICalloutMethodBuilder>>generate >> FFICalloutMethodBuilder>>build: >> FFICalloutAPI>>function:library: >> FFICalloutAPI>>function:module: >> LGitRepository(LGitExternalObject)>>callUnchecked:options: >> LGitRepository>>repository_open:bare_path: >> [ self >> repository_open: self >> bare_path: self repositoryReference pathString ] in LGitRepository>>open in Block: [ self... >> LGitRepository(LGitExternalObject)>>withReturnHandlerDo: >> LGitRepository>>open >> IceLibgitRepository>>repositoryHandle >> [ | tmp1 | >> self isValid >> ifFalse: [ ^ #() ]. >> tmp1 := self repositoryHandle allRemotes. >> ^ tmp1 >> collect: [ :arg1 | >> | tmp3 | >> tmp3 := IceGitRemote name: arg1 remoteName url: arg1 url. >> tmp3 >> localRepository: self; >> yourself ] ] in IceLibgitRepository>>remotes in Block: [ | tmp1 |... >> BlockClosure>>on:do: >> IceLibgitRepository>>handleLibgitError: >> IceLibgitRepository>>remotes >> IcePharoPlugin class>>isAvailableFor: >> [ :arg2 | arg2 isAvailableFor: arg1 ] in IcePlugin class>>allAvailableFor: in Block: [ :arg2 | arg2 isAvailableFor: arg1 ] >> OrderedCollection>>select: >> IcePlugin class>>allAvailableFor: >> IcePluginManager>>availablePluginsFor: >> IcePluginManager>>initializeRepository: >> IcePluginManager class>>managerFor: >> IceLibgitRepository(IceRepository)>>pluginManager >> IceRepositoryCreator>>addLocalRepository >> >> > > If I try to Fuel out the exception I get another exception whose stack looks like this: > >> File>>openForWrite: >> File>>openForWrite >> File>>writeStream >> File>>writeStreamDo: >> FLPharo7Platform>>fileNamed:writeStreamDo: >> FLSerializer>>serialize:toFileNamed: >> FuelOutStackDebugAction class>>serializeTestFailureContext:toFileNamed: >> FuelOutStackDebugAction>>serializeStack >> FuelOutStackDebugAction>>executeAction >> FuelOutStackDebugAction(DebugAction)>>execute >> [ self execute ] in FuelOutStackDebugAction(DebugAction)>>asGlamourAction in Block: [ self execute ] >> BlockClosure>>glamourValueWithArgs: >> GLMGenericAction(GLMAction)>>actOn: >> GLMGenericAction(GLMAction)>>morphicActOn: >> [ | tmp2 | >> (tmp2 := selector numArgs) = 0 >> ifTrue: [ target perform: selector ] >> ifFalse: [ tmp2 = arguments size >> ifTrue: [ target perform: selector withArguments: arguments ] >> ifFalse: [ target perform: selector withArguments: (arguments copyWith: arg1) ] ]. >> self >> showShortcut; >> changed ] in ToggleMenuItemMorph(MenuItemMorph)>>invokeWithEvent: in Block: [ | tmp2 |... >> BlockClosure>>ensure: >> CursorWithMask(Cursor)>>showWhile: >> ToggleMenuItemMorph(MenuItemMorph)>>invokeWithEvent: >> ToggleMenuItemMorph(MenuItemMorph)>>mouseUp: >> ToggleMenuItemMorph(MenuItemMorph)>>handleMouseUp: >> MouseButtonEvent>>sentTo: >> ToggleMenuItemMorph(Morph)>>handleEvent: >> MorphicEventDispatcher>>dispatchDefault:with: >> MorphicEventDispatcher>>handleMouseUp: >> MouseButtonEvent>>sentTo: >> [ ^ arg1 sentTo: self ] in MorphicEventDispatcher>>dispatchEvent:with: in Block: [ ^ arg1 sentTo: self ] >> BlockClosure>>ensure: >> MorphicEventDispatcher>>dispatchEvent:with: >> ToggleMenuItemMorph(Morph)>>processEvent:using: >> MorphicEventDispatcher>>dispatchDefault:with: >> > > > > > > -------------------------------------------- StÃ©phane Ducasse http://stephane.ducasse.free.fr / http://www.pharo.org 03 59 35 87 52 Assistant: Aurore Dalle FAX 03 59 57 78 50 TEL 03 59 35 86 16 S. Ducasse - Inria 40, avenue Halley, Parc Scientifique de la Haute Borne, BÃ¢t.A, Park Plaza Villeneuve d'Ascq 59650 France

May 22, 2020

Re: [Pharo-users] Spec2 Pharo8/9; icons

by StÃ©phane Ducasse

thanks for sharing. I will add it to the chapter Tips of the new book on Spec20 :) I remember also that there is a project to manage icon sets. > On 20 May 2020, at 21:44, TomaÅ¾ Turk <tomaz.turk(a)ef.uni-lj.si> wrote: > > Thanks, Stephane, I'll switch to P9. > > > png is better and there is a library to manage icons > > I do not have the name but you can load icons. > > But look around. > > For icons I found the necessary code in ThemeIcons>>loadIconsFromUrl. Here's a simplistic approach to load icons from PNGs in a local ZIP archive, if somebody needs it: > > | themeIcons newIcons | > > newIcons := IdentityDictionary new. > themeIcons := ThemeIcons new. > > ((FileSystem zip: 'C:\icons\a.zip' asFileReference) > open workingDirectory allChildrenMatching: '*.png') do: > [ :each | newIcons > at: each base asSymbol > put: (themeIcons readPNGFrom: each )]. > newIcons. > > Best wishes, > Tomaz -------------------------------------------- StÃ©phane Ducasse http://stephane.ducasse.free.fr / http://www.pharo.org 03 59 35 87 52 Assistant: Aurore Dalle FAX 03 59 57 78 50 TEL 03 59 35 86 16 S. Ducasse - Inria 40, avenue Halley, Parc Scientifique de la Haute Borne, BÃ¢t.A, Park Plaza Villeneuve d'Ascq 59650 France

May 22, 2020

Re: [Pharo-users] A little help with EnterprisePharo book

by StÃ©phane Ducasse

Hello Hi jonathan I have to check because this is the first book we wrote with Pillar. Normally with more recent books I add a build to produce automatically the pdf (but I have to check because latex is sometimes super boring -like not offering the same packages). > Hi all, > > I'd like to be able to build the EnterprisePharo book, so I might contribute to it with some improvements. However, the README seems to be out of date. What you can do is to issue PRs if they break we will > > The 'download.sh' file mentioned under 'Download Pillar' is not there. There's a 'subdownload.sh' file, but that doesn't do or output anything, and looking into it, the URL returns a 404 (https://raw.githubusercontent.com/pillar-markup/pillar/master/download.sh <https://raw.githubusercontent.com/pillar-markup/pillar/master/download.sh>). > > So I manually cloned the pillar git project from https://github.com/pillar-markup/pillar <https://github.com/pillar-markup/pillar>. I checked out tag v7.7.4, since that was mentioned for Pharo booklets. Building that works, resulting in a pillar 'executable'. > > However, after installing MacText, executing 'pillar build pdf' fails with the message: FileDoesNotExistException: '/Users/jvalteren/git/EnterprisePharo/_support'. Looking at the structure created by the command 'pillar archetype book', it seems that '_support' is the new name for the 'support' folder that does. Yes. between pillar 6 and 7 we revisited fully the pipeline and the configuration managed and many more. > So, I created a symlink from '_support' to 'support' and tried building again, but that fails with the message: KeyNotFound: latexWriter. This seems to be related to the contents of the 'pillar.conf' file. What we can try is to copy the _support file of a more recent version + edit the config and index/main.pillar files. I will be try to find some time this evening. > > Instead of trying to guess what's going on and try different things to fix this and get it built, I thought to reach out here :-) > > Can anyone tell me what to do so I can start making changes to the book? First send a PR so that it is not lost. > > I'm on macOS Catalina by the way, so 64-bit only. > > > Thanks! > > > <https://objectguild.com/> > Jonathan van Alteren > Founding Member | Object Guild B.V. > Sustainable Software for Purpose-Driven Organizations > > jvalteren(a)objectguild.com <mailto:jvalteren@objectguild.com> -------------------------------------------- StÃ©phane Ducasse http://stephane.ducasse.free.fr / http://www.pharo.org 03 59 35 87 52 Assistant: Aurore Dalle FAX 03 59 57 78 50 TEL 03 59 35 86 16 S. Ducasse - Inria 40, avenue Halley, Parc Scientifique de la Haute Borne, BÃ¢t.A, Park Plaza Villeneuve d'Ascq 59650 France

May 22, 2020

Re: [Pharo-users] Refactor without formatting

by Vitor Medina Cruz

Here: https://github.com/pharo-project/pharo/issues/6387 I attached a filled out class with some examples. On Thu, May 21, 2020 at 2:35 PM Vitor Medina Cruz <vitormcruz(a)gmail.com> wrote: > I will setup a class with examples, open an issue and then reply here. > > On Thu, May 21, 2020 at 11:20 AM hogoww <pierre.misse-chanabier(a)inria.fr> > wrote: > >> I wanted to take a look at this, but I could not reproduce the issue, >> although I distinctly remember I had the issue at some point. >> Could you describe the problem further please? >> >> Pierre >> On 21/05/2020 12:06, Guillermo Polito wrote: >> >> I think what Stef means: >> - yes, please open an issue (maybe check there is no one already there?) >> - If somebody wants to give it a try at fixing this, it would be SUPER >> welcome :P :) >> (and that nobody needs to be an expert to do that, itâs the other >> way around, you become an expert by doing it ^^) >> >> El 20 may 2020, a las 21:16, Vitor Medina Cruz <vitormcruz(a)gmail.com> >> escribiÃ³: >> >> Ok, so should I open the issue or leave it as it is? >> >> On Wed, May 20, 2020 at 2:08 PM StÃ©phane Ducasse < >> stephane.ducasse(a)inria.fr> wrote: >> >>> There is what we would love to have and there is what we have. >>> It is difficult to conserve the formatting of the original method >>> especially on extract >>> or more generally on code transformation. >>> Now it does not mean that we like it this way. >>> But given the ratio income/results I think that Pharo is super super >>> good. >>> >>> But but >>> people can help >>> people can pay for more. >>> >>> S. >>> >>> On 19 May 2020, at 19:33, Vitor Medina Cruz <vitormcruz(a)gmail.com> >>> wrote: >>> >>> Hello, >>> >>> When I run a refactoring, Rename Method, for example, the refactoring is >>> reformatting the code affected. Is it possible to configure Pharo to >>> refactor without reformatting code? Depending on the refactoring, the >>> reformat is so intrusive that make it more worth to make the refactoring by >>> hand. >>> >>> Regards, >>> Vitor >>> >>> >>> -------------------------------------------- >>> StÃ©phane Ducasse >>> http://stephane.ducasse.free.fr / http://www.pharo.org >>> 03 59 35 87 52 >>> Assistant: Julie Jonas >>> FAX 03 59 57 78 50 >>> TEL 03 59 35 86 16 >>> S. Ducasse - Inria >>> 40, avenue Halley, >>> Parc Scientifique de la Haute Borne, BÃ¢t.A, Park Plaza >>> Villeneuve d'Ascq 59650 >>> France >>> >>> >>

May 21, 2020

Re: [Pharo-users] [ANN] What are good reasons to use Smalltalk?

by Vitor Medina Cruz

Thanks! " When/if smalltalk grows to a web scale " Let's hope so :) On Thu, May 21, 2020 at 4:09 PM Esteban Maringolo <emaringolo(a)gmail.com> wrote: > On Thu, May 21, 2020 at 11:34 AM Vitor Medina Cruz <vitormcruz(a)gmail.com> > wrote: > > Sorry, I mean how so are Smalltalk systems less compatible than web > browsers are? > > Different dialects have different features (e.g. Namespaces, Traits), > syntax, image format... > > Smalltalk is a concept, with Smalltalk-80 as the canonical reference, > not even a specification, because ANSI Smalltalk was the closest thing > to a standard (Like ECMA TS39 is for JavaScript), but it was DoA. > > > This means between different distributions of Smalltalk (VA, Squeak, > Pharo...)? Same code are not as compatible between different Smalltalks > distribution as a web application is between different browsers? How so? > Why? > > Because of history for the most part. > Smalltalk comes from a pre-opensource era, where commercial vendors > were the norm, and competition was not collaborative as it might be > now. > > Each one took its own path and merging everything back is non-viable, > both for technical and commercial reasons. > > When/if smalltalk grows to a web scale, then the need for standards > and constraint will arise. > > Regards! > > Esteban A. Maringolo > >

May 21, 2020

Re: [Pharo-users] [ANN] What are good reasons to use Smalltalk?

by Esteban Maringolo

On Thu, May 21, 2020 at 11:34 AM Vitor Medina Cruz <vitormcruz(a)gmail.com> wrote: > Sorry, I mean how so are Smalltalk systems less compatible than web browsers are? Different dialects have different features (e.g. Namespaces, Traits), syntax, image format... Smalltalk is a concept, with Smalltalk-80 as the canonical reference, not even a specification, because ANSI Smalltalk was the closest thing to a standard (Like ECMA TS39 is for JavaScript), but it was DoA. > This means between different distributions of Smalltalk (VA, Squeak, Pharo...)? Same code are not as compatible between different Smalltalks distribution as a web application is between different browsers? How so? Why? Because of history for the most part. Smalltalk comes from a pre-opensource era, where commercial vendors were the norm, and competition was not collaborative as it might be now. Each one took its own path and merging everything back is non-viable, both for technical and commercial reasons. When/if smalltalk grows to a web scale, then the need for standards and constraint will arise. Regards! Esteban A. Maringolo

May 21, 2020

Re: [Pharo-users] Refactor without formatting

by Vitor Medina Cruz

I will setup a class with examples, open an issue and then reply here. On Thu, May 21, 2020 at 11:20 AM hogoww <pierre.misse-chanabier(a)inria.fr> wrote: > I wanted to take a look at this, but I could not reproduce the issue, > although I distinctly remember I had the issue at some point. > Could you describe the problem further please? > > Pierre > On 21/05/2020 12:06, Guillermo Polito wrote: > > I think what Stef means: > - yes, please open an issue (maybe check there is no one already there?) > - If somebody wants to give it a try at fixing this, it would be SUPER > welcome :P :) > (and that nobody needs to be an expert to do that, itâs the other > way around, you become an expert by doing it ^^) > > El 20 may 2020, a las 21:16, Vitor Medina Cruz <vitormcruz(a)gmail.com> > escribiÃ³: > > Ok, so should I open the issue or leave it as it is? > > On Wed, May 20, 2020 at 2:08 PM StÃ©phane Ducasse < > stephane.ducasse(a)inria.fr> wrote: > >> There is what we would love to have and there is what we have. >> It is difficult to conserve the formatting of the original method >> especially on extract >> or more generally on code transformation. >> Now it does not mean that we like it this way. >> But given the ratio income/results I think that Pharo is super super >> good. >> >> But but >> people can help >> people can pay for more. >> >> S. >> >> On 19 May 2020, at 19:33, Vitor Medina Cruz <vitormcruz(a)gmail.com> wrote: >> >> Hello, >> >> When I run a refactoring, Rename Method, for example, the refactoring is >> reformatting the code affected. Is it possible to configure Pharo to >> refactor without reformatting code? Depending on the refactoring, the >> reformat is so intrusive that make it more worth to make the refactoring by >> hand. >> >> Regards, >> Vitor >> >> >> -------------------------------------------- >> StÃ©phane Ducasse >> http://stephane.ducasse.free.fr / http://www.pharo.org >> 03 59 35 87 52 >> Assistant: Julie Jonas >> FAX 03 59 57 78 50 >> TEL 03 59 35 86 16 >> S. Ducasse - Inria >> 40, avenue Halley, >> Parc Scientifique de la Haute Borne, BÃ¢t.A, Park Plaza >> Villeneuve d'Ascq 59650 >> France >> >> >

May 21, 2020

A little help with EnterprisePharo book

by Jonathan van Alteren

Hi all, I'd like to be able to build the EnterprisePharo book, so I might contribute to it with some improvements. However, the README seems to be out of date. The 'download.sh' file mentioned under 'Download Pillar' is not there. There's a 'subdownload.sh' file, but that doesn't do or output anything, and looking into it, the URL returns a 404 (https://raw.githubusercontent.com/pillar-markup/pillar/master/download.sh) So I manually cloned the pillar git project fromÂ https://github.com/pillar-markup/pillar. I checked out tag v7.7.4, since that was mentioned for Pharo booklets. Building that works, resulting in a pillar 'executable'. However, after installing MacText, executing 'pillar build pdf' fails with the message: FileDoesNotExistException: '/Users/jvalteren/git/EnterprisePharo/_support'. Looking at the structure created by the command 'pillar archetype book', it seems that '_support' is the new name for the 'support' folder that does. So, I created a symlink from '_support' to 'support' and tried building again, but that fails with the message: KeyNotFound: latexWriter. This seems to be related to the contents of the 'pillar.conf' file. Instead of trying to guess what's going on and try different things to fix this and get it built, I thought to reach out here :-) Can anyone tell me what to do so I can start making changes to the book? I'm on macOS Catalina by the way, so 64-bit only. Thanks! Jonathan van Alteren Founding Member | Object Guild B.V. Sustainable Software for Purpose-Driven Organizations jvalteren(a)objectguild.com

May 21, 2020

Re: [Pharo-users] [ANN] Gravatar wrapper moved to GitHub

by Guillermo Polito

Thanks!! > El 21 may 2020, a las 14:37, Torsten Bergmann <astares(a)gmx.de> escribiÃ³: > > Just migrated "Pharo-Gravatar" - a simple Pharo wrapper for the Gravatar API > over to GitHub: > > https://github.com/astares/Pharo-Gravatar > > see attached image for an example. > > Enjoy! > > Bye > T. > <gravatar.png>

May 21, 2020