December 2018 - Pharo-users

Re: [Pharo-users] [Moose-dev] Re: glamorous toolkit: v0.4.0

by Tudor Girba

Hi Luke, I am happy this looks exciting :). About the confusion part: The Glamorous Toolkit we are working on right now is a complete new world built on a complete new graphical stack that does is not based on the existing stack that ships with Pharo. It is not an evolution. It is a leap. The goal of the new GT is to propose a completely reshaped programming experience that enables moldable development. You will find the concepts from the old GT in the new world as well. For example, the Inspector is extensible in similar ways and the API is similar as well. But, in the new world, we are bringing the concept much further. For example, Documenter provides a whole new kind of a tool that can mold to unify multiple workflows (like data notebooks, code documentation, or tutorials) right in the IDE. Coder provides the infrastructure for manipulating code that can mold its shape as you type. Transcript allows you to embed various widgets to transform the otherwise dull experience of a console into a live one. Behind the scenes GT comes with several engines. The Examples engine enables example-driven development which also bridges the gap between testing and documentation effort, especially when combined with Documenter. Releaser is able to release deeply nested projects. Phlow offers an engine that shares similarities with Glamour. Completer provides moldable completion. Visualizer offers a couple of visualization engines such as Mondrian. All of these are possible because of the underlying graphical stack made of Sparta/Bloc/Brick. All in all, we believe that the new GT enables a new way of programming. Individual features can be attractive, but our goal is to reshape the development experience. Does this address the concern? Cheers, Doru > On Dec 19, 2018, at 2:09 PM, Luke Gorrie <luke(a)snabb.co> wrote: > > On Fri, 14 Dec 2018 at 05:13, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Please do let us know what you think .. and, of course, what you feel. > > I'm feeling excited and confused :). > > Excited because I love seeing all these new demos streaming out and I'm itching to put new capabilities to work. > > Confused about the roadmap. How does this "new" Glamorous Toolkit relate to the "old" one that I learned about last year from the Moldable Tools thesis? Is this a new version or a complete rewrite? Is it backwards compatible or completely reimagined? Is adopting the new version a seamless process or is porting required? Are frameworks like Glamour still there behind the scenes or were they replaced? etc. > > > <gt-documenter-magic-markup.gif><gt-0-4-0.png>_______________________________________________ > Moose-dev mailing list > Moose-dev(a)list.inf.unibe.ch > https://www.list.inf.unibe.ch/listinfo/moose-dev -- www.feenk.com "Things happen when they happen, not when you talk about them happening."

Dec. 20, 2018

is there a refactoring to combine two classes in a heirarchy?

by PAUL DEBRUICKER

I'd like to combine a class and its subclass, adopting all methods from the subclass. Is there a refactoring rule that will do that?

Dec. 19, 2018

Re: [Pharo-users] GPS / Longitude / Latitude library

by Alistair Grant

Hi All, If anyone is interested, I've created the beginnings of a library for handling coordinates at: https://github.com/akgrant43/GeoSphere It only: - Parses string coordinates - Calculates the distance between coordinates - Opens a web browser in OpenStreetMap at the receiver's coordinates Examples of string formats that can be parsed: - 144.61025 @ -38.28697 - 38Â° 17â² 13.09â³ S, 144Â° 36â² 36.9â³ E - 38 deg 17' 13.09" S, 144 deg 36' 36.9" E - https://www.openstreetmap.org/#map=18/-38.28697/144.61025 The distance calculation uses haversine (assumes the earth is a sphere), which is good enough for my needs at the moment. Thanks again to Sven, Benoit, Pierce and Richard for their input. Cheers, Alistair

Dec. 19, 2018

Re: [Pharo-users] Some issues with Pharo and Ubuntu

by Vitor Medina Cruz

I searched a little bit and it seems there will be no action, and the same problem happened with minidebian, I expect that this will start to happen more as new updates of different linux distros are released with libcurl4. Older software depending on libcurl3 are broking and those who still have maintanace are switching to libcrul4 as well. I think sooner or later pharo will have to migrate as well... On Tue, Dec 18, 2018 at 10:41 AM Vitor Medina Cruz <vitormcruz(a)gmail.com> wrote: > It looks like ubuntu 18.04 does not come with libcurl or they have renamed >> the package. >> Looks also that we are not the only ones that got bit by this: >> https://github.com/atom/github/issues/1680 >> >> Could you try installing curl in your system? >> > > Oh well, I was focusing on the libgir stat thing, but it appears to be a > problem with libcurl as you said... But it don't seems to be solved soon: > https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1754686 and > https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1754294 > > I will stay with ubuntu 16 for now. > > To load the latest Seaside in Pharo 7 I use the develop branch: > > > I don't want to do that as it will make my build non repeatable. It is > fine to load in an image to test, but it can create a number of problems if > used into a dependency configuration. > > Regards, > Vitor > > On Tue, Dec 18, 2018 at 7:39 AM Guillermo Polito < > guillermopolito(a)gmail.com> wrote: > >> Hi, >> >> On Mon, Dec 17, 2018 at 4:38 PM Vitor Medina Cruz <vitormcruz(a)gmail.com> >> wrote: >> >>> Hello, >>> >>> I am trying Pharo with Docker and I will leave here some issues I had >>> since I am unsure where I should report them. >>> >> >> http://bugs.pharo.org should be the correct place. >> >> >>> The command I am running is: >>> >>> Metacello new baseline: 'Employees'; >>> repository: 'tonel:///home/employeesSource/pharo/'; >>> ignoreImage; >>> onConflict: [ :ex | ex useIncoming ]; >>> onWarning: [ :ex | Transcript crShow: ex ]; >>> silently; >>> load: #(core). >>> >>> >>> Ubuntu 16.04, Pharo 61 64bits -> *Ok* >>> >>> Ubuntu 16.04, Pharo 70 64bits -> *Fail* >>> >>> >>> Loaded -> Seaside-Widgets-CompatibleUserName.1544645021 --- https://github.com/SeasideSt/Seaside.git[v3.2.5] --- cache >>> Loaded -> Seaside-RenderLoop-CompatibleUserName.1544645021 --- https://github.com/SeasideSt/Seaside.git[v3.2.5] --- cache >>> Loaded -> Seaside-Tools-Core-CompatibleUserName.1544645021 --- https://github.com/SeasideSt/Seaside.git[v3.2.5] --- cache >>> Please use #base64Decoded now. See issue #21937a MetacelloScriptApiExecutored from ThemeIcons>>#seasideAdaptorRunningIcon has been deprecated. >>> >>> >>> Ubuntu 18.04, Pharo 61|Pharo 70 64bits -> *Fail* >>> >>> Seems like libgit is not found and it try to use one internal, but the >>> link is broken. >>> >>> Fetched -> BaselineOfEmployees-tonel.1 --- tonel:///home/employeesSource/pharo --- tonel:///home/employeesSource/pharo >>> Loaded -> BaselineOfEmployees-tonel.1 --- tonel:///home/employeesSource/pharo --- tonel:///home/employeesSource/pharo >>> Loading baseline of BaselineOfEmployees...ioLoadModule(/opt/pharo/pharo-vm/lib/pharo/5.0-201806281256/libgit2.so): >>> libcurl-gnutls.so.4: cannot open shared object file: No such file or directory >>> ioLoadModule(/opt/pharo/pharo-vm/lib/pharo/5.0-201806281256/libgit2.so): >>> libcurl-gnutls.so.4: cannot open shared object file: No such file or directory >>> tryLoading(/opt/pharo/pharo-vm/lib/pharo/5.0-201806281256/libgit2.so/.libs/,libgit2.so): stat(/opt/pharo/pharo-vm/lib/pharo/5.0-201806281256/libgit2.so/.libs/) Not a directory >>> [31mError: External module not found >>> [0mExternalLibraryFunction(Object)>>error: >>> ExternalLibraryFunction(Object)>>externalCallFailed >>> ExternalLibraryFunction(ExternalFunction)>>invokeWithArguments: >>> LGitLibrary>>libgit2_init >>> FFICalloutAPI>>function:module: >>> LGitLibrary(Object)>>ffiCall: >>> LGitLibrary>>libgit2_init >>> LGitLibrary>>initializeLibGit2 >>> LGitGlobal class>>checkInitialized >>> >>> It looks like ubuntu 18.04 does not come with libcurl or they have >> renamed the package. >> Looks also that we are not the only ones that got bit by this: >> https://github.com/atom/github/issues/1680 >> >> Could you try installing curl in your system? >> >> Tx, >> Guille >> >

Dec. 18, 2018

Re: [Pharo-users] Package Install problematic

by Sven Van Caekenberghe

To load the latest Seaside in Pharo 7 I use the develop branch: Metacello new baseline:'Seaside3'; repository: 'github://SeasideSt/Seaside:develop/repository'; load. In any case you need this recent commit https://github.com/SeasideSt/Seaside/commit/fd2887df520505520d5bb7fbf37c2f8… which seems to be on master as well > On 18 Dec 2018, at 15:18, dario.trussardi(a)tiscali.it wrote: > > Ciao, > > after a Pharo 7.0 - 64 bit crash, > > for now irrecoverable, > > where i lose some works......... ( i'm not happy for some days ). > > I'm trying to set up a new image. > > But..... > > Because i think to messed up on /home/party/Pharo/images/Pharo 7.0 - 64bit (development version) > > i rename it. > > After with the command: wget -O- https://get.pharo.org/64/70+vm | bash > > i create new lonely /opt/pharo7.0.0rc1b57 build 57 image > > With this command the system create a new directory: /home/party/Pharo/images/Pharo 7.0 - 64bit (development version) > > > Into Iceberg i import my local existing entry repository: > > Seaside master 9566cb4 add MetacelloAllowLockedProjectChange handling > > When on this repository i do the Metacello Install baseline of Seaside3 (default) > > the system open a Window with titled: > > Could not resolve: ConfigurationOfZincHTTPComponents [ConfigurationOfZincHTTPComponents] in /home/party/Pharo/images/Pharo 7.0 - 64bit (development version)/pharo-local/package-cache http://mc.stfx.eu/ZincHTTPComponents > > > The Metacello report a package entry with: > > BaselineOfSeaside3 (CompatibleUserName.1537724254) > > with repository set to: /home/party/Pharo/images/Pharo 7.0 - 64bit (development version)/pharo-local/package-cache > > > Why this situation? > > Considerations? > > Thanks, > > Dario > >

Dec. 18, 2018

Package Install problematic

by dario.trussardi＠tiscali.it

Ciao, Â Â Â after a Pharo 7.0 - 64 bitÂ Â Â crash, Â Â Â for now irrecoverable, Â Â Â where i lose some works......... ( i'm not happy for some days ). Â Â Â I'm trying to set up a new image. Â Â Â But..... Â Â Â Â BecauseÂ i think to messed up on /home/party/Pharo/images/Pharo 7.0 - 64bit (development version) Â Â Â Â Â Â i rename it. Â Â Â Â Â After with the command:Â Â Â wget -O- https://get.pharo.org/64/70+vm | bash Â Â Â Â Â Â Â Â Â i create new lonelyÂ Â Â /opt/pharo7.0.0rc1b57 build 57Â image Â Â Â Â Â Â With this command the system create a new directory: /home/party/Pharo/images/Pharo 7.0 - 64bit (development version) Â Â Â Â Â Â Into Iceberg i Â Â Â import Â Â Â my local existing entry repository: Â Â Â Â Â Â Â Â Â Seaside Â Â Â master 9566cb4 add MetacelloAllowLockedProjectChange handling Â Â Â When on this repository i do theÂ Â Â Â Â Â Metacello Install baseline of Seaside3 (default) Â Â Â Â Â Â the system open a Window with titled: Â Â Â Â Â Â Â Â Â Â Â Â Could not resolve: ConfigurationOfZincHTTPComponents [ConfigurationOfZincHTTPComponents] in /home/party/Pharo/images/Pharo 7.0 - 64bit (development version)/pharo-local/package-cache http://mc.stfx.eu/ZincHTTPComponents Â Â Â The Metacello report a package entry with: Â Â Â Â Â Â Â Â Â Â Â Â BaselineOfSeaside3 (CompatibleUserName.1537724254) Â Â Â Â Â Â Â with repository set to: /home/party/Pharo/images/Pharo 7.0 - 64bit (development version)/pharo-local/package-cache Â Why this situation? Â Â Â Considerations? Â Â Â Â Â Â Thanks, Â Â Â Â Â Â Â Â Â Dario

Dec. 18, 2018

Re: [Pharo-users] Some issues with Pharo and Ubuntu

by Vitor Medina Cruz

> > It looks like ubuntu 18.04 does not come with libcurl or they have renamed > the package. > Looks also that we are not the only ones that got bit by this: > https://github.com/atom/github/issues/1680 > > Could you try installing curl in your system? > Oh well, I was focusing on the libgir stat thing, but it appears to be a problem with libcurl as you said... But it don't seems to be solved soon: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1754686 and https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1754294 I will stay with ubuntu 16 for now. To load the latest Seaside in Pharo 7 I use the develop branch: I don't want to do that as it will make my build non repeatable. It is fine to load in an image to test, but it can create a number of problems if used into a dependency configuration. Regards, Vitor On Tue, Dec 18, 2018 at 7:39 AM Guillermo Polito <guillermopolito(a)gmail.com> wrote: > Hi, > > On Mon, Dec 17, 2018 at 4:38 PM Vitor Medina Cruz <vitormcruz(a)gmail.com> > wrote: > >> Hello, >> >> I am trying Pharo with Docker and I will leave here some issues I had >> since I am unsure where I should report them. >> > > http://bugs.pharo.org should be the correct place. > > >> The command I am running is: >> >> Metacello new baseline: 'Employees'; >> repository: 'tonel:///home/employeesSource/pharo/'; >> ignoreImage; >> onConflict: [ :ex | ex useIncoming ]; >> onWarning: [ :ex | Transcript crShow: ex ]; >> silently; >> load: #(core). >> >> >> Ubuntu 16.04, Pharo 61 64bits -> *Ok* >> >> Ubuntu 16.04, Pharo 70 64bits -> *Fail* >> >> >> Loaded -> Seaside-Widgets-CompatibleUserName.1544645021 --- https://github.com/SeasideSt/Seaside.git[v3.2.5] --- cache >> Loaded -> Seaside-RenderLoop-CompatibleUserName.1544645021 --- https://github.com/SeasideSt/Seaside.git[v3.2.5] --- cache >> Loaded -> Seaside-Tools-Core-CompatibleUserName.1544645021 --- https://github.com/SeasideSt/Seaside.git[v3.2.5] --- cache >> Please use #base64Decoded now. See issue #21937a MetacelloScriptApiExecutored from ThemeIcons>>#seasideAdaptorRunningIcon has been deprecated. >> >> >> Ubuntu 18.04, Pharo 61|Pharo 70 64bits -> *Fail* >> >> Seems like libgit is not found and it try to use one internal, but the >> link is broken. >> >> Fetched -> BaselineOfEmployees-tonel.1 --- tonel:///home/employeesSource/pharo --- tonel:///home/employeesSource/pharo >> Loaded -> BaselineOfEmployees-tonel.1 --- tonel:///home/employeesSource/pharo --- tonel:///home/employeesSource/pharo >> Loading baseline of BaselineOfEmployees...ioLoadModule(/opt/pharo/pharo-vm/lib/pharo/5.0-201806281256/libgit2.so): >> libcurl-gnutls.so.4: cannot open shared object file: No such file or directory >> ioLoadModule(/opt/pharo/pharo-vm/lib/pharo/5.0-201806281256/libgit2.so): >> libcurl-gnutls.so.4: cannot open shared object file: No such file or directory >> tryLoading(/opt/pharo/pharo-vm/lib/pharo/5.0-201806281256/libgit2.so/.libs/,libgit2.so): stat(/opt/pharo/pharo-vm/lib/pharo/5.0-201806281256/libgit2.so/.libs/) Not a directory >> [31mError: External module not found >> [0mExternalLibraryFunction(Object)>>error: >> ExternalLibraryFunction(Object)>>externalCallFailed >> ExternalLibraryFunction(ExternalFunction)>>invokeWithArguments: >> LGitLibrary>>libgit2_init >> FFICalloutAPI>>function:module: >> LGitLibrary(Object)>>ffiCall: >> LGitLibrary>>libgit2_init >> LGitLibrary>>initializeLibGit2 >> LGitGlobal class>>checkInitialized >> >> It looks like ubuntu 18.04 does not come with libcurl or they have > renamed the package. > Looks also that we are not the only ones that got bit by this: > https://github.com/atom/github/issues/1680 > > Could you try installing curl in your system? > > Tx, > Guille >

Dec. 18, 2018

Re: [Pharo-users] Some issues with Pharo and Ubuntu

by Guillermo Polito

Hi, On Mon, Dec 17, 2018 at 4:38 PM Vitor Medina Cruz <vitormcruz(a)gmail.com> wrote: > Hello, > > I am trying Pharo with Docker and I will leave here some issues I had > since I am unsure where I should report them. > http://bugs.pharo.org should be the correct place. > The command I am running is: > > Metacello new baseline: 'Employees'; > repository: 'tonel:///home/employeesSource/pharo/'; > ignoreImage; > onConflict: [ :ex | ex useIncoming ]; > onWarning: [ :ex | Transcript crShow: ex ]; > silently; > load: #(core). > > > Ubuntu 16.04, Pharo 61 64bits -> *Ok* > > Ubuntu 16.04, Pharo 70 64bits -> *Fail* > > > Loaded -> Seaside-Widgets-CompatibleUserName.1544645021 --- https://github.com/SeasideSt/Seaside.git[v3.2.5] --- cache > Loaded -> Seaside-RenderLoop-CompatibleUserName.1544645021 --- https://github.com/SeasideSt/Seaside.git[v3.2.5] --- cache > Loaded -> Seaside-Tools-Core-CompatibleUserName.1544645021 --- https://github.com/SeasideSt/Seaside.git[v3.2.5] --- cache > Please use #base64Decoded now. See issue #21937a MetacelloScriptApiExecutored from ThemeIcons>>#seasideAdaptorRunningIcon has been deprecated. > > > Ubuntu 18.04, Pharo 61|Pharo 70 64bits -> *Fail* > > Seems like libgit is not found and it try to use one internal, but the > link is broken. > > Fetched -> BaselineOfEmployees-tonel.1 --- tonel:///home/employeesSource/pharo --- tonel:///home/employeesSource/pharo > Loaded -> BaselineOfEmployees-tonel.1 --- tonel:///home/employeesSource/pharo --- tonel:///home/employeesSource/pharo > Loading baseline of BaselineOfEmployees...ioLoadModule(/opt/pharo/pharo-vm/lib/pharo/5.0-201806281256/libgit2.so): > libcurl-gnutls.so.4: cannot open shared object file: No such file or directory > ioLoadModule(/opt/pharo/pharo-vm/lib/pharo/5.0-201806281256/libgit2.so): > libcurl-gnutls.so.4: cannot open shared object file: No such file or directory > tryLoading(/opt/pharo/pharo-vm/lib/pharo/5.0-201806281256/libgit2.so/.libs/,libgit2.so): stat(/opt/pharo/pharo-vm/lib/pharo/5.0-201806281256/libgit2.so/.libs/) Not a directory > [31mError: External module not found > [0mExternalLibraryFunction(Object)>>error: > ExternalLibraryFunction(Object)>>externalCallFailed > ExternalLibraryFunction(ExternalFunction)>>invokeWithArguments: > LGitLibrary>>libgit2_init > FFICalloutAPI>>function:module: > LGitLibrary(Object)>>ffiCall: > LGitLibrary>>libgit2_init > LGitLibrary>>initializeLibGit2 > LGitGlobal class>>checkInitialized > > It looks like ubuntu 18.04 does not come with libcurl or they have renamed the package. Looks also that we are not the only ones that got bit by this: https://github.com/atom/github/issues/1680 Could you try installing curl in your system? Tx, Guille

Dec. 18, 2018

Re: [Pharo-users] what is wrong here. Tests are green but the outcome with real code is much to high

by Roelof Wobben

Dec. 18, 2018

Re: [Pharo-users] Teapot installation

by Renaud de Villemeur

Hi Teapot has been moved from smalltalkhub to github. The new location is https://github.com/zeroflag/Teapot You can have a look at the doc on how to install it, either standalone or as a dependency. https://github.com/zeroflag/Teapot/blob/master/docs/Installation.md Renaud Le lun. 17 dÃ©c. 2018 Ã 20:30, horrido <horrido.hobbies(a)gmail.com> a Ã©crit : > /Something/ has recently changed. The following now incurs an error: > > Gofer it > smalltalkhubUser: 'zeroflag' project: 'Teapot'; > configuration; > loadStable. > > The error is: "Could not resolve: ConfigurationOfNeoJSON in > /home/richard/blah blah blah" > > What's going on??? > > > > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html > >

Dec. 18, 2018