- Pharo-dev - lists.pharo.org

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

Re: [Pharo-dev] when I dropped a CS on pharo 30 I get

by StÃ©phane Ducasse

I fixed it and I will produce a bug entry + slice On Oct 13, 2013, at 7:00 PM, StÃ©phane Ducasse <Stephane.Ducasse(a)inria.fr> wrote: > classReorganized: anAnnouncement > > window ifNil: [ ^ self ]. > window isDisplayed ifFalse: [ ^ self ]. > (self selectedClass = anAnnouncement classReorganized or: [ anAnnouncement classReorganized users includes: self selectedClass ]) > ^^^^^^^^^^^^^^^^^^^^ > PseudoClass does not understand users? > > > ifTrue: [ self updateBothView ]

Oct. 13, 2013

Re: [Pharo-dev] Spec + KM Categories

by Benjamin

I do not know :) I should have a look at the Morphic KeyMapping protocol :) Ben On Oct 13, 2013, at 8:24 PM, Camillo Bruni <camillobruni(a)gmail.com> wrote: > I am trying to fix the shortcuts for the Spec Inspectors by introducing proper KMCategories. > Now, what is the way to properly attach the KMCategories to SpecModels?

Oct. 13, 2013

Spec + KM Categories

by Camillo Bruni

I am trying to fix the shortcuts for the Spec Inspectors by introducing proper KMCategories. Now, what is the way to properly attach the KMCategories to SpecModels?

Oct. 13, 2013

Re: [Pharo-dev] New Bug ? MNU for Shortcuts Description

by Camillo Bruni

yes, reported here: https://pharo.fogbugz.com/f/cases/11863/Nautilus-Shortcuts-description-MNU-… On 2013-10-13, at 20:18, kilon <thekilon(a)yahoo.co.uk> wrote: > When I go to System Browser "down arrow" menu and choose Shortcuts > Description it give me a MNU: ByteSymbol >> ChangeTableLayout. > > Is this a known bug ? > > > > -- > View this message in context: http://forum.world.st/New-Bug-MNU-for-Shortcuts-Description-tp4714204.html > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >

Oct. 13, 2013

New Bug ? MNU for Shortcuts Description

by kilon

When I go to System Browser "down arrow" menu and choose Shortcuts Description it give me a MNU: ByteSymbol >> ChangeTableLayout. Is this a known bug ? -- View this message in context: http://forum.world.st/New-Bug-MNU-for-Shortcuts-Description-tp4714204.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Oct. 13, 2013