October 2013 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] [Pharo-users] Please contributors fill up this form...

by Andrei Chis

PharoContributor new name: 'Andrei Chis'; email: 'andrei(a)iam.unibe.ch'; website: 'http://andreichis.com'; description: 'PhD Student at the University of Bern. Contributor to Pharo (the debugger) and Moose (Glamour, Glamour-Seaside, The Moldable Debugger)'; yourself. On Wed, Oct 9, 2013 at 1:34 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>wrote: > Hi guys > > I would like to get > contributors.pharo.org a bit more representative of Pharo. > > We should have Previous contributors and enhance the current list. > Can you please reply to this mail > > PharoContributor new > name: 'Esteban Lorenzano'; > id: 'estebanlm'; > email: 'estebanlm(a)gmail.com'; > website: 'http://smallworks.eu'; > description: 'Pharo core team. Contributor of several > projects, including Kernel, DBXTalk, Voyage, Mars, etc. Also I work on the > VM.'; > image: ' > http://www.gravatar.com/avatar/193af464509ae8fbcc04abad70b72fc0?s=120'; > yourself > > > Stef >

Oct. 14, 2013

Re: [Pharo-dev] How to delete an obsolete class ?

by roberto.minelli＠usi.ch

Thank you Pavel, Just run into the same situation and your 'Smalltalk fixObsoleteReferences' worked like a charm ;) Cheers, Roberto On Oct 10, 2013, at 11:11 AM, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: > Hi Olivier, > > firstly try Smalltalk fixObsoleteReferences. Then try this: > > Smalltalk tools pointerExplorer openOn: SystemNavigation default > obsoleteClasses first. > > Look at every reference that is not related to the explorer itself and > try to find why it is not garbage-collected. > > Cheers, > -- Pavel > > 2013/10/10 Olivier Auverlot <olivier.auverlot(a)gmail.com>: >> Hi Pavel, >> >> Thanks for your response. >> >> I tryed this morning and in fact, the obsolete class has not instances. >> >> SystemNavigation default obsoleteClasses {AnObsoletePVENodeStatus} >> >> SystemNavigation default obsoleteClasses collect: #allSubInstances. an Array(an OrderedCollection()) >> >> have you an idea how to remove this class ? >> >> Best regards >> Olivier ;-) >> >> Le 9 oct. 2013 Ã 10:46, Pavel Krivanek a Ã©crit : >> >>> You need to check if it still does have some instances and kill them. >>> Then find and remove all references to the class. >>> >>> SystemNavigation default obsoleteClasses. >>> >>> SystemNavigation default obsoleteClasses collect: #allSubInstances. >>> >>> SystemNavigation default obsoleteClasses first allSubInstances first pointersTo. >>> >>> etc... >>> >>> Good hunt >>> -- Pavel >>> >>> 2013/10/9 Olivier Auverlot <olivier.auverlot(a)gmail.com>: >>>> Hi, >>>> >>>> In my project, my code has a strange behavior when I'm reading all subclasses of an another class. >>>> >>>> The following code must visit all the subclasses of PVEStatus but I get a bad result. >>>> >>>> PVEStatus allSubclasses >>>> do: [ :statusDatatype | >>>> (aRawStatus at: 'type') = statusDatatype type >>>> ifTrue: [ ^ statusDatatype getStatus: aRawStatus callback: self ] ] >>>> >>>> The answer contains #AnObsoletePVENodeStatus and this class doesn't exist. She doesn't appear in the class browser. I suppose that it's a rest of refactoring. How can I delete this obsolete class ? >>>> >>>> Best regards >>>> Olivier ;-) >>>> >>>> >>>> >>> >> >> >

Oct. 14, 2013

[pharo-project/pharo-core]

by GitHub

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

Oct. 14, 2013

[pharo-project/pharo-core] f3f5b0: 30478

by GitHub

Branch: refs/heads/3.0 Home: https://github.com/pharo-project/pharo-core Commit: f3f5b01f95b6c3b8e12b1f8e7d0112f9f3623ebd https://github.com/pharo-project/pharo-core/commit/f3f5b01f95b6c3b8e12b1f8e… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2013-10-13 (Sun, 13 Oct 2013) Changed paths: A ScriptLoader30.package/ScriptLoader.class/instance/pharo - scripts/script133.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - updates/update30478.st M ScriptLoader30.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st A System-FilePackage.package/PseudoClass.class/instance/accessing/users.st R System-Support.package/SystemNavigation.class/instance/query/hierarchyOfClassesSurrounding_.st R System-Support.package/SystemNavigation.class/instance/query/hierarchyOfImplementorsOf_forClass_.st R System-Support.package/SystemNavigation.class/instance/query/isThereAnImplementorOf_.st R Tools-Base.package/CodeHolder.class/instance/commands/copyUpOrCopyDown.st M Tools-Browser.package/Browser.class/instance/message functions/shiftedMessageListMenu_.st R Traits-Kernel-Traits.package/TClassDescription.class/instance/authors/addAuthorsTo_.st M Traits-Kernel-Traits.package/TClassDescription.class/instance/authors/authors.st Log Message: ----------- 30478 11864 More cleanups in SystemNavigation https://pharo.fogbugz.com/f/cases/11864 11868 Fixing users DNU on CS dropping on desktop https://pharo.fogbugz.com/f/cases/11868 http://files.pharo.org/image/30/30478.zip

Oct. 14, 2013

Re: [Pharo-dev] Fix Review Needed - Slice query - was Re: bug: [4993] Typing cmd+L cancel all typing and we can't undo it [Terminated]

by btc＠openinworld.com

Oct. 14, 2013

serializing and materializing MSE files with the Fame meta-engine

by Tudor Girba

Hi, I put together a short description/tutorial on using Fame for serialization and materialization of models and meta-models. Perhaps it can be useful for others, too: http://www.humane-assessment.com/blog/serializing-and-materializing-mse-fil… Cheers, Doru -- www.tudorgirba.com "Every thing has its own flow"

Oct. 13, 2013

Re: [Pharo-dev] bug: [4993] Typing cmd+L cancel all typing and we can't undo it [Terminated]

by StÃ©phane Ducasse

On Oct 13, 2013, at 1:08 PM, kilon <thekilon(a)yahoo.co.uk> wrote: > This is my first pharo bug fix so be gentle :D Great! We love contributions. Stef > https://pharo.fogbugz.com/f/cases/4993/Typing-cmd-L-cancel-all-typing-and-w… > <https://pharo.fogbugz.com/f/cases/4993/Typing-cmd-L-cancel-all-typing-and-w…> > > As I explain in the link and in my commit log , I have added a confirm > dialog so the user in case he accidentally pressed CMD+L will click no and > his changes will not be lost. I have verified the bug fix with the latest > pharo build. > > > > -- > View this message in context: http://forum.world.st/bug-4993-Typing-cmd-L-cancel-all-typing-and-we-can-t-… > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >

Oct. 13, 2013

Re: [Pharo-dev] Fix Review Needed - Slice query - was Re: bug: [4993] Typing cmd+L cancel all typing and we can't undo it [Terminated]

by Marcus Denker

On Oct 13, 2013, at 7:00 PM, kilon <thekilon(a)yahoo.co.uk> wrote: > how you do that ? I try to find in the slice the method I have changed and I > see it has the whole morphic inside it. Very confusing. > Monticello always snapshots the whole package even for a one-character change. Marcus

Oct. 13, 2013

Re: [Pharo-dev] Fix Review Needed - Slice query - was Re: bug: [4993] Typing cmd+L cancel all typing and we can't undo it [Terminated]

by Marcus Denker

On Oct 13, 2013, at 6:36 PM, btc(a)openinworld.com wrote: > As I reviewed the Slice <Changes> related to Case 4993, I notice the relevant part was only a single method, but also included were several more unrelated modifications with zero-sum refactorings. eg, from... > position: aPoint > super position: aPoint. > self viewBox ifNotNil: [self viewBox: (aPoint extent: self viewBox extent)]. > > to... > position: aPoint > super position: aPoint. > self viewBox ifNotNil: [:viewBox | self viewBox: (aPoint extent: viewBox extent)]. > > which itself is cool, but my first thought was that these shouldn't have been included in the Case 4993 Slice, but in a separate Slice for a different Case that dealt just with those refactorings. But thinking further in general the image I use for testing could have moved on from the image used to generate that Slice. So maybe its not not such a problem anyhow? > Also, if the zero-sum refactoring modifications were put in their own separate Slice, then probably the specific modifications related to the Case would build upon that, so ultimately you end up with the same situation. > > So in short my question is, how much do you typically separate out Case-specific modifications from incidental zero-sum refactoring made along the way. > In theory: yes. In practice: just too much work. I often slip in small refactorings with other changes (and code deletionsâ¦ nothing works less than asking "There is this obscure feature that nobody used in 20 years, can I remove it?" The answer always will be "Wow, this is cool, over my dead body!". If people would know what I removed over the yearsâ¦ ;-) Marcus

Oct. 13, 2013

Re: [Pharo-dev] bug: [4993] Typing cmd+L cancel all typing and we can't undo it [Terminated]

by Marcus Denker

On Oct 13, 2013, at 7:11 PM, btc(a)openinworld.com wrote: >> >> Normally the first step is "fix review needed". Then someone else needs to check if this is ok (not any small mistake, problem really solved), "fix to include" should be the state >> when it is guaranteed that is can be included without check and thinking. >> >> Marcus >> > > After loading the slice, as well as some functional testing, would you typically run all tests in TestRunner, or just those associated with the modified package ? > running tests is slow, so in the end people (hum, that is, me ;-) forget to even run the tests of the package. > Also at which point does the monkey do its checking? > Sadly the monkey is sick right nowâ¦ we need to fix it. Marcus

Oct. 13, 2013