- Pharo-dev - lists.pharo.org

[Pharo-project] Monticello Speedup!
by Fernando Olivero May 31, 2012

May 31, 2012

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

3 2

Re: [Pharo-project] moving Finder up to first level of World menu
by Fernando Olivero May 31, 2012

May 31, 2012

NICE. Excellent summary, thanks Mariano. gracias totales! Fernando pd: i will start using Spotlight right away! On Thu, May 31, 2012 at 10:27 AM, Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: > > > On Thu, May 31, 2012 at 10:18 AM, Fernando Olivero <fernando.olivero(a)usi.ch<mailto:fernando.olivero@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<mailto:stephane.ducasse@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 >

1 0

Re: [Pharo-project] moving Finder up to first level of World menu
by Fernando Olivero May 31, 2012

May 31, 2012

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 >>>>> >>>> >>>> >>> >>> >> >> > >

2 1

[Pharo-project] Classes that implement unsafe #=
by Mariano Martinez Peck May 31, 2012

May 31, 2012

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

4 9

[Pharo-project] moving Finder up to first level of World menu
by Ben Coman May 31, 2012

May 31, 2012

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

4 6

[Pharo-project] [ANN] NativeBoost 1.2 version released (#development)
by Igor Stasenko May 31, 2012

May 31, 2012

Hi, there i prepared new Metacello configuration of NativeBoost. Here the list of changes: Integer>>#| in AsmJit now - added a recursion detecting/handling via notifications - NBExternalHandle / NBExternalAddress is no longer subclasses of NBExternalStructure - more safer way to handle finalizing external objects survived from old session - avoid recursion when printing external struct fields - default alignment of external struct is machine word size - correct padding between struct fields (need to test) - ** fix ** conceptual bug when passing a struct by value. Now copying its contents on stack, instead of passing pointer - rewrote accessing struct fields, allowing nested structs - added #size_t type and NBSizeT marshaller - use stack pointer directly by getting it's address (via stackPointerAddress() available in Cog), so accessing ST stack is faster.. - added recursion guards in NBInterpreterProxy and in NBNativeCodeGen to prevent runaway train(s) - NBExternalType >> #typeSize answers the number of bytes which value of full type (including ptr arity) variable takes place in memory. NBExternalType >> valueSize is the number of bytes for base type (excluding pointers) takes in memory. NBExternalType >> stackSize taking into account stack argument alignment ------------------------- The main change is handling correctly passing structs by value. Before i was wrongly assuming that if function takes struct: int foo ( struct x a) you need to push the pointer to struct.. but in fact you need to copy struct contents on stack! This means that all function signatures which were written based on this wrong assumption should be changed to pass a pointer (if function takes a pointer to struct). So, don't be so haste to use it with Athens with new version of NB. It will definitely break (and i know where) because of this mistake. Fortunately, most of the libraries avoid passing structs by value, so most of the bindings should still keep working fine after update. But be warned about it! Thanks Luc for pointing out on this issue. Another improvement is because of more correct handling of structs, now NB allows nested structs. I blessed this version as #development. If no serious bugs will be found, after testing it with Athens and NBOpenGL (+ add your projects) i will change blessing to #release. -- Best regards, Igor Stasenko.

4 5

[Pharo-project] omni browser
by Milan Mimica May 31, 2012

May 31, 2012

I don't get it. What do I do to load a working OmniBrowser in latest Pharo 1.4? -- Milan Mimica http://sparklet.sf.net

3 5

[Pharo-project] Blog.
by Santiago Bragagnolo May 30, 2012

May 30, 2012

Hi all again, im writting to announce the opening of a new blog of mine. http://concretetypeinference.blogspot.com.ar/ Here ill write, organize my new knowledge and broadcast news about the concrete-types inference project. I was broadcasting just via twitter, but this way is better. (From now on, on twitter i'll just paste url with the related hashtags ) That's all. Keep tunned. Santiago.

3 2

[Pharo-project] Nautilus doesn't like Vistary theme
by Sean P. DeNigris May 30, 2012

May 30, 2012

When selecting a method, sometimes the code pane turns into the dreaded "big red X". Issue 5994: Nautilus doesn't like Vistary theme http://code.google.com/p/pharo/issues/detail?id=5994 -- View this message in context: http://forum.world.st/Nautilus-doesn-t-like-Vistary-theme-tp4632292.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

7 7

[Pharo-project] [update 2.0] #20101
by Marcus Denker May 30, 2012

May 30, 2012

20101 ----- Issue 5987: Remove SARInstaller http://code.google.com/p/pharo/issues/detail?id=5987 Issue 5979: Method names containing shortcut broken http://code.google.com/p/pharo/issues/detail?id=5979 Issue 5696: Failing tests: Traits http://code.google.com/p/pharo/issues/detail?id=5696 -- Marcus Denker -- http://marcusdenker.de

2 1