July 2016 - Pharo-users - lists.pharo.org

Re: [Pharo-users] Image not starting

by Nicolai Hess

2016-07-18 14:36 GMT+02:00 Valentin Ryckewaert < valentin.ryckewaert(a)gmail.com>: > Hello, > > with Pavel we tried to print with a lot of methods but it didn't work, i'm > searching the source of the problem manually. > What do you mean witth: "tried to print with a lot of methods" ? You can not use stdout to print when doing image shutdown and restart, because all file streams will be closed during the shutdown (see session manager). If you want to use stdout to print log messages (right after image startup), you need to make sure that the stdout/err stream are already recreated. (And for example, reinitialize Coral, if coral has reference to the (old) closed filestream. > > 2016-07-18 14:32 GMT+02:00 stepharo <stepharo(a)free.fr>: > >> Thanks for the suggestion. It is probably the case. >> >> Le 17/7/16 Ã 23:27, Nicolai Hess a Ã©crit : >> >> Hi Valentin, Ithink you can not print to stdout during shutdown and >> restart. >> It will end in a Loop of writing to stdout, throwing an exceptions >> because it can not write and trying to log the error on stdout, throwing an >> error... >> >> Am 17.07.2016 18:36 schrieb "Valentin Ryckewaert" < >> valentin.ryckewaert(a)gmail.com>: >> >>> i will do it tomorrow. >>> >>> 2016-07-17 17:23 GMT+02:00 stepharo <stepharo(a)free.fr>: >>> >>>> did you try to solution proposed? >>>> >>>> Stef >>>> >>>> Le 17/7/16 Ã 16:22, Valentin Ryckewaert a Ã©crit : >>>> >>>> Hello Stef, >>>> >>>> no i'm still on it :( >>>> I'm going to test every code I modified >>>> >>>> Valentin >>>> >>>> 2016-07-17 15:23 GMT+02:00 stepharo <stepharo(a)free.fr>: >>>> >>>>> HI valentin >>>>> >>>>> >>>>> did you solve your problem? >>>>> >>>>> >>>>> Stef >>>>> >>>>> Le 12/7/16 Ã 15:33, Valentin Ryckewaert a Ã©crit : >>>>> >>>>> Hello everyone, >>>>> >>>>> I'm currently working on the project file policy and I'm having a >>>>> problem that I don't understand >>>>> >>>>> I import my code, configure my image as readOnly (Pharo won't try to >>>>> write on changesFiles,source,image....), set the folder of the image in >>>>> readonly and try to open the image again and it's not possible, I don't get >>>>> any stacktrace so it's hard to understand the problem. >>>>> >>>>> PS : If we set back the folder in write mode, it's possible again to >>>>> open the image again. >>>>> >>>>> Here is the code to reproduce the bug, could someone give me a clue >>>>> please? >>>>> >>>>> sudo rm -r testPharo >>>>> mkdir testPharo >>>>> cd testPharo >>>>> >>>>> echo "Metacello new >>>>> smalltalkhubUser: 'Uryon' project: 'Coral'; >>>>> configuration: 'Coral'; >>>>> version: #development; >>>>> onConflictUseIncoming; >>>>> load. >>>>> SmalltalkImage configureSystemAsReadonlyAndQuit:true >>>>> " >> load.st >>>>> >>>>> mkdir coral >>>>> cd coral >>>>> curl get.pharo.org/alpha | bash >>>>> curl get.pharo.org/vm60 | bash >>>>> pharo-vm/pharo Pharo.image ../load.st >>>>> cd .. >>>>> chmod -R -w coral >>>>> coral/pharo-vm/pharo coral/Pharo.image >>>>> >>>>> >>>>> >>>> >>>> >>> >> >

July 18, 2016

Re: [Pharo-users] [ANN] Metacello support for GitFileTree metadata-less mode

by Dale Henrichs

On 07/17/2016 11:19 AM, Cyril Ferlicot D. wrote: > Le 14/07/2016 Ã 21:49, Dale Henrichs a Ã©crit : >> Depending on the version of Pharo you are using, at some point in time, >> I expect this new release of Metacello to be available in the standard >> download. Until then, to install the latest version of Metacello into >> Pharo execute the following in a workspace: >> >> Metacello new >> baseline: 'Metacello'; >> repository: 'github://dalehenrich/metacello-work:master/repository'; >> get. >> Metacello new >> baseline: 'Metacello'; >> repository: 'github://dalehenrich/metacello-work:master/repository'; >> onConflict: [:ex | ex allow]; >> load >> > Hi Dale, > > When I try to upgrade Metacello in the latest Pharo 6 I get an error > "receiver of withSqueakLineEnding is nil" > > See: http://puu.sh/q3zet/310f6d3086.png > Hello Cyril, This appears to be related to the fact that the class comment file (README.md) is unexpectedly missing from your download ... Since the file is present on GitHub[1] ... perhaps the download from failed in an odd way without triggering an error leading to this problem ... I would have expected an incomplete download error along the way --- if you still have a copy of the Transcript a download error message should be present ... Retrying the git get/load might get a good result ... Dale [1] https://github.com/dalehenrich/metacello-work/tree/master/repository/Baseli… https://github.com/dalehenrich/filetree/blob/pharo6.0_dev/repository/Montic…

July 18, 2016

Re: [Pharo-users] How learning Smalltalk can make you a better developer

by Ben Coman

On Mon, Jul 18, 2016 at 9:19 PM, horrido <horrido.hobbies(a)gmail.com> wrote: > A new article on Smalltalk has been published at TechBeacon: How learning > Smalltalk can make you a better developer > <http://techbeacon.com/how-learning-smalltalk-can-make-you-better-developer> > . Hopefully, it will go viral. Good to see a nicely balanced article from you. Only thing I'd change is from " widely perceived" to "sometimes perceived". Don't dig a hole too deep that you later talk your way out of ;) You might consider linking at the end to some videos of opinions from people from outside the Smalltalk community... MountainWest RubyConf 2014 - But Really, You Should Learn Smalltalk https://www.youtube.com/watch?v=eGaKZBr0ga4 In which I make you hate Ruby in 7 minutes http://www.virtuouscode.com/2015/05/11/in-which-i-make-you-hate-ruby-in-7-m… cheers -ben

July 18, 2016

How learning Smalltalk can make you a better developer

by horrido

A new article on Smalltalk has been published at TechBeacon: How learning Smalltalk can make you a better developer <http://techbeacon.com/how-learning-smalltalk-can-make-you-better-developer> . Hopefully, it will go viral. -- View this message in context: http://forum.world.st/How-learning-Smalltalk-can-make-you-a-better-develope… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

July 18, 2016

Re: [Pharo-users] Image not starting

by Valentin Ryckewaert

Hello, with Pavel we tried to print with a lot of methods but it didn't work, i'm searching the source of the problem manually. 2016-07-18 14:32 GMT+02:00 stepharo <stepharo(a)free.fr>: > Thanks for the suggestion. It is probably the case. > > Le 17/7/16 Ã 23:27, Nicolai Hess a Ã©crit : > > Hi Valentin, Ithink you can not print to stdout during shutdown and > restart. > It will end in a Loop of writing to stdout, throwing an exceptions because > it can not write and trying to log the error on stdout, throwing an error... > > Am 17.07.2016 18:36 schrieb "Valentin Ryckewaert" < > valentin.ryckewaert(a)gmail.com>: > >> i will do it tomorrow. >> >> 2016-07-17 17:23 GMT+02:00 stepharo <stepharo(a)free.fr>: >> >>> did you try to solution proposed? >>> >>> Stef >>> >>> Le 17/7/16 Ã 16:22, Valentin Ryckewaert a Ã©crit : >>> >>> Hello Stef, >>> >>> no i'm still on it :( >>> I'm going to test every code I modified >>> >>> Valentin >>> >>> 2016-07-17 15:23 GMT+02:00 stepharo <stepharo(a)free.fr>: >>> >>>> HI valentin >>>> >>>> >>>> did you solve your problem? >>>> >>>> >>>> Stef >>>> >>>> Le 12/7/16 Ã 15:33, Valentin Ryckewaert a Ã©crit : >>>> >>>> Hello everyone, >>>> >>>> I'm currently working on the project file policy and I'm having a >>>> problem that I don't understand >>>> >>>> I import my code, configure my image as readOnly (Pharo won't try to >>>> write on changesFiles,source,image....), set the folder of the image in >>>> readonly and try to open the image again and it's not possible, I don't get >>>> any stacktrace so it's hard to understand the problem. >>>> >>>> PS : If we set back the folder in write mode, it's possible again to >>>> open the image again. >>>> >>>> Here is the code to reproduce the bug, could someone give me a clue >>>> please? >>>> >>>> sudo rm -r testPharo >>>> mkdir testPharo >>>> cd testPharo >>>> >>>> echo "Metacello new >>>> smalltalkhubUser: 'Uryon' project: 'Coral'; >>>> configuration: 'Coral'; >>>> version: #development; >>>> onConflictUseIncoming; >>>> load. >>>> SmalltalkImage configureSystemAsReadonlyAndQuit:true >>>> " >> load.st >>>> >>>> mkdir coral >>>> cd coral >>>> curl get.pharo.org/alpha | bash >>>> curl get.pharo.org/vm60 | bash >>>> pharo-vm/pharo Pharo.image ../load.st >>>> cd .. >>>> chmod -R -w coral >>>> coral/pharo-vm/pharo coral/Pharo.image >>>> >>>> >>>> >>> >>> >> >

July 18, 2016

Re: [Pharo-users] Shortcuts for navigation history in Pharo5

by stepharo

Hi ben It is better to copy the fix in both repositories. Stef Le 18/7/16 Ã 11:53, Ben Coman a Ã©crit : > Thanks Davide. If its not too much trouble and you'd like to learn a > bit more about the contribution process, could you submit your fix > following the instructions at [1]. Create two issues, one with > Milestone=Pharo5, and a subcase with Milestone=Pharo6. Policy is for > fixes to be integrated to Pharo 6 first, then back ported to Pharo5. > > [1] http://pharo.org/contribute-propose-fix > > cheers -ben > > P.S. @admins, should [1] be updated from Pharo50Inbox to Pharo60Inbox ? > > > On Mon, Jul 18, 2016 at 4:15 PM, Davide Varvello via Pharo-users > <pharo-users(a)lists.pharo.org> wrote: >> >> ---------- Forwarded message ---------- >> From: Davide Varvello <varvello(a)yahoo.com> >> To: pharo-users(a)lists.pharo.org >> Cc: >> Date: Mon, 18 Jul 2016 00:31:32 -0700 (PDT) >> Subject: Re: Shortcuts for navigation history in Pharo5 >> Hi Stef, >> >> I was wrong, the descriptions exist in the Keymap Browser, but their >> shortcut name are "next" and "previous". >> A better name is #goBackInTheNavigationHistory and >> #goForwardInTheNavigationHistory >> >> so the selector could be >> NautilusUI class>>buildHistoryShortcutsOn: aBuilder >> <keymap> >> >> (aBuilder shortcut: #goBackInTheNavigationHistory) >> category: #NautilusGlobalShortcuts >> default: $[ meta shift >> do: [:target| target previous ] >> description: 'Go back in the navigation history.'. >> >> (aBuilder shortcut: #goForwardInTheNavigationHistory) >> category: #NautilusGlobalShortcuts >> default: $] meta shift >> do: [:target| target next ] >> description: 'Go forward in the navigation history'. >> >> >> Davide >> >> >> stepharo wrote >>> Hi Davide >>> >>> add them to the description and send us a fix. >>> >>> Stef >> >> >> >> >> -- >> View this message in context: http://forum.world.st/Shortcuts-for-navigation-history-in-Pharo5-tp4906689p… >> Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. >> >> >

July 18, 2016

Re: [Pharo-users] Image not starting

by stepharo

Thanks for the suggestion. It is probably the case. Le 17/7/16 Ã 23:27, Nicolai Hess a Ã©crit : > > Hi Valentin, Ithink you can not print to stdout during shutdown and > restart. > It will end in a Loop of writing to stdout, throwing an exceptions > because it can not write and trying to log the error on stdout, > throwing an error... > > > Am 17.07.2016 18:36 schrieb "Valentin Ryckewaert" > <valentin.ryckewaert(a)gmail.com <mailto:valentin.ryckewaert@gmail.com>>: > > i will do it tomorrow. > > 2016-07-17 17:23 GMT+02:00 stepharo <stepharo(a)free.fr > <mailto:stepharo@free.fr>>: > > did you try to solution proposed? > > Stef > > > Le 17/7/16 Ã 16:22, Valentin Ryckewaert a Ã©crit : >> Hello Stef, >> >> no i'm still on it :( >> I'm going to test every code I modified >> >> Valentin >> >> 2016-07-17 15:23 GMT+02:00 stepharo <stepharo(a)free.fr >> <mailto:stepharo@free.fr>>: >> >> HI valentin >> >> >> did you solve your problem? >> >> >> Stef >> >> >> Le 12/7/16 Ã 15:33, Valentin Ryckewaert a Ã©crit : >>> Hello everyone, >>> >>> I'm currently working on the project file policy and I'm >>> having a problem that I don't understand >>> >>> I import my code, configure my image as readOnly (Pharo >>> won't try to write on changesFiles,source,image....), >>> set the folder of the image in readonly and try to open >>> the image again and it's not possible, I don't get any >>> stacktrace so it's hard to understand the problem. >>> >>> PS : If we set back the folder in write mode, it's >>> possible again to open the image again. >>> >>> Here is the code to reproduce the bug, could someone >>> give me a clue please? >>> >>> sudo rm -r testPharo >>> mkdir testPharo >>> cd testPharo >>> >>> echo "Metacello new >>> smalltalkhubUser: 'Uryon' project: 'Coral'; >>> configuration: 'Coral'; >>> version: #development; >>> onConflictUseIncoming; >>> load. >>> SmalltalkImage configureSystemAsReadonlyAndQuit:true >>> " >> load.st <http://load.st> >>> >>> mkdir coral >>> cd coral >>> curl get.pharo.org/alpha <http://get.pharo.org/alpha> | >>> bash >>> curl get.pharo.org/vm60 <http://get.pharo.org/vm60> | bash >>> pharo-vm/pharo Pharo.image ../load.st <http://load.st> >>> cd .. >>> chmod -R -w coral >>> coral/pharo-vm/pharo coral/Pharo.image >>> >> >> > >

July 18, 2016

Re: [Pharo-users] Spec, Icons in subclasses of ComposableModel

by Peter UhnÃ¡k

In that case it should be either self iconNamed: #smallBackIcon or #smallBackIcon asIcon that is â to avoid directly asking global singletons. This is similar to Theme, where one should not always ask Smalltalk ui theme, but instead have a single reference to it and ask "self theme". As for which one of the two would be better in this situation, I don't know. In general I would prefer the latter, but if there was a Spec-way added, then it should be used â it would make it easier to switch icons just for Spec in the future if such need would arise. Also thanks for all the Spec fixes, this is really important! Peter On Mon, Jul 18, 2016 at 2:12 PM, Marion Noirbent < ms.noirbent(a)etudiant.univ-lille1.fr> wrote: > Hi, > > In the issue 18742 add class to manage focusorder, Peter UhnÃ¡k says: > > " > The idiomatic way of creating icons should be either > #smallBackIcon asIcon (ideally) > > or the long-form > (Smalltalk ui icons iconNamed: #smallBackIcon) > " > > > But there is a third way, ComposableModel defines iconNamed: like that > > ComposableModel>>iconNamed: aSymbol > ^ Smalltalk ui icons iconNamed: aSymbol > > So it is possible to use self iconNamed: #smallBackIcon > > So my question is: what way is really ideal ? > >

July 18, 2016

Re: [Pharo-users] Spec, Icons in subclasses of ComposableModel

by stepharo

Le 18/7/16 Ã 14:12, Marion Noirbent a Ã©crit : > Hi, > > In the issue 18742 add class to manage focusorder, Peter UhnÃ¡k says: > > " > The idiomatic way of creating icons should be either > #smallBackIcon asIcon (ideally) > > or the long-form > (Smalltalk ui icons iconNamed: #smallBackIcon) > " > > > But there is a third way, ComposableModel defines iconNamed: like that > > ComposableModel>>iconNamed: aSymbol > ^ Smalltalk ui icons iconNamed: aSymbol > > So it is possible to use self iconNamed: #smallBackIcon > > So my question is: what way is really ideal ? For now use ComposableModel>>iconNamed: aSymbol Stef > >

July 18, 2016

Spec, Icons in subclasses of ComposableModel

by Marion Noirbent

Hi, In the issue 18742 add class to manage focusorder, Peter UhnÃ¡k says: " The idiomatic way of creating icons should be either #smallBackIcon asIcon (ideally) or the long-form (Smalltalk ui icons iconNamed: #smallBackIcon) " But there is a third way, ComposableModel defines iconNamed: like that ComposableModel>>iconNamed: aSymbol ^ Smalltalk ui icons iconNamed: aSymbol So it is possible to use self iconNamed: #smallBackIcon So my question is: what way is really ideal ?

July 18, 2016