- Pharo-dev - lists.pharo.org

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

by Mariano Martinez Peck

On Thu, May 31, 2012 at 10:18 AM, Fernando Olivero <fernando.olivero(a)usi.ch>wrote: > How i can install/see plugins for Nautilus? > > http://marianopeck.wordpress.com/2012/05/19/pharo-tips-and-tricks/ cmd+f -> plugin :) > Fernando > > On Thu, May 31, 2012 at 9:44 AM, StÃ©phane Ducasse > <stephane.ducasse(a)inria.fr> wrote: > >>> > >>> Examples than pattern. > >>> because Pattern to me measn something else. > >> > >> I know :) But some people argue the opposite so I just picked :) > >> > >>> > >>> We should also give us access to update spec and nautilus directly > because like that we are not the bottleneck. > >> > >> What o you mean ? > > > > that you should commit directly your changes to nautilus and spec and > that we do not have to do it. > > But right now focus on the paper. Can you create a svn repo? > > > > Stef > > > >> > >> Ben > >> > >>> Stef > >>> > >>> On May 30, 2012, at 6:12 PM, Benjamin wrote: > >>> > >>>> +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 > >>>>> > >>>> > >>>> > >>> > >>> > >> > >> > > > > > > -- Mariano http://marianopeck.wordpress.com

May 31, 2012

[Pharo-project] Pharocasts ... updating and screencasts wanted

by Torsten Bergmann

Hi all, http://www.pharocasts.com/ is a little bit outdated since it still shows Pharo 1.3 instead of 1.4. Download linke also goes to 1.3. Would also be nice if someone can record some new screencasts on things like - Nautilus - Roassal - Zinc/Zodiac - New Fuel Release with visual debugging support - Ring - FileSystem - NativeBoost - Nagare logging library - Artefact PDF library - Athens - Working with SS3 - ... and send them to Laurent. Any takers? Thx T. -- Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de

May 31, 2012

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

by Fernando Olivero

How i can install/see plugins for Nautilus? Fernando On Thu, May 31, 2012 at 9:44 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >>> >>> Â Â Â Examples than pattern. >>> Â Â Â because Pattern to me measn something else. >> >> I know :) But some people argue the opposite so I just picked :) >> >>> >>> We should also give us access to update spec and nautilus directly because like that we are not the bottleneck. >> >> What o you mean ? > > that you should commit directly your changes to nautilus and spec and that we do not have to do it. > But right now focus on the paper. Can you create a svn repo? > > Stef > >> >> Ben >> >>> Stef >>> >>> On May 30, 2012, at 6:12 PM, Benjamin wrote: >>> >>>> +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 31, 2012

Re: [Pharo-project] Monticello Speedup!

by Mariano Martinez Peck

On Thu, May 31, 2012 at 10:10 AM, Fernando Olivero <fernando.olivero(a)usi.ch>wrote: > Thanks for making Monticello/Gofer 300% faster! > > +1 > And its non-blocking, now when i commit/merge i dont have to look at > the ceiling for 3 minutes. > > but you get the RSOD (red square of death) :( -- Mariano http://marianopeck.wordpress.com

May 31, 2012

[Pharo-project] Monticello Speedup!

by Fernando Olivero

Thanks for making Monticello/Gofer 300% faster! And its non-blocking, now when i commit/merge i dont have to look at the ceiling for 3 minutes. Fernando

May 31, 2012

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

by Mariano Martinez Peck

On Thu, May 31, 2012 at 5:37 AM, Chris Muller <asqueaker(a)gmail.com> wrote: > Another flexible option could be to test it respondsTo: each attribute > being used for comparison. > Indeed, but on the other hand it could be slow ;) > > > On Wed, May 30, 2012 at 8:32 AM, 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. > > > > > > > > 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 31, 2012

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

by StÃ©phane Ducasse

>> >> Examples than pattern. >> because Pattern to me measn something else. > > I know :) But some people argue the opposite so I just picked :) > >> >> We should also give us access to update spec and nautilus directly because like that we are not the bottleneck. > > What o you mean ? that you should commit directly your changes to nautilus and spec and that we do not have to do it. But right now focus on the paper. Can you create a svn repo? Stef > > Ben > >> Stef >> >> On May 30, 2012, at 6:12 PM, Benjamin wrote: >> >>> +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 31, 2012

Re: [Pharo-project] [ANN] NativeBoost 1.2 version released (#development)

by StÃ©phane Ducasse

thanks a lot for all that good work. On May 31, 2012, at 2:33 AM, Igor Stasenko wrote: > Update: > i synchronized Athens Cairo backend with latest changes in NativeBoost. > > ConfigurationOfAthens version 1.2 > is now working with NB v 1.2 > > (same version numbers are just coincidence) > > > -- > Best regards, > Igor Stasenko. >

May 31, 2012

Re: [Pharo-project] Log framework

by Santiago Bragagnolo

Hi again Im already add several classes to the logger. http://ss3.gemstone.com/ss/PaulLePulp the way to use it still primitive, but is a nice draft. If you look at LogConfiguration configuration (class method) you'll find something like this self for:[ :builder | builder forClass:LogTestObject useLevel:#info showingLogAs: ('[%pid | %tstmp | %tag] #%class >> %selector' asPatternFormatter) into: Transcript asLogWriter retain:true. builder forKey:'default' useLevel:#error. ] then, with LogTestObject, if you send it "error", "warn" or "info", all you send there (blocks, strings, symbols or what-understand-value) will be showed at Transcript. (im didnt test on file or stdout yet) Finally retain:true adds the log to LogHolder, which responds to LogHolder instance select:[ :log | log whatYouWantToTest ]. Ill be testing tomorrow and fixing, but, if you want to see and advise me, you are welcome :) Ok, is 4am, im going to sleep 2012/5/30 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > I would like a logging mechanism that manipulate objects that then are > printed in various format. > The compiler could use such logger > > I did not look at the code of toothpick probably extending LoggingEvent > should do it. > > Stef > > > On May 30, 2012, at 3:41 PM, Santiago Bragagnolo wrote: > > > Ok, i'll take what i need from the marianito's and zn and fork them in > an other package, add what i need for massive loggin (like levels of > loggin) and make a log-framework. > > > > Any names? clairvoyant :3? > > > > Then, is any easy aspect fwk that could i use for the logger? (sometimes > i need just trace runtime, or i dont want to add a log line one by one) > that works in pharo 2.0 ? :P? > > > > > > 2012/5/30 Sven Van Caekenberghe <sven(a)beta9.be> > > > > 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. > > > > Sven > > > > > > > > >

May 31, 2012

Re: [Pharo-project] omni browser

by Milan Mimica

On 31 May 2012 00:27, Guillermo Polito <guillermopolito(a)gmail.com> wrote: > > Thats because it loads the default group. > > Try with this script after loading the configuration from > MetacelloRepository: > > Gofer it > squeaksource: 'MetacelloRepository'; > package: 'ConfigurationOfOmniBrowser'; > load. > > (ConfigurationOfOmniBrowser > project version: #stable) load: #( 'Dev' 'Dev Tests'). > Ah! Took me two days. Bye bye Nautilus! -- Milan Mimica http://sparklet.sf.net

May 31, 2012