- Pharo-dev - lists.pharo.org

[Pharo-project] [update 2.0] #20123
by StÃ©phane Ducasse June 10, 2012

June 10, 2012

20123 ----- - Issue 6043: Unused ivs in SystemNavigation. Thanks Camille Teruel. http://code.google.com/p/pharo/issues/detail?id=6043. - Issue 6033: RPackageOrganizer should use the private announcer and not the public one. http://code.google.com/p/pharo/issues/detail?id=6033. - Issue 6016: privateAnnouncer is not used and this is not good. http://code.google.com/p/pharo/issues/detail?id=6016 Stef

1 0

[Pharo-project] Nautilus & Trats
by Igor Stasenko June 10, 2012

June 10, 2012

Hi, i have many DNU's when working with Nautilus and coding traits.. - browsing trait's class side -> DNU - changing/adding new methods -> DNU please check that -- Best regards, Igor Stasenko.

1 0

[Pharo-project] Enhancement - version history to include class and method renames
by Ben Coman June 10, 2012

June 10, 2012

Since <Versions> shows both the class name and method name, it would be useful to have class and method renames to have that show up in the version history. Use case: 1. PersonA creates a ClassA and methodA. <Versions> shows the author of ClassA>methodA as PersonA. 2. PersonB renames classA to classB. <Versions> shows the author of ClassB>methodA as PersonA. Where as I think the guilty party should show as PersonB. cheers -ben

1 0

Re: [Pharo-project] [Pharo-users] Fuel FLMethodChanged error
by Mariano Martinez Peck June 9, 2012

June 9, 2012

On Fri, Jun 8, 2012 at 1:41 AM, Paul DeBruicker <pdebruic(a)gmail.com> wrote: > On 06/07/2012 02:25 PM, Mariano Martinez Peck wrote: > >> | serializer | >> serializer := FLSerializer newFull. >> serializer serialize: xxx on: aStream. >> >> and tell me if that also work? >> > > > > After loading FuelMetaLevel as Martin suggested the above code works to > serialize and materialize the problematic domain objects just fine. > Ok, just to clarify: when you install the package Fuel only, and in your graph you have entities like classes or methods, they will be considered "global", that is, we just store the class name and selector and during materialization we search it in the Smalltalk globals. If the class/method is not present, we throw an error. Now...closures are more complicated because you can even EVALUATE them. If the method surrounding the closure has changed in the image you are materializing, evaluating the closure (depending on the change in the method) can even crash your VM. Because of that, when serializing methods "as globals" we also store a chemsum and we compare during materialization to see that it hasn't change it. If changed, we throw the FLMethodChanged. With the package FuelMetalevel, and by using #newFull the serializer will consider the method as "full" so it will be fully serialized, and therefore you don't have the problem of the checksum. Anyway, you found a bug because you should not be needing FuelMetalevel since you are serializing and materializing in the same image. We will investigate it. Thanks -- Mariano http://marianopeck.wordpress.com

1 1

[Pharo-project] [update 2.0] #20122
by StÃ©phane Ducasse June 9, 2012

June 9, 2012

20122 ----- - Issue 6044: Nautilus Method Rename. Thanks Benjamin van Ryseghem. http://code.google.com/p/pharo/issues/detail?id=6044 - Issue 5487: Deferring the calculation of the failure description string in TestCases. Thanks Stefan Marr. http://code.google.com/p/pharo/issues/detail?id=5487 + cleaning all hardcoded references to TestResult, TestResource and TestSuite. - Issue 6049: Monticello Browser repository List and repositories out of sync when searching. Thanks Dan Uber. http://code.google.com/p/pharo/issues/detail?id=6049

1 0

[Pharo-project] What can be negative regarding timezones with date-related objects?
by Mariano Martinez Peck June 9, 2012

June 9, 2012

Hi guys. Imagine in Fuel I am serializing date/time-related objects sending these messages: aDate julianDayNumber. aDateAndTime julianDayNumber. aDateAndTime nanoSecond. aDateAndTime secondsSinceMidnight. aDateAndTime offset asSeconds. aDateAndTime offset nanoSeconds. aDuration asSeconds. aDuration nanoSeconds. aTime asSeconds. aTime nanoeSecond. which of those things could answer negative numbers? because once I remember in my image everything was positive, but in other timezone I think "offset asSeconds" and "offset nanoSeconds" were negative in DateAndTime. thanks! -- Mariano http://marianopeck.wordpress.com

3 9

[Pharo-project] [update 2.0] #20121
by StÃ©phane Ducasse June 9, 2012

June 9, 2012

20121 ----- - Issue 5873: [BUG]: ZipArchive does not correctly zip hierarchies. Thanks Sean de Nigris. http://code.google.com/p/pharo/issues/detail?id=5873

1 0

[Pharo-project] Monticello Browser repository search problem
by Daniel Uber June 9, 2012

June 9, 2012

I submitted a slice for Issue 6049. If you search for a repo in Monticello browser, the list of names updates, but the repositories array is kept the same. So if you open a selected repo after searching, the wrong repository opens (index of selection in the list does not match index of the repository with that name). I tested this in Pharo-1.4, and Pharo-2.0, and it appears to fix the issue. Dan Uber

2 1

June 9, 2012

20120 ----- - Issue 5969: [ENH]: Clean SystemProgressMorph and friends (Part 2) ProgressBarPartTwo. Thanks a lot Sean and Guillermo for the hand. http://code.google.com/p/pharo/issues/detail?id=5969 Stef

1 0

June 9, 2012

20119 ----- Preparing ProgressBarMorph integration

1 0