December 2019 - Pharo-users

Re: [Pharo-users] External Module not found - LGitLibrary

by Andrei Chis

Hi, We got a slightly similar error with Pharo 8 on a Linux CI when loading code quite often (but still randomly). Does it happen for you when loading code or just when opening the image? Which Pharo 8.0 build are you using? Error: External module not found ExternalLibraryFunction(Object)>>error: ExternalLibraryFunction(Object)>>externalCallFailed ExternalLibraryFunction(ExternalFunction)>>invokeWithArguments: LGitCommit>>commit_tree:commit: LGitCommit>>tree LGitCommitStore>>nodeAt:ifPresent:ifAbsent: LGitCommitStore(FileSystemStore)>>exists: FileSystem>>exists: FileReference>>exists IceBasicProjectReader>>canReadProjectFromCommitish: [ :any | any canReadProjectFromCommitish: anIceCommitish ] in IceProjectReader class>>readProjectFrom: in Block: [ :any | any canReadProjectFromCommitish: anIceCom...etc... [ :each | (aBlock value: each) ifTrue: [ ^ foundBlock cull: each ] ] in OrderedCollection(Collection)>>detect:ifFound:ifNone: in Block: [ :each | ... OrderedCollection>>do: OrderedCollection(Collection)>>detect:ifFound:ifNone: OrderedCollection(Collection)>>detect:ifNone: OrderedCollection(Collection)>>detect: IceProjectReader class>>readProjectFrom: [ IceProjectReader readProjectFrom: self ] in IceGitCommit>>project in Block: [ IceProjectReader readProjectFrom: self ] BlockClosure>>on:do: IceGitCommit>>project IceWorkingCopy>>refreshProjectFromRepository IceWorkingCopy>>referenceCommit: IceWorkingCopy>>adoptCommit: IceGitCommit(IceCommit)>>adopt IceCheckoutDoNotLoadPackages>>checkoutOn: IceWorkingCopy>>checkout: IceLibgitRepository(IceRepository)>>checkout: IceGitLocalBranch(IceCommitish)>>checkout: IceGitLocalBranch(IceCommitish)>>switch IceLibgitRepository(IceRepository)>>switchToCommitishNamed: On Fri, Dec 20, 2019 at 1:28 AM BrunoBB <smalltalk(a)adinet.com.uy> wrote: > Hi, > > Using Pharo on Windows time to time i got "External Module not found" for > LGitLibrary. > > Not sure if i'm hitting: > https://github.com/pharo-project/pharo-launcher/issues/307 > > But this time the problem is not fixed. Other time after some trying to > open > the image in different way (PharoLaucher, from CommandLine, selecting > Pharo.exe to open .image files, ..) the problem fixed itself. > > ExternalLibraryFunction(Object)>>error: > ExternalLibraryFunction(Object)>>externalCallFailed > ExternalLibraryFunction(ExternalFunction)>>invokeWithArguments: > LGitLibrary>>libgit2_init > FFICalloutAPI>>function:module: > LGitLibrary(Object)>>ffiCall: > LGitLibrary>>libgit2_init > [ self libgit2_init. > self recordInitializationSuccess ] in LGitLibrary>>initializeLibGit2 in > Block: [ self libgit2_init.... > BlockClosure>>on:do: > LGitLibrary>>initializeLibGit2 > LGitLibrary class>>startUp: > ClassSessionHandler>>startup: > [ :each | each startup: isImageStarting ] in WorkingSession>>runStartup: in > Block: [ :each | each startup: isImageStarting ] > [ aBlock value: each ] in [ :each | > [ aBlock value: each ] > on: Exception > do: [ :error | self errorHandler handleError: error ] ] in > WorkingSession>>runList:do: in Block: [ aBlock value: each ] > BlockClosure>>on:do: > [ :each | > [ aBlock value: each ] > on: Exception > do: [ :error | self errorHandler handleError: error ] ] in > WorkingSession>>runList:do: in Block: [ :each | ... > Array(SequenceableCollection)>>do: > WorkingSession>>runList:do: > WorkingSession>>runStartup: > WorkingSession>>start: > SessionManager>>launchSnapshot:andQuit: > [ isImageStarting := self launchSnapshot: save andQuit: quit. > wait signal ] in SessionManager>>snapshot:andQuit: in Block: [ > isImageStarting := self launchSnapshot: save and...etc... > [ self value. > Processor terminateActive ] in BlockClosure>>newProcess in Block: [ self > value.... > > > > > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html > >

Dec. 20, 2019

Re: [Pharo-users] Code overview - or maybe not

by David T. Lewis

On Thu, Dec 19, 2019 at 09:57:43PM +0100, Trygve Reenskaug wrote: > Such a tool has existed for a long time, it's called /Squeak Reverse > Engineering /(/SRE/). It's very useful for exploring execution stacks, > objects, and object structures. It goes across different kinds of > objects. It only works in Squeak 3.10.2. > User manual at > http://folk.uio.no/trygver/themes/SRE/BabySRE.pdf > Latest version of the SRE programs in this image > http://dx.doi.org/10.17632/5xxgzv7fsp.1 I just downloaded this image from http://dx.doi.org/10.17632/5xxgzv7fsp.1 and it is working fine on my Linux laptop. It does require a suitable VM (I compile my own). Very interesting stuff, thanks. Dave > > Examples. (Top line/[OOP]object name if any/. Bottom line /://Object's > clas//s name/). > > > > > The new object inspector with state and behavior. > > > > The new /Transcript //show:xx/ with the stack. > > >

Dec. 19, 2019

External Module not found - LGitLibrary

by BrunoBB

Hi, Using Pharo on Windows time to time i got "External Module not found" for LGitLibrary. Not sure if i'm hitting: https://github.com/pharo-project/pharo-launcher/issues/307 But this time the problem is not fixed. Other time after some trying to open the image in different way (PharoLaucher, from CommandLine, selecting Pharo.exe to open .image files, ..) the problem fixed itself. ExternalLibraryFunction(Object)>>error: ExternalLibraryFunction(Object)>>externalCallFailed ExternalLibraryFunction(ExternalFunction)>>invokeWithArguments: LGitLibrary>>libgit2_init FFICalloutAPI>>function:module: LGitLibrary(Object)>>ffiCall: LGitLibrary>>libgit2_init [ self libgit2_init. self recordInitializationSuccess ] in LGitLibrary>>initializeLibGit2 in Block: [ self libgit2_init.... BlockClosure>>on:do: LGitLibrary>>initializeLibGit2 LGitLibrary class>>startUp: ClassSessionHandler>>startup: [ :each | each startup: isImageStarting ] in WorkingSession>>runStartup: in Block: [ :each | each startup: isImageStarting ] [ aBlock value: each ] in [ :each | [ aBlock value: each ] on: Exception do: [ :error | self errorHandler handleError: error ] ] in WorkingSession>>runList:do: in Block: [ aBlock value: each ] BlockClosure>>on:do: [ :each | [ aBlock value: each ] on: Exception do: [ :error | self errorHandler handleError: error ] ] in WorkingSession>>runList:do: in Block: [ :each | ... Array(SequenceableCollection)>>do: WorkingSession>>runList:do: WorkingSession>>runStartup: WorkingSession>>start: SessionManager>>launchSnapshot:andQuit: [ isImageStarting := self launchSnapshot: save andQuit: quit. wait signal ] in SessionManager>>snapshot:andQuit: in Block: [ isImageStarting := self launchSnapshot: save and...etc... [ self value. Processor terminateActive ] in BlockClosure>>newProcess in Block: [ self value.... -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Dec. 19, 2019

Re: [Pharo-users] Code overview - or maybe not

by Kasper Ãsterbye

My issue with the background color was how to make a TextAttribute to set the background color of individual characters, not the overall background of the text. I succeeded, and Pharo 8 has a background text attribute - at least using Rubric - see https://github.com/pharo-project/pharo/pull/5326 Christopher - thanks for the hint on doing background colors based on theme. I did do it for the two main themes, and did not try out the larger set of themes. I needed it because I am working on an in-image pillar renderer for class and package comments, and I wanted to be able to do the inline code as done in github markdown. There is a preview of this at: https://github.com/kasperosterbye/PillarRichTextRender Best, Kasper On 19 December 2019 at 23.07.38, Christopher Fuhrman ( christopher.fuhrman(a)etsmtl.ca) wrote: If you want to consider changing background color that takes into consideration the theme background (e.g. dark or light themes), this code (see it on GitHub) <https://github.com/moosetechnology/Moose-Easy/blob/f7967b310021147792858c57…> can adapt to it: normalColor := Smalltalk ui theme backgroundColor. green := normalColor mixed: 0.8 with: Color green. red := normalColor mixed: 0.8 with: Color red. I didn't really test it with all possibilities of themes, however. On Thu, 19 Dec 2019 at 12:58, Hilaire <hilaire(a)drgeo.eu> wrote: > You should use TextMorph. > > What about: > > || t | > t := TextMorph new. > t backgroundColor: Color blue. > t contents: 'Hello'. > t lock. > t openInWorld|| > | > > Le 19/12/2019 Ã 15:28, Kasper Osterbye a Ã©crit : > > I was struggling for weeks (not every day, but still) to find out how > > to change the system to be able to give background color to text. > > > -- > Dr. Geo > http://drgeo.eu > > > > -- Christopher Fuhrman, P.Eng., PhD *Professeur au DÃ©partement de gÃ©nie logiciel et des technologies de l'information ÃTS (Ãcole de technologie supÃ©rieure)*

Dec. 19, 2019

Re: [Pharo-users] Code overview - or maybe not

by Christopher Fuhrman

If you want to consider changing background color that takes into consideration the theme background (e.g. dark or light themes), this code (see it on GitHub) <https://github.com/moosetechnology/Moose-Easy/blob/f7967b310021147792858c57…> can adapt to it: normalColor := Smalltalk ui theme backgroundColor. green := normalColor mixed: 0.8 with: Color green. red := normalColor mixed: 0.8 with: Color red. I didn't really test it with all possibilities of themes, however. On Thu, 19 Dec 2019 at 12:58, Hilaire <hilaire(a)drgeo.eu> wrote: > You should use TextMorph. > > What about: > > || t | > t := TextMorph new. > t backgroundColor: Color blue. > t contents: 'Hello'. > t lock. > t openInWorld|| > | > > Le 19/12/2019 Ã 15:28, Kasper Osterbye a Ã©crit : > > I was struggling for weeks (not every day, but still) to find out how > > to change the system to be able to give background color to text. > > > -- > Dr. Geo > http://drgeo.eu > > > > -- Christopher Fuhrman, P.Eng., PhD *Professeur au DÃ©partement de gÃ©nie logiciel et des technologies de l'informationÃTS (Ãcole de technologie supÃ©rieure)*

Dec. 19, 2019

Grafoscopio accepted at FOSDEM :-)... Now looking for travel funds :-/

by Offray Vladimir Luna CÃ¡rdenas

Hi, The subject pretty much resumes the current situation: organizers at FOSDEM[1] approved my talk about Grafoscopio for the 2020 version (Feb 1 and 2). They tell me that they don't provide travel funds, but because I spoke about the voluntary and self funded nature of the project and asked for travel funds, the usual route here is trying to find an entity, located in Brussels that would be interested in some workshops about the tool and that will cover travel expenses. Ideally such entity would be related with the subjects and themes we have been working with the Grafoscopio community: civic tech, hacktivism, reproducible research, data journalism, data feminism, critical science and technology studies, open data, collective writing self publishing and book sprints. As you can see, Grafoscopio and its community are pretty versatile and diverse in their concerns and approaches, so I hope that opens possibilities for a lot of interested sponsors, located in Brussels. Even sponsors in Europe could work, as internal travel is kind of cheap and the biggest part of the expenses are inter continental travel. I don't know of any particular European entity that could sponsor my travel funds for FOSDEM, but hopefully the European pharoers know of some. The FOSDEM organizers asked me for some possible entities so, I'm all ears :-) Santiago and Phill, any particular ideas? If not, remember that we can prepare a remote talk :-) [1] https://fosdem.org/2020/ Thanks, Offray

Dec. 19, 2019

Re: [Pharo-users] Code overview - or maybe not

by Kasper Ãsterbye

Do you know https://github.com/fuhrmanator/PlantUMLPharoGizmo ? Norbert Indeed I know that tool, I actually base my stuff on the transformation Furhman makes in that program, only I did not use the whole tool, but just the source to url part. On 19 December 2019 at 19.15.39, tbrunz (wild.ideas(a)gmail.com) wrote: A standardized linkage to PlantUML in Pharo would be an excellent tool -- I hope you're able to pursue this and make it available on GitHub... I tried to reduce the pharo to plantUML to its barebone. Take a look at https://github.com/kasperosterbye/PlantUMLBridge Trygve: Yes, such tools are very useful - I will try to see if I can get that old image up and running and see if there is anything salvageable there. â Kasper

Dec. 19, 2019

Re: [Pharo-users] Code overview - or maybe not

by Trygve Reenskaug

Such a tool has existed for a long time, it's called /Squeak Reverse Engineering /(/SRE/). It's very useful for exploring execution stacks, objects, and object structures. It goes across different kinds of objects. It only works in Squeak 3.10.2. User manual at http://folk.uio.no/trygver/themes/SRE/BabySRE.pdf Latest version of the SRE programs in this image http://dx.doi.org/10.17632/5xxgzv7fsp.1 Examples. (Top line/[OOP]object name if any/. Bottom line /://Object's clas//s name/). The new object inspector with state and behavior. The new /Transcript //show:xx/ with the stack. On 19.12.2019 15:28, Kasper Osterbye wrote: > In an other thread Steve Davies mentions that Pharo can be a bit > overwhelming. Indeed I have had the same feeling. > > I was struggling for weeks (not every day, but still) to find out how > to change the system to be able to give background color to text. > > As part of my attempt at understanding the code, I ended up looking at > Rubric and its Text morphs. I have been working at building a little > tool which can help me get an overview of the objects and how the are > connected. Not a static code analysis, but a snapshot view. > > What I did was I took a root object, and made the transitive object > closure from that object, with the following restrictions: > - Only Rubric, Morphic and Collections are examined, though Strings > are excluded > - Only instance variables which has a selector of the same name are > included > - The same object only appear once in the diagram, but more than one > instance of a class can be present (at different places). > > I build on a tool named PlantUML. > > When I bring up the morphic halo on a playground and select "inspect > morph", and then draw the diagram for that morph,I get this diagram > <https://www.plantuml.com/plantuml/svg/ZLfFZzks4h_lfp1oUdieG54aHVNmq6IJea4RTD4jyCvQMzdLYsmPifncltr7iZYS6L7hFHamvpSav_yCzSjfgFhXl6zlRePcQEjDjVdh_FYmxRkshNT_rp-6Brr_VFvFMPQkB4gjRczkkiV_rzjXymu8Hu8_caFzRbETDl2_YgiJxjEFeJwSckuG26pkjRVAkaZuULyzrHDr8CfANIXTQCBjOL-rxUTTVO1JldnijWFmhFeNH3YTErFc1F6-xwkuNkIPCzOOTlhxgg-U-YfkN7ezxgpygvSioB6wVgXtTwEmfYC54cTrcIdA9oqEu-6MPUdvkO2ihnxgcUV7UjlrrT3rU1cL5IhF2otPDzjFtq52lrM7NLiZUPvRwtFZ_MiYBvGj2bLOlIP02n8i7HVCmtDt7Xw65zXiSSZ2gp8hbL4CyNxNzOSzdF5ZSpgsrKiyfSkpJ9VAYnr6jGzL--tJhY7CTUwjpfoY1d84yb-Rm-wl6XXlwuUw_zviKMSQZACq9jUC_TqpMC1sgFiFRRVzXWBBR6P052fz572EvZWqXwSltIxQXFMbjKpZJ7wkp7AjnUtk-sOFHeoQPXh9jNCP75fViw7IUsrqLhYhlcUiTuxf-4FNx-g-th6TdIjDgHX3RWjWJUF9hbktjc1NeAWt-x4VUSC9kPf6vOEyt_TrXPS66bCo2n0E3oSqnfbhPzJEP8Mn2p6dVQai2rTgLrnLIcvL3YQNhVgJCOK7dypVB1fjGU9PvkqYDbryOxDjgzCfXj2iB6Yu-tmurSD5tQXdOvJsJikWlH96HlVtXI8y7vhziQq5Ks_17Dz0G-xnTryTJb-xVl-_PdZ-etg1gC9T8IyLE8-vQd3WCva2DnUUEsMp3nNkR_8yywQWqIpf20QIbJ9BRQS5117CGc2wQd7UALU2s2LXcglFbGTDqi2Ii0qu9fXnocaUXch0A6L1FCxAT7DtxdlOU4nn8AH59BTPNkQ5k-vAESZAAUFLma8l6hYlOWw5U0WUuWkzeBthziVkL9DORyinVRybSfUb0grcYyIO28KcSw2hg_NAI6Co5iBIX4v1ndEiPk4E3oBaYPwP6cZ6-epLHQyPXGUTA1QqKdPU571opvBUdnSpNrOi6hQ7KAYjD8qJAJp03g7EkYfTIFsk04DpL_mBYgJIvdejP-eCXAQqMHFfMAkz8d1OXg11DRSiA6JGr4hRjsShS2KrnkGrfMOsLndtz7ISKTvOiF3LYrfWevay-Rg3h6cKusxzvx4-G02uQxiJ_7oissRV38bApKBjx8j5RITRWEXZSoVmjeIf8C6wmbyJ0TIqKCDxLY6nEqB5aOqzmQgsBRYGfo9QDVMYo0jhYwlnp07BqIMkrpaEQcSk_qiMk--xOzqFJOqc1YMB6sjn8hrNKZwKn4gfh7opHHe3BGml4fBYXcgqrBbwOsOhNGvk3qvzJH15viUOCv5X4xTvbxtR_FJJVxcbCugVDzdjflldKFVJ_w5P2wZOd7IaHwDyOpd8A2Q-0rZmM3eAi4Pmp302h6ytspaRtNIngGkusB9qf9DZrqLrC8hBTOVdkey6SjFHneuoYVx9IIOk1xZS3HKHsnxh5qOXf3rtTd6xa8aIYqn_sEAnqsArm2ZOOL5m51XhDqOn0UjWQ08TTHYZaa1hSbLi6rTD9r8iJ8U0YUcWXmemRBkhlrRdTlYzVjbNnoE4uC-7NVr3iCeZA-nG1QlyTlDrqTUEHDYdqkieleBN6AkxIIMXKLsLGQHOo21qiKaSDgoKSomh6CN4-Vje-TkBwHEmJX-BWZK_5W57USOoMu1pOKy4RQvlROWzOUVDP8aHdb5CDsv5LX1CuirZPI6Ow6JW83oY0EPEJ320spzE6M6QsuohE1QWjvXRDBOyNM4T74yV9qu23wUlINwPJ2eC6-Zk8O-mzKGaYDYuUIow19f60fnCq5tZy85Hh4LhD14cD-nh6CN4uuHTa83hT12WSBqM10YRgFeuZH9iHjk_z8NZy4hWe_N7mOt06w41WhOhoPYWxUtcgHw-r8VpVTSssnV1mKKTXaP3C72GaAUEH22BY9nBU04iBlVk-hkntXTe7-M6Gqk1zxUROnWM2tH9p3wCAGIwf363M8qYEJuqvj9i56fiwkGb2n9fSIOgMMJXyX9Cx6vkfIGKpEvqVjoFnTwbGWbZDRHtd1LsP9QsY2I6BwSY2G6JE1XcAWAU22GuSKjl7fTJcnCmhId2i4_W4xlFypPMVOMEXInVui3vSMexvymNh4Q4aSkuc144TDG70STpnqS5WTOoyqLqdevW59tJ-1acQFJG-4R029Q79c1DFI2MdHIjHzTxciU_0XvFZQC4WOP3dzfcjpYrIT-NGY7MxI58jW9fIP8E_Q50MY5dhCEPjF19Yb6an8Leuh0ujXPegME29la11qC2JNMC1HIlvy8Kcb6ivKZ2GoUSaZBGozeY14NM9k3Z3AEO3h2l-c_JF52WgKk70Q50ZrRMDOSX1OzoYrDx0H_pwlxuN9sQqs_GR4_BeH5YIezFTuo4jqV18jczQNA95AImcEkf2DPfVLCmNFlxPTBpM4auQKrmlYJWkJ1LWYQbD6lD29gMqWGP7IpEwGKI7EnvxTYnYeXZ6G5tmaTm0C1KHNKTAIvLgD0rOK25Fe-P11vata8pTgb2WZqkMhYuicZXS7ZDYbSS2JEAot5bgWn3xPLKYSl9L1d1fEB7no61JrNyOLAUxZVYScft0ewxnpSIWKybwdaEdsmNv28Re626ul4mZ6OPnJAA4pGvE0xA1Lf6SOBEq-v1qJIAe-ipsmwF4OnWUMW2NccmA7gHgGaydZgE7WMSfMe2NKdL54fJDK76I1BVUmHIfkhGUR2H5dwpGWcMxMZ4hemm29OsesW5QNUCooc7862oAmvi1JxX4A5oOflZOnObMDuuOlMALKOi6yHTsWqo-fi_TLYkqLOGdtII1h5SfVFPkJ5alZk_cfBLwOfJSNxVTIt34GUOtzOPRkgKeFBPXWOJWIIFueCMW-Qo9K0Fu_LY-AA1KIoTbg19WCPtJ86MaOQWL-f5YcOzGPWDirFZkmoZI5Iv4KrEZLzH2FIYoetebVX8qVJK6C19YHPUecZfawp3S3JF1e3u4HcZO2KUraJhioEaICsE8fmuFNu79E1IM0HDIbjyBXLeMUCHD8dCuNit0OR0t9yXq8JdZLcohB35hmOuIIA-4lnAuyZmRE0tD-E9EH6QA5cRFp_iOXM7hZ3L6A7pOth7fqv6aQp0i3Hble8VCJAAjTuAtnuGZzzbqJJBCXb-0SOebg8cw9KkWgAfeEVHBRDh_Cw8h2zosSqlzM4tVeZwBm00>. > > Strangely, I find it useful. I use it as a supplement to the inspector. > > I hope to be able to pack this tool, and a companion one for > generating sequence diagrams based on the execution of a block given > as parameter. I see these tools as exploratory tools, not as > documentation tools. > > Best, > > Kasper, > > -- /The essence of object orientation is that objects collaborateto achieve a goal. / Trygve Reenskaug mailto: trygver(a)ifi.uio.no <mailto:%20trygver@ifi.uio.no> Morgedalsvn. 5A http://folk.uio.no/trygver/ N-0378 Oslo http://fullOO.info NorwayÂ Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Tel: (+47) 468 58 625

Dec. 19, 2019

Re: [Pharo-users] Code overview - or maybe not

by Norbert Hartl

> Am 19.12.2019 um 19:22 schrieb tbrunz <wild.ideas(a)gmail.com>: > > Hi Kasper, > > PlantUML is an excellent tool for visualizing code structure, design, > behavior... For both designing it and documenting it. > > I think its most interesting feature is that its API is text-based: You > literally "spell out" your diagram in text phrases, and its (Java-based) > engine will render it as a diagram (with the help of GraphViz). > > And since it's text-based, there are extensions to text editors and document > processors (e.g., Word, LibreOffice Writer) that allow you to include the > PlantUML text in your document, then will render the diagrams in your > document for you automatically. No cut-and-paste! > > A standardized linkage to PlantUML in Pharo would be an excellent tool -- I > hope you're able to pursue this and make it available on GitHub... > Do you know https://github.com/fuhrmanator/PlantUMLPharoGizmo <https://github.com/fuhrmanator/PlantUMLPharoGizmo> ? Norbert > -Ted > > > > > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >

Dec. 19, 2019

Re: [Pharo-users] Code overview - or maybe not

by tbrunz

Hi Kasper, PlantUML is an excellent tool for visualizing code structure, design, behavior... For both designing it and documenting it. I think its most interesting feature is that its API is text-based: You literally "spell out" your diagram in text phrases, and its (Java-based) engine will render it as a diagram (with the help of GraphViz). And since it's text-based, there are extensions to text editors and document processors (e.g., Word, LibreOffice Writer) that allow you to include the PlantUML text in your document, then will render the diagrams in your document for you automatically. No cut-and-paste! A standardized linkage to PlantUML in Pharo would be an excellent tool -- I hope you're able to pursue this and make it available on GitHub... -Ted -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Dec. 19, 2019