- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Zinc/Zodiac Documentation

by Sean P. DeNigris

Sven Van Caekenberghe wrote > > Now that I have recovered from the intensive Pharo Conference, I found the > time to publish the Zinc and Zodiac documentation. > ... > http://zn.stfx.eu/zn/zinc-http-components-paper.html > http://zdc.stfx.eu/zodiac-paper.html > Wow, really clear and thorough. The way the raw internet protocols are woven into the examples is really cool (I always have to be reminded that there's no magic, just binary turtles all the way down)... And I found numberOfRetries:, retryDelay:, contentReader:, and #enforceHttpSuccess: particularly useful in simplifying my code A few thoughts: * ZnClient>>retryDelay: - it'd be nice if it took aDuration. If I was reading someone else's code, "client retryDelay: 30" forces me to find the method, but "client retryDelay: 30 seconds" is clear - I think it should return self, like enforceHttpSuccess:. Besides consistency, it will avoid having to send #yourself when configuring a new client instance. * JSJsonParser - where does this class live? A reference would be great... * FileSystem - I remember you mentioned having a problem with FS. Has this been solved? There is a slice in the inbox which replaces all uases of FileDirectory and friends with FS. Also, how will this effect portability (e.g. to Squeak). If you make Zn depend on FS, is the Pharo (renamed classes) version of FS loadable in Squeak trunk? * [up/down]load convenience methods - What do you think about adding e.g. ZnEasy>>download:to: & upload:to: (is POST a good default?) -- View this message in context: http://forum.world.st/Zinc-Zodiac-Documentation-tp4632114p4632508.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

May 30, 2012

Re: [Pharo-project] moving Finder up to first level of World menu

by Ben Coman

Benjamin wrote: > +1 :) > > You can also use the finder plugin for Nautilus made by Damien Cassou :) > > Ben > Thanks. I'll try it. > On May 30, 2012, at 11:43 AM, Ben Coman wrote: > > >> Has any consideration been given to moving World > Tools > Finder up to World > Finder. >> I find this is core to my work flow and I it is used much more often than any of System Browser, Workspace, Test Runner or Monticello Browser - and I wonder if anyone finds the same? >> >> cheers -ben >> >> > > > >

May 30, 2012

Re: [Pharo-project] moving Finder up to first level of World menu

by Benjamin

+1 :) You can also use the finder plugin for Nautilus made by Damien Cassou :) Ben On May 30, 2012, at 11:43 AM, Ben Coman wrote: > > Has any consideration been given to moving World > Tools > Finder up to World > Finder. > I find this is core to my work flow and I it is used much more often than any of System Browser, Workspace, Test Runner or Monticello Browser - and I wonder if anyone finds the same? > > cheers -ben >

May 30, 2012

Re: [Pharo-project] moving Finder up to first level of World menu

by Sean P. DeNigris

btc wrote > > - and I wonder if anyone finds the same? > Yes, I always add that in my images (as well as commands to build fresh 1.3/1.4/etc image, and open the issue tracker/jenkins in a browser). -- View this message in context: http://forum.world.st/moving-Finder-up-to-first-level-of-World-menu-tp46324… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

May 30, 2012

[Pharo-project] moving Finder up to first level of World menu

by Ben Coman

Has any consideration been given to moving World > Tools > Finder up to World > Finder. I find this is core to my work flow and I it is used much more often than any of System Browser, Workspace, Test Runner or Monticello Browser - and I wonder if anyone finds the same? cheers -ben

May 30, 2012

Re: [Pharo-project] Glamorous Inspector

by Igor Stasenko

On 30 May 2012 16:47, Camillo Bruni <camillo.bruni(a)inria.fr> wrote: > I'm trying to load the Glamorous Inspector in 2.0. > Besides some difficulties with non-present versions in some > Configs (RB and Co) I got the thing more or less running. > > However it doesn't find BorderedSubpaneDividerMorph, any chance where I might find this class? > in trash bin: http://code.google.com/p/pharo/issues/detail?id=5193 > best > cami > > -- Best regards, Igor Stasenko.

May 30, 2012

Re: [Pharo-project] Classes that implement unsafe #=

by Mariano Martinez Peck

> >> > > Ok, I will do that. Now, I would like to keep > #testAllClassesImplementSafeEqualsMethod somewhere for the future. But I > cannot find a good existing class/package for it? ideas? > forget about the test since it is not 100% accurate. We still need human intervation. Anywya, I publish a slice with the fixes to those classes I think that need to be fixed. If anyone can review: http://code.google.com/p/pharo/issues/detail?id=5997 cheers > >> and btw...the automatic #hash and #= generator, shouldn't use #species >> rather then #classes to? >> >> thanks >> >> Yes, I've never used those :) >> >> Cheers, >> Henry >> > > > > -- > Mariano > http://marianopeck.wordpress.com > > -- Mariano http://marianopeck.wordpress.com

May 30, 2012

Re: [Pharo-project] Classes that implement unsafe #=

by Mariano Martinez Peck

On Wed, May 30, 2012 at 3:32 PM, Henrik Sperre Johansen < henrik.s.johansen(a)veloxit.no> wrote: > On 30.05.2012 15:02, Mariano Martinez Peck wrote: > > > > On Wed, May 30, 2012 at 2:37 PM, Henrik Sperre Johansen < > henrik.s.johansen(a)veloxit.no> wrote: > >> On 30.05.2012 14:05, Mariano Martinez Peck wrote: >> >>> Hi guys. I found a problem while working with FuelPreview where we store >>> objects of the graph in a Set. While doing a collect, there was an error >>> because an implementation of #= was assuming that the argument was of a >>> certain shape. Of course, that should answer false instead. So I wrote this >>> test to see all existing wrong implementations: >>> >>> testAllClassesImplementSafeEqualsMethod >>> "This tests that all classes in the system that implements #= do it in a >>> way that they don't throw error when passing as an argument something >>> different from expected. The correct behavior is that #= answers false." >>> | wrongClasses | >>> wrongClasses := IdentityDictionary new. >>> ((SystemNavigation default allImplementorsOf: #=) >>> collect: [:each | each methodClass]) >>> do: [:each | >>> | instance | >>> "Some classes like CompiledMethod override basicNew to >>> throw an error. >>> In any case, the comparison will be false, so no problem" >>> [instance := each basicNew] on: Error do: []. >>> [instance = Object new] >>> on: Error >>> do: [: err | wrongClasses at: each put: err ]]. >>> self assert: wrongClasses isEmpty >>> >>> >>> The result is: {Magnitude. WideCharacterSet. KMKeymap. MCMockDefinition. >>> ScaledDecimal. MCSnapshot} >>> >>> So, my I think we should change #= in those classes by adding: >>> >>> self == aKeymap >>> ifTrue: [ ^ true ]. >>> self class = aKeymap class >>> ifFalse: [ ^ false ]. >>> >>> at the beginning of the #= >>> >>> what do you think? if agree, I open an issue. >>> >>> >>> -- >>> Mariano >>> http://marianopeck.wordpress.com >>> >>> I'd test against self species rather than self class, since it gives >> greater flexibility for user-defined instances to potentially = classes in >> the system. >> >> In other word, #class has a very strict meaning which would hinder >> extensibility, #species less so. >> >> > Ok, I see. But the classes are only a few (five). So you recommend you use > self species instead of self class even if we "analyze" those 5 classes to > see if it is worth it or not (for example, we check if they do override > #species or not) ? > > Yes. > The default implementation of #species in Object uses the class primitive > directly, so there's no overhead. > > The benefit is that I could write a custom MyMagnitude class, override > species: > species > ^Magnitude > > and not have to override the base system Magnitude = implementation in > order to compare with MyMagnitude instances and have a true result. > In other words, using species in #= even if it's not needed, is setting a > good example. > > > Ok, I will do that. Now, I would like to keep #testAllClassesImplementSafeEqualsMethod somewhere for the future. But I cannot find a good existing class/package for it? ideas? > > and btw...the automatic #hash and #= generator, shouldn't use #species > rather then #classes to? > > thanks > > Yes, I've never used those :) > > Cheers, > Henry > -- Mariano http://marianopeck.wordpress.com

May 30, 2012

[Pharo-project] Glamorous Inspector

by Camillo Bruni

I'm trying to load the Glamorous Inspector in 2.0. Besides some difficulties with non-present versions in some Configs (RB and Co) I got the thing more or less running. However it doesn't find BorderedSubpaneDividerMorph, any chance where I might find this class? best cami

May 30, 2012

Re: [Pharo-project] Log framework

by Mariano Martinez Peck

see http://book.pharo-project.org/book/LanguageAndLibraries/LoggingTools/ On Wed, May 30, 2012 at 4:08 PM, Ben Coman <btc(a)openinworld.com> wrote: > Marcus Denker wrote: > >> On May 30, 2012, at 10:03 AM, Sven Van Caekenberghe wrote: >> >> >> >>> On 30 May 2012, at 01:56, Santiago Bragagnolo wrote: >>> >>> >>> >>>> Im looking for a log framework with configurable levels. Theres any >>>> stable and useful? I browsed the list and didn't find nothing but >>>> something like 'every body has its own logging framework'. >>>> I wrote a small logging fwk for my project, but if is any more >>>> complete, it would be great. >>>> >>>> >>> There is one logging framework already in your image: Zinc-HTTP-Logging. >>> It is based on Announcments. Although it is part of Zn, it is general >>> purpose. >>> What is special is that it logs the process ID as well, which is useful >>> to debug multiprocess applications. >>> See the Zn documentation for more info. >>> >>> >>> >> >> We should really think about promoting one framework to be the >> one-and-only to be used in the image itself... >> >> Marcus >> >> -- >> Marcus Denker -- http://marcusdenker.de >> >> >> >> >> > Or a defined API that can be swapped out underneath for different > implementations. > > -- Mariano http://marianopeck.wordpress.com

May 30, 2012