- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] [FEEDBACK] Install Pharo on MacOSX

by Matias Garcia Isaia

Hi there! Worked like a charm in Mavericks here. The Pharo Loader looks superb :) I've installed the app with no trouble, and downloaded the latest Pharo2 image. After launching it, the image showed a notification with this message: "Information Pharo cannot locate the sources file named /Applications/PharoV20.sources. Please check that the file is named properly and is in the same directory as this image. Make sure the sources file is not an Alias." I hope that says to you more than it says to me :) Feel free to ask for clarification, if you need any. On Thu, Nov 7, 2013 at 10:36 AM, Damien Cassou <damien.cassou(a)gmail.com>wrote: > On Tue, Nov 5, 2013 at 12:10 PM, Mark Bestley <news{(a)bestley.co.uk> wrote: > > This is due to Gatekeeper I think. I managed to open it by choosing Open > > in the right click menu in Finder. see > > <http://support.apple.com/kb/ht5290> I think you need to sign the app > > > thank you for the reference. I will have a look. I wanted to put the > application on the Mac App Store, but it looks I would have to pay > Apple and I don't want to. Hope your solution doesn't require that. > > > The Launcher looks for and save images in ~/Library/Preferences/Pharo > > This is wrong it should be ~/Library/Application/Support/Pharo for > > general use, there is a case for using ~/Library/Containers to fit in > > with Apple's sandboxing. > > > I wanted to do that already. Thanks for the directory names. Do you > have an url where Apple discusses such directories? > > > > Or better allow us to chnage the directory > > > That's on my todo. As always, I need help. This is the kind of change > people can do easily (the preference mechanism is already in place). > So, if you want to hack on the launcher, this would be a good start. > > > > The icons are odd, trying to get a new Pharo 3 image it says hit refresh > > icon which took me some time to find. Although I am bad at all icons so > > might just be me. > > It's not just you. I see 2 solutions: > > - have a menu item to refresh when right clicking on the "hit refresh > button" message. > - automatically download the content when expanding the tree. > > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Success is the ability to go from one failure to another without > losing enthusiasm." > Winston Churchill > >

Nov. 7, 2013

Re: [Pharo-dev] Support understanding changes

by Goubier Thierry

Le 07/11/2013 13:00, Martin Dias a Ã©crit : > Hi > > On Wed, Nov 6, 2013 at 1:38 PM, Goubier Thierry <thierry.goubier(a)cea.fr > <mailto:thierry.goubier@cea.fr>> wrote: > > > > Le 06/11/2013 13:20, StÃ©phane Ducasse a Ã©crit : > > Now that we have epicea I would really love to have a tool that > does not show me stupidly a diff but > take into account the actions that have been performed like > rename class, splitâ¦. > > > Yes! I want that too! How do we try EPICEA? Is it already integrated? > > > Nop, not ready for integration. I sent an email two weeks ago, but now > the updated information is here: > > http://smalltalkhub.com/#!/~MartinDias/Epicea > > Any feedback is welcome. I'd dream of having enough time to study it in depth :( Thierry -- Thierry Goubier CEA list Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95

Nov. 7, 2013

Re: [Pharo-dev] extracting a pier book into pillar files

by Damien Cassou

I put the Magritte/Pier mailing list on copy. On Wed, Nov 6, 2013 at 2:24 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > Is there existing support to extract an existing Pier-based book into Pillar > files? > > I would be interested in moving the Moose book to this format. I'm not finished yet with the Pier-Book migration to Pillar. But the format (i.e., wiki syntax) is exactly the same. So, you *just* need to extract each Pier-Book chapter to a separate file. -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill

Nov. 7, 2013

Re: [Pharo-dev] [FEEDBACK] Install Pharo on MacOSX

by Damien Cassou

On Tue, Nov 5, 2013 at 12:10 PM, Mark Bestley <news{(a)bestley.co.uk> wrote: > This is due to Gatekeeper I think. I managed to open it by choosing Open > in the right click menu in Finder. see > <http://support.apple.com/kb/ht5290> I think you need to sign the app thank you for the reference. I will have a look. I wanted to put the application on the Mac App Store, but it looks I would have to pay Apple and I don't want to. Hope your solution doesn't require that. > The Launcher looks for and save images in ~/Library/Preferences/Pharo > This is wrong it should be ~/Library/Application/Support/Pharo for > general use, there is a case for using ~/Library/Containers to fit in > with Apple's sandboxing. I wanted to do that already. Thanks for the directory names. Do you have an url where Apple discusses such directories? > Or better allow us to chnage the directory That's on my todo. As always, I need help. This is the kind of change people can do easily (the preference mechanism is already in place). So, if you want to hack on the launcher, this would be a good start. > The icons are odd, trying to get a new Pharo 3 image it says hit refresh > icon which took me some time to find. Although I am bad at all icons so > might just be me. It's not just you. I see 2 solutions: - have a menu item to refresh when right clicking on the "hit refresh button" message. - automatically download the content when expanding the tree. -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill

Nov. 7, 2013

Re: [Pharo-dev] Deep Into Pharo: PPExpressionParser

by Damien Cassou

On Wed, Nov 6, 2013 at 12:41 PM, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > Thanks! I'm clear on how to use them, just not on why to choose one over the > other.. I would say you can instantiate a PPExpressionParser if you want to do a small parser for small task. Now, if you have a grammar that's composed of many parsers, I would subclass PPCompositeParser. -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill

Nov. 7, 2013

Re: [Pharo-dev] Support understanding changes

by Martin Dias

Hi On Wed, Nov 6, 2013 at 1:38 PM, Goubier Thierry <thierry.goubier(a)cea.fr>wrote: > > > Le 06/11/2013 13:20, StÃ©phane Ducasse a Ã©crit : > > Now that we have epicea I would really love to have a tool that does not >> show me stupidly a diff but >> take into account the actions that have been performed like rename class, >> splitâ¦. >> > > Yes! I want that too! How do we try EPICEA? Is it already integrated? Nop, not ready for integration. I sent an email two weeks ago, but now the updated information is here: http://smalltalkhub.com/#!/~MartinDias/Epicea Any feedback is welcome. > > Side questions: camillo and other giter, I was thinking that it would >> make sense to publish on git metadata (may be in ston) >> representing the semantics of the operation that led to the changes) so >> that tools can take advantage of this information >> to present semantical operation instead of plain stupid diff. For example >> split this method, rename class,â¦. >> > > +100 > > My approach would be to focus on tools in the Pharo world to explore that, > at the Monticello GUI level (and merge tools). > > In the Git world, I'll focus simply on a file format able to store that > knowledge, in a way which minimises git-induced conflicts... The goal being > that a git merge would recreate a working Smalltalk result (no conflicts) > with a correct EPICEA history (eventually recreated from the git stored > data). > > What I know is that a single file in whatever format containing the EPICEA > log will be a conflict magnet. > > Thierry > -- > Thierry Goubier > CEA list > Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s > 91191 Gif sur Yvette Cedex > France > Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95 > >

Nov. 7, 2013

Re: [Pharo-dev] Deep Into Pharo: PPExpressionParser

by Stephan Eggermont

Norbert wrote: >You may have a look at PParser>>#delimitedBy: Thank you. Stephan

Nov. 7, 2013

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/30550 Home: https://github.com/pharo-project/pharo-core

Nov. 7, 2013

[pharo-project/pharo-core] abc422: 30550

by GitHub

Branch: refs/heads/3.0 Home: https://github.com/pharo-project/pharo-core Commit: abc4223ca00772a462c1258f45047f40bc4a0e9d https://github.com/pharo-project/pharo-core/commit/abc4223ca00772a462c1258f… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2013-11-07 (Thu, 07 Nov 2013) Changed paths: M Monticello.package/MCFileBasedRepository.class/instance/accessing/allFileNamesOrCache.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - scripts/script205.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - updates/update30550.st M ScriptLoader30.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M System-CommandLine.package/STCommandLineHandler.class/README.md M System-CommandLine.package/STCommandLineHandler.class/instance/activation/activate.st A System-CommandLine.package/STCommandLineHandler.class/instance/private/end.st M System-Localization.package/Locale.class/instance/accessing/determineLocaleID.st Log Message: ----------- 30550 11739 STCommandLineHandler cannot save https://pharo.fogbugz.com/f/cases/11739 6155 Locale plugin returning wrong isoCountry code https://pharo.fogbugz.com/f/cases/6155 11393 allFileNamesOrCache seems to be inconsistent with other methods https://pharo.fogbugz.com/f/cases/11393 http://files.pharo.org/image/30/30550.zip

Nov. 7, 2013

Re: [Pharo-dev] [Vm-dev] Frequent SegFaults in PharoVM with Pharo 3.0

by Max Leske

On 07.11.2013, at 00:27, vm-dev-request(a)lists.squeakfoundation.org wrote: > Date: Wed, 6 Nov 2013 19:23:47 -0200 > From: Mariano Martinez Peck <marianopeck(a)gmail.com> > Subject: Re: [Vm-dev] Frequent SegFaults in PharoVM with Pharo 3.0 > To: Squeak Virtual Machine Development Discussion > <vm-dev(a)lists.squeakfoundation.org> > Message-ID: > <CAA+-=mWDtHGQWSHx-m4u37Kj0UAMx=UG=qUCz+wMvgDT8BaQZQ(a)mail.gmail.com> > Content-Type: text/plain; charset="windows-1252" > > Max, did you try with Eliot VMs besides the pharo ones? No, I havenât. I can try (though only on my machine), but if I canât reproduce the SegFault that doesnât mean much unfortunately. It took me 10 to 20 tries with the PharoVM tooâ¦ Iâll try anyway and let you know what I find. Max > > Thanks > > > On Wed, Nov 6, 2013 at 6:04 PM, Max Leske <maxleske(a)gmail.com> wrote: > >> >> Hi >> >> Weâve been encountering frequent SegFaults when running the Fuel tests on >> the Pharo CI (https://ci.inria.fr/pharo-contribution/job/Fuel/) Since >> today Iâve also been able to reproduce the SegFaults on my MacBook Pro (OS >> X 10.9) too. We have not been able to determine the cause of the SegFault >> but we can produce SegFaults often, although not reliable (more reliable on >> the CI). >> >> The CI uses the stable VM: >> http://files.pharo.org/vm/pharo/linux/stable.zip >> I use a newer version from October on my machine: >> http://files.pharo.org/vm/pharo/mac/273.zip >> >> Iâve attached all the dumps of the crashes I was able to produce on my >> machine, together with Appleâs crash logs. >> >> Iâve been able to deduce the following: >> - garbage collection seems to be a trigger for the SegFault. When one of >> the methods FLMethodContextSerialization>>testFuelShouldIgnoreFuel and >> FLMethodContextSerialization>>testMethodContextWithNilPc contain the line >> â3 timesRepeat: [Smalltalk garbageCollect]â the SegFault appears nearly >> always (on CI). When I remove the line the builds run through. >> - Not all methods with the garbage collect line trigger a SegFault (I >> could only identify those two) >> - the garbage collect line itself suffices as a trigger in the mentioned >> methods. >> - The number of tests (amount of used memory?) seems to influence the >> appearence of the SegFault (e.g. loading "DevelopmentGroup" seems to >> trigger it more often than loading âBenchmarksâ) >> - the SegFault always appears after the tests with the garbage collect >> line have been run, never before >> - the VM canât write the crash.dmp every time >> >> Since the SegFaults are so random I cannot give you an image to reproduce >> the problem. Iâve had the best results using a fresh 3.0 image ( >> http://files.pharo.org/image/30/30549.zip) and then evaluating the >> following in a workspace: >> >> Gofer it >> smalltalkhubUser: 'Pharo' project: 'Fuel'; >> package: 'ConfigurationOfFuel'; >> load. >> >> ((Smalltalk at: #ConfigurationOfFuel) project version: #bleedingEdge) >> load: 'DevelopmentGroup'. >> >> HDTestReport >> runClasses: (TestCase allSubclasses select: [ :class | class name >> beginsWith: 'FL']) >> named: âfoo' >> >> If it doesnât work, try using the TestRunner manually. Select the default >> Fuel tests (alphabetically at F) and the additional Fuel tests (at the >> bottom of the list) and run them. >> >> If anybody has any clue about what could be going on Iâd really appreciate >> any input. Iâll happily provide more information if I can. >> >> Thanks for reading :) >> Max >> >> >> > > > -- > Mariano > http://marianopeck.wordpress.com

Nov. 7, 2013