- Pharo-users - lists.pharo.org

Progress bar for ZnClient>>#downloadTo:
by Ben Coman April 13, 2018

April 13, 2018

I see ZnClient >> downloadTo: calls ZnClient >> downloadEntityTo: which uses #withProgressDo: which indicates a progress bar might appear. But... ZnClient new url: ' https://download.libsodium.org/libsodium/releases/ libsodium-1.0.16-msvc.zip' ; downloadTo: FileLocator imageDirectory. doesn't show a progress bar. What is the recommended way to display one? cheers -ben

3 5

Re: [Pharo-users] Where do we go now ?
by ClÃ©ment Bera April 13, 2018

April 13, 2018

"Alpha software can be unstable and could cause crashes or data loss" [1] Experiencing instability, crashes and data loss in the alpha version of a software, including Pharo alpha, is to be expected and nothing to be surprised about. The support of the Pharo stable version (currently 6.1) has significantly improved in the past year. Many fixes and enhancements were back-ported from Pharo 7 to Pharo 6.1. Based on your comments, it seems that you have issues because you are not using the version of Pharo that fits your needs (i.e. the stable version). Checking the Pharo website [2], it seems there are *no* download links to the alpha version so far because it's not considered stable enough. Where did you get a link to download Pharo 7 alpha ? [1] https://en.wikipedia.org/wiki/Software_release_life_cycle [2] https://pharo.org/download On Fri, Apr 13, 2018 at 11:26 AM, Benoit St-Jean via Pharo-users < pharo-users(a)lists.pharo.org> wrote: > > > ---------- Forwarded message ---------- > From: Benoit St-Jean <bstjean(a)yahoo.com> > To: Esteban Lorenzano <estebanlm(a)gmail.com> > Cc: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> > Bcc: > Date: Fri, 13 Apr 2018 09:26:09 +0000 (UTC) > Subject: Re: [Pharo-users] Where do we go now ? > BTW, why put an .exe installer for Windows available when it crashes right > from the start? It just doesn't work at all. Period. For everyone. > > And I thought looking for senders of a method was something we mastered a > long time ago, like starting with Smalltalk-76. Am I supposed to assume > that everything, even basic functionalities, are all broken because it's > labeled "alpha" ? > > > ----------------- > BenoÃ®t St-Jean > Yahoo! Messenger: bstjean > Twitter: @BenLeChialeux > Pinterest: benoitstjean > Instagram: Chef_Benito > IRC: lamneth > Blogue: endormitoire.wordpress.com > "A standpoint is an intellectual horizon of radius zero". (A. Einstein) > > > On Friday, April 13, 2018, 5:20:28 a.m. EDT, Esteban Lorenzano < > estebanlm(a)gmail.com> wrote: > > > > > On 13 Apr 2018, at 11:07, Benoit St-Jean <bstjean(a)yahoo.com> wrote: > > I'm on Windows 10, using Pharo 7.0 alpha 32 bit. > > > and btwâ¦ which part of ALPHA you do not get? > > Esteban > > -- ClÃ©ment BÃ©ra https://clementbera.github.io/ https://clementbera.wordpress.com/

1 0

Re: [Pharo-users] Where do we go now ?
by Cyril Ferlicot D. April 13, 2018

April 13, 2018

On 13/04/2018 11:26, Benoit St-Jean via Pharo-users wrote: Do you expect a cleaning of the Kernel without any break during alpha version? This version introduce a new message browser, new Traits, more modularization of the kernel and some cleaning of the Kernel. I see a lot of reason why it might break during the alpha version. -- Cyril Ferlicot https://ferlicot.fr

1 0

Re: [Pharo-users] Where do we go now ?
by Cyril Ferlicot D. April 13, 2018

April 13, 2018

On 13/04/2018 11:07, Benoit St-Jean via Pharo-users wrote: "Can I at least expect to be able to save code in my local Monticello repository ? It bombs. I just reported a bug!" "Can I expect that when looking for implementors of a method things still work? I get duplicates (see attached file)." => The meaning of alpha is that things like this can happen often. Else it would be a beta or a release version. But if you stick to use it, the bug reports are really welcomed! For the windows launcher indeed there is weird behaviour and Christophe is working on it when he gets bug reports. (https://github.com/pharo-project/pharo-launcher/issues) "Can I expect reading input from the console to work on Windows? It doesn't." What do you mean by that? Having Pharo running and the user sending input from it's CMD? I never saw an application doing that on windows. "Can I expect to be able to contribute ? That is kinda sad but all the cool scripts out there are .sh files." Which scripts? I contribute to Pharo from windows 7 and windows 10 without any script. Sometimes I have some troubles but it's only natural during the version that change all the contribution process the time it stabilize. If you have troubles on windows can you open issues please? Because most of the time I see that people complain about some bugs but some of those bugs never got a bug report. -- Cyril Ferlicot https://ferlicot.fr

1 0

Re: [Pharo-users] Where do we go now ?
by Cyril Ferlicot D. April 13, 2018

April 13, 2018

On 13/04/2018 07:53, Benoit St-Jean via Pharo-users wrote: Hi, I don't have time to answer to everything but I can give some details: - Nautilus will be removed when Calypso will be really stable (During the Calypso development if calypso breaks, you need an other browser to replace it) - The old compiler will be removed as an external project (https://github.com/pharo-project/pharo-workingRoadmaps/blob/master/Pharo7/R…) - I think it's planned to remove the EyeInspector - Kommiter and Versionner will also be removed in next versions of Pharo "Pharo 5.1 had 5885 classes. Pharo 6.1 had 6481 classes. Pharo 7.0 alpha has 7612 classes." In general I do not like metrics in term of number of classes because I prefer a system with 7500 classes of 50 lines of code than a system of 6000 classes of 300 lines of codes. "Pharo 5.1 had 416 preference settings. Pharo 6.1 had 494 preference settings. Pharo 7.0 alpha has 662 preference settings." The number of settings is not a bad thing if it's well organized. The current problem is not the number of settings, it's more their organization. Have a nice day. :) -- Cyril Ferlicot https://ferlicot.fr

2 1

Frozen at start up
by Hilaire April 12, 2018

April 12, 2018

Hi, I have this strange situation with a DrGeo built against P7, where DrGeo starts, but then get frozen with this message. Strangely the start seems not to have completed as the UI messages are not localized in French. What is strange, on my PC where I built the app, this problem does not occur. Any idea? Thanks Hilaire -- Dr. Geo http://drgeo.eu

4 12

To be there or not to be there
by Hilaire April 12, 2018

April 12, 2018

Hello, I have re-organized the packages and classes in DrGeo with Calypso. An now I come to a situation where methods seems to be there without been there. For example DrGeoWindow>>newTable: methods, - Calypso can browse it and can show its implementor - Nautilus can browse it and can NOT show its implementor - and more importantly when exported to tonel file, it is missing ! Who knows what else methods are missing. See screenshot. Any idea? Hilaire -- Dr. Geo http://drgeo.eu

4 9

installation of packages on 6.1
by Baveco, Hans April 12, 2018

April 12, 2018

Trying to install Territorial the installation got stuck on the installation of Roassal2 1.35, with error "LGitObjectNotInitialized" Transcript says: "Project: Roassal2 1.35 I got an error while cloning: There was an authentication error while trying to execute the operation: error authenticating: failed connecting agent. This happens usually because you didn't provide a valid set of credentials. You may fix this problem in different ways: 1. adding your keys to ssh-agent, executing ssh-add ~/.ssh/id_rsa in your command line. 2. adding your keys in settings (open settings browser search for "Use custom SSH keys" and add your public and private keys). 3. using HTTPS instead SSH (Just use an url in the form HTTPS://etc.git) I will try to clone the HTTPS variant." I have encountered this several times before, for different packages (on windows 7, pharo 6.1 (Image: Pharo6.0 [Latest update: #60540])) and have no idea how to deal with this. Any suggestions? Hans

8 14

Quick website fix
by Markus Fritsche April 12, 2018

April 12, 2018

Hi, it says on "https://pharo.org/contribute-propose-fix" that Manuscript used to be called "Fugbugz" - although an understandable mistake, I believe it was called "Fogbugz" :-) Kind regards Â Markus

2 1

migration to 6.1 was super easy.
by PAUL DEBRUICKER April 12, 2018

April 12, 2018

Thanks for all the hard work. It took me about 30 minutes to migrate one of my projects from 32bit Pharo 5 to 64bit 6.1 this afternoon. It has about 40 external dependencies so I thought it would take much longer to get everything sorted.

2 1