- Pharo-dev - lists.pharo.org

Font chooser broken (12704)
by Nicolai Hess Jan. 25, 2014

Jan. 25, 2014

Sean, can you look at my latest submission for 12704. There were some types in your slice := instead of = or each value: aBlock instead of aBlock value:each And an error with Announcements for FontChooser that were sent to the PluggableListMorph too. nicolai

3 3

Re: [Pharo-dev] execute external command?
by Torsten Bergmann Jan. 25, 2014

Jan. 25, 2014

3 2

Re: [Pharo-dev] issue 12506 Vm crashes vm when testing updates [A-L]
by Nicolai Hess Jan. 25, 2014

Jan. 25, 2014

2014/1/6 Marcus Denker <marcus.denker(a)inria.fr> > > On 06 Jan 2014, at 00:58, Nicolai Hess <nicolaihess(a)web.de> wrote: > > These are the minimal steps I can use to reproduce the crash > take the 30663 image > running tests A-L -> no crash > open the image and execute: > > ScriptLoader new unloadPackage: 'Athens-Tutorial'. "<-- one part of 30664 > update" > HashedCollection cleanUp:true. "<-- one part of Smalltalk cleanUp:true" > > running tests A-L -> CRASH > > > Hmm... > > > 2014/1/5 Nicolai Hess <nicolaihess(a)web.de> > >> How about this: >> Take a 30663 image, apply all updates, recompile and cleanup. >> >> btw what exactly does a "Do Image Cleanup" (from system menu)? >> Is it the same as "Smalltalk cleanup"? >> >> > It is âSmalltalk cleanUp: trueâ > (so it does a bit more, e.g. resetting change sets) > > Marcus > I don't know if it is since the lates NB changes, but running all A-L tests works again. Tested on Linux: pharo --nodisplay Pharo-30719.image test --junit-xml-output '^[A-L].*' -> no crash

1 0

execute external command?
by Johan Brichau Jan. 25, 2014

Jan. 25, 2014

Hi list, In another thread, Sven pointed me to the environment variables access from within Pharo3 (using Smalltalk os environment). This already eliminates one use case we have for OSProcess, but I fail to find a replacement for the other one: invoking external commands. So, my question: is OSProcess the only way to perform an external command from within Pharo3 ? thanks for the info Johan

1 0

asReactiveVariable ????
by Pharo4Stef Jan. 24, 2014

Jan. 24, 2014

Hi guys, I think that we will rename all the asReactiveVariable that got introduced into their old name asValueHolder. And we will rename the class too to its old name. Why? I think that we should not change at the last moment ValueHolder into ReactiveVariable even if the name could be better: - First there are books around (and not only mine) that use this vocabulary for decades. - Second all the Spec tools developed by people right now do not work in latest 3.0. - I think that this change does not worth the noise it introduced: all the future changes of Spec-based tools that will be using asReactive will not work in Pharo3.0. We are in beta and now we should not change that. Then I would appreciate that we discuss it before. Because I would not change that even between versions of Pharo. Stef

3 2

Issue 12720 Spec: Button Layout Occludes Label
by Sean P. DeNigris Jan. 24, 2014

Jan. 24, 2014

https://pharo.fogbugz.com/default.asp?12720 Screenshots and code attached. ----- Cheers, Sean -- View this message in context: http://forum.world.st/Issue-12720-Spec-Button-Layout-Occludes-Label-tp47391… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

1 0

problems with RPackage and cie...
by Alexandre Bergel Jan. 24, 2014

Jan. 24, 2014

Hi! We are constantly facing problems when moving classes between packages. This is highly discouraging. This involves tricky parts of the system that both difficult to understand and to debug. Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

6 14

[Fuel] Back to stable builds
by Max Leske Jan. 24, 2014

Jan. 24, 2014

Hi guys So apparently somehow the problems weâve had with the builds are now gone. Iâve reenabled failure e-mails for failed / broken builds. Hereâs whatâs on my list and what I will work on (in that order): - fix last failing test for 3.0 - prepare compatibility packages for Squeak4.5 (see https://code.google.com/p/fuel/issues/detail?id=204&colspec=ID%20Type%20Sta…) - implement truncation (see https://code.google.com/p/fuel/issues/detail?id=203&colspec=ID%20Type%20Sta…) Cheers, Max

2 1

Issue 2711 Monticello wastes significant amounts of memory
by Stephan Eggermont Jan. 24, 2014

Jan. 24, 2014

The number of distinct authors of monticello packages is not so large. MCVersionInfo allInstances size 13984 Pharo 30716 30721 Moose 5.0 (on 30714) (MCVersionInfo allInstances collect: [ :each | each author ]) asSet size 129 Pharo 30716 269 Moose 5.0 Can we expect issues if we replace the author string by a symbol? WideString issues perhaps? initializeWithName: vName id: aUUID message: aString date: aDate time: aTime author: initials ancestors: aCollection stepChildren: stepCollection name := vName. id := aUUID. message := aString. date := aDate. time := aTime. author := initials asSymbol. ancestors := aCollection. stepChildren := stepCollection author ^ author asString and then replace all authors by their symbols in the image? We could do the same for date (1821 unique in 30716, 3027 in Moose 5) This is issue 2711 I donât think this should be a must-fix for 3.0 Stephan

2 2

Re: [Pharo-dev] [Moose-dev] Re: a problem in latest moose 5.0 image
by Tudor Girba Jan. 24, 2014

Jan. 24, 2014

Retrying with the attachment. [image: Inline image 1] On Fri, Jan 24, 2014 at 2:56 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Hi, > > I also just downloaded the latest Pharo 3.0 (30719), and I took the first > class AIRootContext from the 'AST-Interpreter-Core' and dragged it to > 'AST-Core' and the category is not changed. So, the problem comes from > Pharo. > > See the picture attached. > > Cheers, > Doru > > [image: Inline image 1] > > -- > www.tudorgirba.com > > "Every thing has its own flow" > > > On Fri, Jan 24, 2014 at 2:52 PM, Stephan Eggermont <stephan(a)stack.nl>wrote: > >> Followups in the pharo-dev list, please >> >> Esteban wrote: >> >I would really like a reproducible caseâ¦ in the form of an image, if no >> else. >> > >> >btwâ¦ moose 5.0 images are severely broken in that area, so if you are >> using one of them you *will* have problems. >> >> I can deny that it is a Moose problem, I can reproduce it in Pharo 30716 >> on mac >> >> Open the image, open a Nautilus browser >> Add new package AZ >> Select AST-Core, Nodes >> Select RBProgramNode >> Copy the class with right-click menu >> Rename to AZProgramNode >> Enter your name (should have happened when creating the new package!) >> Drag AZProgramNode to AZ >> Category is not updated. >> >> Stephan >> _______________________________________________ >> Moose-dev mailing list >> Moose-dev(a)iam.unibe.ch >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >> > > > > -- > www.tudorgirba.com > > "Every thing has its own flow" > -- www.tudorgirba.com "Every thing has its own flow"

1 1