- Pharo-users - lists.pharo.org

Re: [Pharo-users] Following Git(Hub) History

by Guillermo Polito

> El 6 ago 2019, a las 0:48, Sean P. DeNigris <sean(a)clipperadams.com> escribiÃ³: > > Does anyone have any strategies for following git histories past code > reorganizations (see steps #2 and #5 below)? > > My typical experience is: > 1. Do blame or history on a file > 2. Follow it back to the inevitable "convert to tonel" > 3. Go to that commit's parent > 4. View repo files at that point > 5. Follow back to "rename code subfolder" > 6. Repeat steps 3 - 5 as necessary until I find the version I need or > "initial commit porting from StHub!â Have you tried a $git log âfollow ? The follow option will take into account file renames and moves, simplifying at least steps 3-6. > > > > ----- > Cheers, > Sean > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >

Aug. 6, 2019

Following Git(Hub) History

by Sean P. DeNigris

Does anyone have any strategies for following git histories past code reorganizations (see steps #2 and #5 below)? My typical experience is: 1. Do blame or history on a file 2. Follow it back to the inevitable "convert to tonel" 3. Go to that commit's parent 4. View repo files at that point 5. Follow back to "rename code subfolder" 6. Repeat steps 3 - 5 as necessary until I find the version I need or "initial commit porting from StHub!" ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Aug. 5, 2019

A Canticle for Smalltalk

by Richard Kenneth Eng

A big fan of my work created this rogue video: https://drive.google.com/file/d/1opveHaukFK8WbQ8wg8b14wuKJsjoOZfO/view I appreciate the homage, but I can't take credit for it. It's really quite beautiful, though. I'm using it as part of my evangelism.

Aug. 5, 2019

Re: [Pharo-users] Pharo 6.0 and 6.1 64 bit freeze on MacMini -also in 7.03

by TedVanGaalen

Hi Tim, I did that before (see thread history) and other kinds of magic too. Probably (still) a VM error? (because it happens with squeak also, which uses same VM?) However, it is beyond my skills and knowledge No idea how to solve this. The problem has been around for much too long It bounces people away that arrive for the first time at Pharo/Smalltalk. (and they surely won't know about a workaround) When the first simple things they try freezes the whole environment, they'll go away and probably never return. That was then their first and last impression of Smalltalk. TedvG -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Aug. 3, 2019

Re: [Pharo-users] Can I control the location of the PharoDebug.log

by JuliÃ¡n Maestri

I think Smalltalk logFileName: is what you want On Wed, Jul 31, 2019, 20:58 Dale Henrichs <dale.henrichs(a)gemtalksystems.com> wrote: > It appears that the PharoDebug.log can be dropped into the directory > from which a Pharo image is launched ... I would have expected it to be > dropped into the local directory, but that does not appear to be the > case ... > > I've looked in the Settings Browser and there does not appear to be a > way to influence the location of the PharoDebug.log. > > I am currently using the `st` command line handler if that is important. > > I've googled for PharoDebug.log to no avail. > > Any help will be appreciated, > > Dale > > >

Aug. 2, 2019

Re: [Pharo-users] Pharo 6.0 and 6.1 64 bit freeze on MacMini -also in 7.03

by Tim Mackinnon

Out of curiosity - instead of going true âfull screenâ (Iâm assuming you are clicking the green + button), try doing alt+click green button (which just resizes the window full screen), and then try your steps - does that make a difference? I believe there is a full screen issue covered here before - but the resized full screen may be a decent workaround. Tim Sent from my iPhone > On 2 Aug 2019, at 15:24, TedVanGaalen <tedvga(a)gmail.com> wrote: > > To All > (this thread becomes a bit long) > Ca. 4 months later: > Today 2 Aug 2019 I did this: > -downloaded and run Pharo Launcher. > -In the launcher, downloaded and started the fresh Pharo 7.0 64 image > > Pharo then starts up with this image > > (but did it also launch with the most recent VM it could find on the server > or did it take a VM from somewhere on my Mac Mini? > Should I remove all VMs etc. from my Mac? > I did that also 4 months ago but that didn't help either...) > > > In Pharo, all I did was this: > - did go fullscreen (4K), still working. > - selected dark theme from the introduction window. > - Opened "Appearance" menu > - changed the appearance with one click to "Medium" > (now showing readable fonts on my 4K screen) > - changed background to nice blueish gradient. > - selected fullscreen in top menu to toggle back to a window. > Nothing happens and Pharo is frozen again > Forced quit Pharo was the only thing left to do. > > So this is still a problem, leaving me to fall back again to Pharo 5.0 > (Is still OK, but not what I desire. 5.0 is the last version that doesn't do > these things.) > > Kind Regards > TedvG > > > > > > > > > > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >

Aug. 2, 2019

Re: [Pharo-users] Pharo 6.0 and 6.1 64 bit freeze on MacMini -also in 7.03

by TedVanGaalen

To All (this thread becomes a bit long) Ca. 4 months later: Today 2 Aug 2019 I did this: -downloaded and run Pharo Launcher. -In the launcher, downloaded and started the fresh Pharo 7.0 64 image Pharo then starts up with this image (but did it also launch with the most recent VM it could find on the server or did it take a VM from somewhere on my Mac Mini? Should I remove all VMs etc. from my Mac? I did that also 4 months ago but that didn't help either...) In Pharo, all I did was this: - did go fullscreen (4K), still working. - selected dark theme from the introduction window. - Opened "Appearance" menu - changed the appearance with one click to "Medium" (now showing readable fonts on my 4K screen) - changed background to nice blueish gradient. - selected fullscreen in top menu to toggle back to a window. Nothing happens and Pharo is frozen again Forced quit Pharo was the only thing left to do. So this is still a problem, leaving me to fall back again to Pharo 5.0 (Is still OK, but not what I desire. 5.0 is the last version that doesn't do these things.) Kind Regards TedvG -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Aug. 2, 2019

Re: [Pharo-users] Mindmaps and WardleyMaps in Pharo

by Christopher Fuhrman

With the help of several folks in RMoD, the project for PlantUML is now pretty stable. Here's an example with a mind map: https://github.com/fuhrmanator/PlantUMLPharoGizmo#mind-map On Thu, 9 May 2019 at 20:27, Christopher Fuhrman < christopher.fuhrman(a)gmail.com> wrote: > PlantUML now supports mind maps. I am thinking of doing a class in pharo > to use PlantUML on the web to render diagrams (PNG, SVG) in Pharo. > > On Thu, May 9, 2019, 11:46 Rafael Luque <rafael.luque.leiva(a)gmail.com> > wrote: > >> I'm looking for drawing some mindmaps and (obviously) I'd like to be able >> to draw and visualize them inside my own Pharo tools. >> >> I've found this video in Stephan Eggermont's channel: >> >> https://vimeo.com/136943448 >> >> Do you know any other alternatives for Pharo? >> >> BTW, I also found this other video about Wardley maps: >> https://vimeo.com/141653455 >> I found it very interesting. Somebody knows where can I find this project? >> >> Thank you! >> >> >> -- Christopher Fuhrman, P.Eng, PhD *Professor in the DÃ©partement of Software and IT EngineeringÃTS (Ãcole de technologie supÃ©rieure)* http://profs.etsmtl.ca/cfuhrman +1 514 396 8638 *L'ÃTS est une constituante de l'UniversitÃ© du QuÃ©bec* *Confidentiality Notice* This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify christopher.fuhrman(a)etsmtl.ca. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. *Avis de confidentialitÃ©* L'information contenue dans ce message Ã©lectronique ainsi que dans les fichiers qui peuvent y Ãªtre attachÃ©s est de nature confidentielle et destinÃ©e Ã l'usage exclusif du destinataire. Si ce message vous est parvenu par erreur ou que vous n'Ãªtes pas le destinataire visÃ©, vous Ãªtes par la prÃ©sente avisÃ© que tout usage, copie ou distribution de l'information contenue dans ce message est strictement interdit et vous Ãªtes priÃ© d'en aviser christopher.fuhrman(a)etsmtl.ca et de dÃ©truire ce message.

Aug. 1, 2019

Re: [Pharo-users] more fun with System>>Local directory settings

by Dale Henrichs

Thanks for the sample code! ... I keep forgetting that a scan of allInstances is a good way to patch problems like these:) and the fixed to relative path snippet is especially useful. Dale On 8/1/19 1:50 PM, Sean P. DeNigris wrote: > Dale Henrichs-3 wrote >> the act of starting the image automagically populates the System >> local >> directory with a full path to a directory in my current directory > This sounds like the same problem I've been having with absolute resolved > paths to local iceberg repos. Here is the script I use to fix them in a way > that survives image moving and renaming. It should be easy to adapt for your > needs. Obviously it would be better if Pharo didn't resolve the paths in > these cases, but at least there is a workaround. > > fixIcebergRepoLocations > "E.g. after an image is moved or renamed, its local Iceberg repos become > broken because the locations are stored as static FileReferences instead of > dynamic FileLocations following the image around. Limitation: assumes all > images are stored in flat folders under root" > > | imageRoot repos | > imageRoot := FileLocator home / 'Dynabook' / 'Working Images'. > repos := IceLibgitRepository allSubInstances > select: [ :e | > e location isNotNil > and: [ (FileLocator imageDirectory contains: e location) not > and: [ imageRoot contains: e location ] ] ]. > repos > do: [ :e | > | oldPath newPath fixedLocation | > oldPath := e location relativeTo: imageRoot. > newPath := RelativePath withAll: oldPath segments allButFirst. > fixedLocation := FileLocator imageDirectory withPath: newPath. > e location: fixedLocation ] > > > > ----- > Cheers, > Sean > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >

Aug. 1, 2019

Re: [Pharo-users] more fun with System>>Local directory settings

by Sean P. DeNigris

Dale Henrichs-3 wrote > the act of starting the image automagically populates the System >> local > directory with a full path to a directory in my current directory This sounds like the same problem I've been having with absolute resolved paths to local iceberg repos. Here is the script I use to fix them in a way that survives image moving and renaming. It should be easy to adapt for your needs. Obviously it would be better if Pharo didn't resolve the paths in these cases, but at least there is a workaround. fixIcebergRepoLocations "E.g. after an image is moved or renamed, its local Iceberg repos become broken because the locations are stored as static FileReferences instead of dynamic FileLocations following the image around. Limitation: assumes all images are stored in flat folders under root" | imageRoot repos | imageRoot := FileLocator home / 'Dynabook' / 'Working Images'. repos := IceLibgitRepository allSubInstances select: [ :e | e location isNotNil and: [ (FileLocator imageDirectory contains: e location) not and: [ imageRoot contains: e location ] ] ]. repos do: [ :e | | oldPath newPath fixedLocation | oldPath := e location relativeTo: imageRoot. newPath := RelativePath withAll: oldPath segments allButFirst. fixedLocation := FileLocator imageDirectory withPath: newPath. e location: fixedLocation ] ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Aug. 1, 2019