January 2014 - Pharo-dev - lists.pharo.org

[pharo-project/pharo-core]

by GitHub

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

Jan. 31, 2014

[pharo-project/pharo-core] 9244dd: 30733

by GitHub

Branch: refs/heads/3.0 Home: https://github.com/pharo-project/pharo-core Commit: 9244ddb91f1dfdf3d1d672636b3821c9e906e308 https://github.com/pharo-project/pharo-core/commit/9244ddb91f1dfdf3d1d67263… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-01-31 (Fri, 31 Jan 2014) Changed paths: M AsmJit-Core.package/AJAssembler.class/README.md M AsmJit-Core.package/AJConstants.class/README.md M AsmJit-Core.package/AJGeneratedCode.class/README.md M AsmJit-Extension.package/AJLineStream.class/README.md M AsmJit-Instructions.package/AJInstruction.class/README.md M AsmJit-Instructions.package/AJInstructionDecoration.class/README.md M AsmJit-Instructions.package/AJJumpInstruction.class/README.md M AsmJit-Instructions.package/AJJumpLabel.class/README.md M AsmJit-Instructions.package/AJRoutineEpilogue.class/README.md M AsmJit-x86.package/AJx64Instruction.class/README.md M AsmJit-x86.package/AJx64InstructionDescription.class/README.md M AsmJit-x86.package/AJx64JumpInstruction.class/README.md M AsmJit-x86.package/AJx86Instruction.class/README.md M AsmJit-x86.package/AJx86JumpInstruction.class/README.md M Balloon.package/BalloonEngineConstants.class/README.md M Compiler.package/BlockStartLocator.class/README.md M Compiler.package/DecompilerConstructorForClosures.class/README.md M Compiler.package/InstanceVariableNode.class/README.md M Compiler.package/LiteralVariableNode.class/README.md M Compiler.package/ParserNotification.class/README.md M Compiler.package/ReparseAfterSourceEditing.class/README.md M Compiler.package/UndeclaredVariable.class/README.md M Compiler.package/UndeclaredVariableWarning.class/README.md M Compiler.package/UndefinedVariable.class/README.md M Compiler.package/UnknownSelector.class/README.md M Compiler.package/UnusedVariable.class/README.md M CompilerTests.package/ArrayLiteralTest.class/README.md M CompilerTests.package/ClosureCompilerTest.class/README.md M CompilerTests.package/ClosureTests.class/README.md M CompilerTests.package/CompilerExceptionsTest.class/README.md M CompilerTests.package/ContextCompilationTest.class/README.md M CompilerTests.package/IfNotNilTests.class/README.md M CompilerTests.package/MethodHighlightingTests.class/README.md M CompilerTests.package/MethodNodeTest.class/README.md M CompilerTests.package/MockSourceEditor.class/README.md M CompilerTests.package/ScannerTest.class/README.md M DebuggerFilters.package/BlockFilter.class/README.md M DebuggerFilters.package/BooleanFilter.class/README.md M DebuggerFilters.package/FilterTest.class/README.md M DebuggerFilters.package/KernelClassesFilter.class/README.md M DebuggerFilters.package/SelectorFilter.class/README.md M DebuggerFilters.package/StackFilter.class/README.md A ScriptLoader30.package/ScriptLoader.class/instance/pharo - scripts/script386.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - updates/update30733.st M ScriptLoader30.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Spec-Tools.package/ChangeSorterModel.class/instance/text/buildSelectorDescriptionFor_class_selector_prettyPrint_showDiff_.st M Tools.package/ImageCleaner.class/instance/api/cleanUpForProduction.st A Tools.package/ImageCleaner.class/instance/cleaning/examplePackages.st M Tools.package/ImageCleaner.class/instance/cleaning/packagesForCleanUpInProduction.st M Tools.package/ImageCleaner.class/instance/cleaning/testPackages.st Log Message: ----------- 30733 12758 Class comments missing for Balloon package https://pharo.fogbugz.com/f/cases/12758 12766 #cleanUpForProduction more improvements https://pharo.fogbugz.com/f/cases/12766 12749 Provide class comments for AsmJIT https://pharo.fogbugz.com/f/cases/12749 12760 Class comments missing for package DebuggerFilters https://pharo.fogbugz.com/f/cases/12760 12759 Class comments missing for Compiler and CompilerTests package https://pharo.fogbugz.com/f/cases/12759 12753 ChangeSorter does not differentiate between changed/removed/added methods https://pharo.fogbugz.com/f/cases/12753 http://files.pharo.org/image/30/30733.zip

Jan. 31, 2014

Re: [Pharo-dev] Please keep your cool new stuff for Pharo 4

by btc＠openinworld.com

Esteban Lorenzano wrote: > Soâ¦ instead following my advice, you people continue submitting and asking for integration things that are API changes. > As a result, instead gaining stability we are loosing itâ¦ > > can you guys please be so kind and stop doing what you shouldnât? > > I will ask it again: *now* we need to bugfix the upcoming release. > Cleanups, enhancements, small additions *are not* bugfixing. And even if you are sure that it is not breaking anything, it most probably will do (for more details, take as an example the mail I will send in 5 min). > > I know we all want a better Pharo. But at this moment the way to achieve it is to collaborate in testing, reporting and fixing the current version. > > Thanks, > Esteban > > Also time is consumed developing, reviewing and integrating non-bug-cases, which could be tackling bugs. Can a "Pharo4.0" milestone be added to Fogbugz? Setting something to "Later" feels like it might get lost in the woods of old tickets imported from the old tracker. For instance, I've recently submitted a slice for [1] that adds two new methods and a trivial refactoring of one other to Spec's ComposableModel (so I can't imagine it would break anything), but in support of discipline on the feature freeze, I could get by with making these PharoLauncher extensions for now and hold them over to Pharo4.0. [1] https://pharo.fogbugz.com/f/cases/12677/subscribe-to-window-closed-event-ou… Indeed, it might even be worthwhile to be more heavy handed and for New Cases replace 'Pharo3.0' with 'Pharo3.0-bugfix-only' - or maybe there is some way to splash some heading text at the top of each page using BugMonkey. cheers -ben

Jan. 31, 2014

Re: [Pharo-dev] poolDictionaries removal breaks my projects

by Esteban Lorenzano

I donât know what happened. All that I know is that it was not working and now with the last fix it is, so Iâm happy for now. worried? yes. But not too much :) On 31 Jan 2014, at 14:59, Henrik Johansen <henrik.s.johansen(a)veloxit.no> wrote: > > On 30 Jan 2014, at 6:14 , Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > >> Soâ¦ that. >> >> Is super cool to remove poolDictionaries from the default class template. >> What is not cool *at all* is the fact that now my low level projects, who uses them intensively, does not work anymore. >> The reason? the classes are created without poolDictionaries. >> >> So, pleaseâ¦ whoever pushed this change. Please fix it. >> >> thanks, >> Esteban > > Sooo, since Iâm curios, anyone care to explain how a change intended to affect whether Nautilus displays pool Dicts end up breaking how theyâre loaded from Monticello? > > Did Nautilus pick up on the class load announcement from RPackage and end up recompiling the class with itâs own (lacking) default definition or something similarly crazy? > > Cheers, > Henry

Jan. 31, 2014

Re: [Pharo-dev] poolDictionaries removal breaks my projects

by Pharo4Stef

Torsten I love the changes of Johan. I would love to have a more compact class definition :) Now the question by henrik is really puzzling me. Stef > Hi Johan, > > Still I really do not understand what particular problem that is solved by changing > the template from > > MySuperclass subclass: #Foo > instanceVariableNames: '' > classVariableNames: '' > poolDictionaries: '' > category: 'Bar-Core' > > to > > MySuperclass subclass: #Foo > instanceVariableNames: '' > classVariableNames: '' > category: 'Bar-Core' > > other than some of your student had problem not yet knowning what pool dictionaries are > and you want to hide pools therefore. A weak argument since some students may not yet > know about class variables - so why not hiding them in the first place too? > > Another teacher may argue that his students got problems because the template was changed > and nearly all ST, Seaside and Pharo books used for teaching include the extended variant > of the message. > > IMHO a class template is (as the name says) a "template" and a template should be > something one just has to fill out. The idea of a template is to avoid too much typing afterwards. > So the idea is one just should fill out the template without much hazzle. > If I require an ivar, a class variable, a pool or a category I just put it in. > > By now reducing the template people who require pools have to do more typing and > they have to remember the order of words in the keyword message... > > I stand at my point I think there is not much real value in this change of the default > template, but are fine if community agrees on the reduced version. > > Thanks > T. >

Jan. 31, 2014

Re: [Pharo-dev] Seaside extensions and lowercase package names in Pharo

by Chris Cunningham

On Fri, Jan 31, 2014 at 3:57 AM, Torsten Bergmann <astares(a)gmx.de> wrote: > Now that Pharo uses real packages beside categories I see some > lowercase "ghost" packages in Monticello Browser list after loading > Seaside. > > To reproduce just load Seaside using config browser and check in > Monticello browser. > > > I guess this is coming from methods in lowercase extension > categories like "*seaside-pharo-core" which do not really > match "Seaside-Pharo-Core" package. > > Any comments? > > Using a star (*) and all-lowercase method category names has been the convention for PackageInfo / Monticello for method extensions since the beginning (that is, for many many years now). You'll undoubtedly run into this several more times - at least you will when bringing in older Monticello packages or those created outside of Pharo. Not all, but some. -cbc > Thx > T. > > >

Jan. 31, 2014

Re: [Pharo-dev] poolDictionaries removal breaks my projects

by Chris Cunningham

On Thu, Jan 30, 2014 at 11:42 PM, Torsten Bergmann <astares(a)gmx.de> wrote: > Please make it a setting - so one can see the creation message with > poolDictionaries in Nautilus > as before in the browser and is able to fill out the template. > > When using NB one requires them. > > Well, since it seems that the direction is to auto-hide the poolDictionaries part (and a preference is undesirable), another option is a NB-specific browser that just always shows this keyword. And for those (few) of us that use Traits, maybe a specific browser to include the uses: keyword as well, so that I don't have to remember where it goes when I need it in another 6 months time. But, not for Pharo3, and not from me (at least, not right right now). -cbc > Thx > T. > > >

Jan. 31, 2014

Re: [Pharo-dev] Seaside extensions and lowercase package names in Pharo

by Pharo4Stef

On 31 Jan 2014, at 11:57, Torsten Bergmann <astares(a)gmx.de> wrote: > Now that Pharo uses real packages beside categories I see some > lowercase "ghost" packages in Monticello Browser list after loading Seaside. > > To reproduce just load Seaside using config browser and check in > Monticello browser. > > > I guess this is coming from methods in lowercase extension > categories like "*seaside-pharo-core" which do not really > match "Seaside-Pharo-Core" package. would be nice to have a little checker :) > > Any comments? > > Thx > T. > >

Jan. 31, 2014

Re: [Pharo-dev] xpath?

by HernÃ¡n Morales Durand

2014-01-30 Tudor Girba <tudor(a)tudorgirba.com>: > Hi, > > Does anyone know what is the currently functional XPath library? > > I just tested XPath from PharoExtras, but it does not work with the latest > XMLParser. > > The XPath library is not complete, although supports querying attributes with @. Try for example: | doc | doc := (XMLDOMParser onURL: 'http://unicode.org/repos/cldr/trunk/common/supplemental/supplementalData.xml') parseDocument. (XPath for: '/languageData/language/@type') in: doc. I just uploaded a new configuration for Pharo 3 (you may find it in the Configuration Browser).

Jan. 31, 2014

Re: [Pharo-dev] Nautilus often loses context

by Noury Bouraqadi

There is also a show stopper bug: when adding a protocol to a new class. It a show stopper I faced with my students. I did a quick fix and uploaded it. https://pharo.fogbugz.com/f/cases/12473/Wrong-behavior-of-ListDialogWindow-… On 31 janv. 2014, at 11:42, Johan Brichau wrote: > Indeed, that is exactly the case. > > Thank you. Please integrate! ;-) > > Johan > > On 30 Jan 2014, at 22:56, Nicolai Hess <nicolaihess(a)web.de> wrote: > >> 2014-01-30 Sabine KnÃ¶fel <sabine.knoefel(a)gmail.com>: >> me too, but it is only sometimes I can not tell, how to reproduce it. >> >> >> On Thu, Jan 30, 2014 at 8:31 PM, Johan Brichau <johan(a)inceptive.be> wrote: >> Hi all, >> >> When working with Nautilus in Pharo 3, I often experience that the browser looses its context after a save. >> I edit a method, save it, and Nautilus will jump away from that context, essentially showing itself as if it was just opened from scratch so I need to manually reselect the class, the protocol and the method I was working on. >> >> It's very annoying and I wonder if this is something other people experience too and that this is known? >> >> At first I thought it was when I was editing methods in class extensions. But it happens randomly, sometimes after I got the dialog to 'save your changes' but sometimes not. >> >> Anybody? >> >> Johan >> >> >> >> >> >> Most of the time it happens the first time a package gets dirty. >> And it is related to this error: >> >> 12734 Nautilus accept changes shows prompt for cancel dialog >> >> The fix is there, but not yet integrated. >> >> >> >> Nicolai > > Noury Bouraqadi Ecole des Mines de Douai http://car.mines-douai.fr/noury --

Jan. 31, 2014