- Pharo-dev - lists.pharo.org

[Pharo-project] Porting SmaCC from 1.4 to 2.0; doSilently: equivalent ?
by Goubier Thierry March 12, 2013

March 12, 2013

Hi, I'm trying to port SmaCC to 2.0 and I'm looking for the equivalent to SystemChangeNotifier>>doSilently:. Is it SystemAnnouncer>>suspendAllWhile:? (doSilently: is used in SmaCC tests). Thanks, 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

4 11

[Pharo-project] IMPORTANT: Issue 6351: FileReference>>deleteAll follows symlinks in 1.4
by Sean P. DeNigris March 12, 2013

March 12, 2013

This is a fun one to find out about by accident... Hey, what happened to my temporary variable names? Oh, they're decompiled because my image folder was deleted while deleting my home folder because the folder being deleted contained a symlink to it. Thank god for backups... and that it was deleting alphabetically, so mostly rarely-changed config files were deleted (i think/hope)... Pharo1.4 Latest update: #14448 '/path/to/dir' asFileReference deleteAll. * If the link is valid, it follows it and keeps deleting * If not, it claims the link file doesn't exist. http://code.google.com/p/pharo/issues/detail?id=6351 -- View this message in context: http://forum.world.st/IMPORTANT-Issue-6351-FileReference-deleteAll-follows-… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

1 2

[Pharo-project] When is 2.0 shipping?
by phil＠highoctane.be March 12, 2013

March 12, 2013

As I saw 11/3 in the fogbugz tracker, I wondered. BTW, hi there, Penelope :-) Funny! Phil

4 3

[Pharo-project] Zeroconf: config command issue - oops
by phil＠highoctane.be March 12, 2013

March 12, 2013

In the book, we have that config should show the help. As in: Examples: # display this help message $PharoVM My.image config but... PhilMac:~/Documents/Smalltalk/2-MyWorkspaces/workspaceZeroConf20130312 philippeback$] ./vm.sh Pharo.image config ==== Startup Error: SubscriptOutOfBounds: 1 OrderedCollection(Object)>>errorSubscriptBounds: OrderedCollection>>ensureBoundsFrom:to: OrderedCollection>>at: CommandLineArguments>>argumentAt: ConfigurationCommandLineHandler(CommandLineHandler)>>argumentAt: ConfigurationCommandLineHandler>>loadRepositoryURL ConfigurationCommandLineHandler>>repositoryURL ConfigurationCommandLineHandler>>gofer ConfigurationCommandLineHandler>>loadConfigurationNames ConfigurationCommandLineHandler>>listConfigurations ConfigurationCommandLineHandler>>list ConfigurationCommandLineHandler>>activate ConfigurationCommandLineHandler class(CommandLineHandler class)>>activateWith: DefaultCommandLineHandler>>handleSubcommand DefaultCommandLineHandler>>handleArgument: DefaultCommandLineHandler>>activate DefaultCommandLineHandler class>>startUp: in Block: [self new activate] BlockClosure>>cull: SmalltalkImage>>executeDeferredStartupActions: in Block: [each cull: resuming] BlockClosure>>on:do: SmalltalkImage>>logStartUpErrorDuring:into:tryDebugger: SmalltalkImage>>executeDeferredStartupActions: in Block: [:each | self... OrderedCollection>>do: SmalltalkImage>>executeDeferredStartupActions: SmalltalkImage>>startupImage:snapshotWorked: SmalltalkImage>>snapshot:andQuit: SmalltalkImage>>saveImageInFileNamed: SmalltalkImage>>saveAs: SaveCommandLineHandler>>saveImage SaveCommandLineHandler>>activate Got startup errors: SubscriptOutOfBounds: 1 Is this the behavior we want? It is kind of scary actually. Phil

4 10

[Pharo-project] migrating PharoNonCorePackages/Sound to PharoExtras/Sound
by stephane ducasse March 12, 2013

March 12, 2013

Hi guys I will also copy the configuration files from MetacelloRepository. Then I will update these configurations to propose SoundSynthesis SoundScore SoundTools Then I will try to make them work on 2.0 Stef

1 1

Re: [Pharo-project] GSoC13: Distributed Issue Tracker
by Stephan Eggermont March 12, 2013

March 12, 2013

GÃ¶ran wrote: >Would you like me to dig out the Gjallar codebase and share it with you? >With some annotations? There should be lots to pick/learn from it. I have a Gjallar0.4 image here. Any changes since then? Stephan

1 0

[Pharo-project] GSoC13: Distributed Issue Tracker
by Stephan Eggermont March 12, 2013

March 12, 2013

Distributed Issue Tracker Level: (intermediate, advanced) Possible mentor: Stephan Eggermont Possible second mentor: Diego Lont Description A native smalltalk distributed issue tracker. It should have basic issue tracking functionality including attaching files/pictures/code. It should have a native interface, a web interface and a scripting API. Primary development is in Pharo. Issue trackers have different kind of users. To make clear that different users have different needs, persona can be helpful. Isabelle is an information technology student looking for an interesting language and environment to learn. She wants to contribute to and learn from a smart community and needs interesting experiences on her cv. She has already learned the basics of a few mainstream languages and feels ready to try something more exotic. Smalltalk seems interesting as the origin of many inventions. Yann is the major developer of a web-based platform based on Pharo and Seaside. He needs to ensure the platform keeps working smoothly and is updated regularly with the latest changes. In production he uses the released versions. He fears the major clean-ups Pharo is making make it difficult for him to keep up. He is dependent on a few old unmaintained squeaksource packages. Janine just found an interesting old package on squeaksource. It was last changed in 2007. She has been using smalltalk for a few years, so knows what to expect when trying to load an unmaintained package. There are some missing classes that still exist in squeak. Tony is the developer of a package that is used with nearly all smalltalks. He mainly works with a commercial smalltalk and keeps just enough contact with the Pharo community to keep his package working. He has complained about some changes that made it necessary for him to change his package structure. He mainly updates the Pharo version on his way to and from the office in the train. Eve maintains a few of the crucial Pharo kernel packages. They are under heavy development and once in a while everything breaks, leading to a flood of issues. They mostly come from outsiders, as she talks daily with the Pharo core team. She has to close a lot of them as duplicates. She also has to review code that gets attached in one form or another to the issue. Daniel is a maintainer of the vm that forms the basis for the Pharo vm. The vm is used by many more projects. Lara is a release manager for a well known linux distribution. Pharo is just one of 30 languages that are included in the distribution. Before doing a release she scans the issue tracker for any show stoppers. She had to stop including environments because of security issues. Technical Details The recent decision by Google to deprecate and stop its API for the Google Issue Tracker used by a.o. the Pharo, Seaside, MOOSE and Metacello projects makes it necessary for those projects to select a different issue tracker. The timespan before this decision has to be made is too short for the development of a new issue tracker from scratch. Now most development in Smalltalk uses distributed version control systems, either Monticello or Git, the question arises why these projects still would want to use a centralized issue tracker. The long-standing problems in keeping squeaksource up-and-running are only one example of the problems of depending on centralized infrastructure. Other examples are the move of Lukas' repository and the number of times where the Pharo CI infrastructure was not available, especially on holidays and weekends. The currently used issue trackers cannot work disconnected. Integrating the issue tracker in the CI workflow of the projects is crucial. The goals of the persona should be translated into a storymap. Delivery should be iterative and incremental, driven by value to the community and technical risk. The student is expected to be active on the mailing list and discuss development there. This includes handling (source) contributions by others. There is a small prototype available. Benefits to the Student - getting to know the difficulties of issue tracking/the workflow of open source projects - experience with distributed systems - experience an agile open source environment Benefits to the Community - better integrated workflow - native issue tracker, accessible both in-image, web and automated - showcase for productive environment Questions Here are seven persona. Which ones are missing/should be fleshed out?

2 1

[Pharo-project] Bad links on http://www.squeakvm.org/mac/
by phil＠highoctane.be March 12, 2013

March 12, 2013

Looks like you guys are going to https://ci.lille.inria.fr/pharo/job/Cog-VM/Architecture=32,OS=mac/lastSucce… but the servername is not that anymore. Stuff now lives here: http://pharo.gforge.inria.fr/ci/ Please adjust the links accordingly... Phil

1 0

Re: [Pharo-project] where to report vm crashes? (while running Moose tests)
by Stephan Eggermont March 12, 2013

March 12, 2013

Phil wrote: >Eliot as a new VM as of yesterday > >http://www.mirandabanda.org/files/Cog/VM/VM.r2701/README.2701 > >That kind of fixes things. > >But I guess the Pharo team still has to integrate these fixes. This is with 2701. The Moose image is based on Pharo 20589 Stephan

1 0

Re: [Pharo-project] where to report vm crashes? (while running Moose tests)
by Stephan Eggermont March 12, 2013

March 12, 2013

Esteban wrote: > Eliot builds will always have the old vm warning, even if they are not old :)... > you need one of the pharo builds (CogVM, NBCogVM or PharoVM) Well, Doru reported they crashed. Eliot's one doesn't: > 15875 run, 15472 passes, 2 skipped, 88 expected failures, 216 failures, 99 errors, 0 unexpected passes On the other hand, not being able to add a monticello directory repository is also not helpful. No filedialog is shown (receiver of bitAt: is nil, looks like a problem with filesystem permissions) Stephan

2 1