November 2011 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Instantiating from a Symbol

by Eliot Miranda

On Mon, Nov 7, 2011 at 3:21 PM, Markus Rother <smalltalk(a)markusrother.de>wrote: > On 11/07/2011 11:08 PM, StÃ©phane Ducasse wrote: > > > The issue I could not solve on my own is this: > I would like to instantiate from symbols. My use-case is a collection of class names which I want to ask to return one instance each. > > why are you trying to do? > because symbols are not done to be instantiated like that. > > aString asSymbol is instantiating symbols for you. > > Stef > > > Thanks everybody for the kind, plenty and swift replies. > > Here is what I was up to: > > ChessBoard class>>newGame > | newBoard | > ... > firstRow := #(Rook Knight Bishop Queen King Bishop Knight Rook). > 1 to: 8 do: [ :col | > (newBoard at: 1 at: col) putFigure: (firstRow at: col) asClass > newWhite > ]. > ... > > Symbol>>asClass > ^(Smalltalk classNamed: self) > > > I don't see how a string representation would have helped me here...? > Although, I am a noob, my intuition tells me that symbols are absolutely > fine, here - especially considering they are used precisely for that > purpose internally. > But so is ChessBoard class>>newGame | newBoard | ... firstRow := {Rook. Knight. Bishop. Queen. King. Bishop. Knight. Rook}. 1 to: 8 do: [ :col | (newBoard at: 1 at: col) putFigure: (firstRow at: col) newWhite ]. ... as could be newBoard at: 1 put: ({Rook. Knight. Bishop. Queen. King. Bishop. Knight. Rook} collect: [:class| class newWhite]; at: 2 put: (1 to: 8) collect: [:ign| Pawn newWhite]; atAll: (3 to: 6) put: (Array new: 8); at: 7 put: (1 to: 8) collect: [:ign| Pawn newBlack]; at: 8 put: ({Rook. Knight. Bishop. Queen. King. Bishop. Knight. Rook} collect: [:class| class newBlack] > > > Greets, > Markus > -- best, Eliot

Nov. 7, 2011

Re: [Pharo-project] Best practices for overrides/extension methods with Monticello and correct packaging?

by Stefan Marr

Hi: On 07 Nov 2011, at 23:38, StÃ©phane Ducasse wrote: > if you look in the scripttloatder you can tell the MC that it should apply a list of package one after the other and not (by default collect all the classes and apply all the change together). Hm, I currently have only one Monticello package. I don't put subpackages currently into different *mcz, but I guess that is the way to go. Thanks Lukas, but that looks like breaking a fly on the wheel. Don't need that kind of complexity just yet. > Now another smart move is to think (if the license allows it) how you can push the hooks that you need to the community like that you are more customization and less override. License: MIT... But, 50% of the stuff is to specific, I think. The following would be a candidate for inclusion: ----- !Parser class methodsFor: '*Omni-Compiler-Kernel' stamp: 'StefanMarr 11/3/2011 21:40'! encoderClassFor: aCompiledMethod ^ aCompiledMethod isBlueBookCompiled ifTrue: [EncoderForV3] ifFalse: [EncoderForV3PlusClosures]! ! !CompiledMethod methodsFor: '*Omni-Compiler-Kernel' stamp: 'StefanMarr 11/3/2011 15:55'! methodNode "Return the parse tree that represents self" | aClass source | aClass := self methodClass. source := self getSourceFor: (self selector ifNil: [self defaultSelector]) in: aClass. ^(aClass parserClass new encoderClass: (aClass parserClass encoderClassFor: self); parse: source class: aClass) sourceText: source; yourself! ! ----- But for instance the following and similar changes aren't generally useful, and probably just an artifact of me being too lazy to do it right: !InstanceVariableNode methodsFor: '*Omni-code generation' stamp: 'StefanMarr 11/3/2011 14:20'! emitCodeForValue: stack encoder: encoder stack push: 1. encoder adjustParseStackForPushInstVar: stack. ^encoder genPushInstVar: index! ! !BytecodeEncoder methodsFor: '*Omni-bytecode generation' stamp: 'StefanMarr 11/3/2011 14:20'! adjustParseStackForPushInstVar: parseStack ^ parseStack! ! Best regards Stefan -- Stefan Marr Software Languages Lab Vrije Universiteit Brussel Pleinlaan 2 / B-1050 Brussels / Belgium http://soft.vub.ac.be/~smarr Phone: +32 2 629 2974 Fax: +32 2 629 3525

Nov. 7, 2011

Re: [Pharo-project] Instantiating from a Symbol

by Markus Rother

On 11/07/2011 11:08 PM, StÃ©phane Ducasse wrote: > >> The issue I could not solve on my own is this: >> I would like to instantiate from symbols. My use-case is a collection of class names which I want to ask to return one instance each. > why are you trying to do? > because symbols are not done to be instantiated like that. > > aString asSymbol is instantiating symbols for you. > > Stef Thanks everybody for the kind, plenty and swift replies. Here is what I was up to: ChessBoard class>>newGame | newBoard | ... firstRow := #(Rook Knight Bishop Queen King Bishop Knight Rook). 1 to: 8 do: [ :col | (newBoard at: 1 at: col) putFigure: (firstRow at: col) asClass newWhite ]. ... Symbol>>asClass ^(Smalltalk classNamed: self) I don't see how a string representation would have helped me here...? Although, I am a noob, my intuition tells me that symbols are absolutely fine, here - especially considering they are used precisely for that purpose internally. Greets, Markus

Nov. 7, 2011

Re: [Pharo-project] Type inference

by Lukas Renggli

There is atyper in the Refactoring Browser, also there is RoelTyper. Lukas On Tuesday, 8 November 2011, Santiago Bragagnolo < santiagobragagnolo(a)gmail.com> wrote: > Hello people. I'm looking for a software for type inference. I know is there a software that does it, but i' dont know the project(s)'s name(s). Can any one guide me :D? > > Thanks in advance. > > > > -- Lukas Renggli www.lukas-renggli.ch

Nov. 7, 2011

[Pharo-project] Type inference

by Santiago Bragagnolo

Hello people. I'm looking for a software for type inference. I know is there a software that does it, but i' dont know the project(s)'s name(s). Can any one guide me :D? Thanks in advance.

Nov. 7, 2011

Re: [Pharo-project] Task List

by Sean P. DeNigris

Sean P. DeNigris wrote: > > when a modifier key is pressed (cmd, option, ctrl), > InputEventSensor>>handleEvent: receives mouse events In fact, as you can see below, letting up on the Cmd key is indistinguishable from moving the mouse #(1 3182055 1073 411 0 0 0 1) "mouse move event buffer" #(1 3183695 1073 411 0 8 0 1) "Cmd pressed event buffer" #(1 3183768 1073 411 0 0 0 1) "Cmd unpressed event buffer" Sean b.t.w. I'm using the Cog Carbon Jit vm from Jenkins with Pharo 1.3 rc -- View this message in context: http://forum.world.st/Task-List-tp4014056p4014193.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Nov. 7, 2011

Re: [Pharo-project] Best practices for overrides/extension methods with Monticello and correct packaging?

by Lukas Renggli

For an example, have a look at the package Helvetia-Loader in http://source.lukas-renggli.ch/helvetia. It verifies the expected sytem, patches Monticello, bootstraps the quasiquoting, replaces the compiler and parser infrastructure in multiple steps, ... Lukas On Monday, 7 November 2011, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > if you look in the scripttloatder you can tell the MC that it should apply a list of package one after the other and not (by default collect all the classes and apply all the change together). > > Now another smart move is to think (if the license allows it) how you can push the hooks that you need to the community like that you are more customization and less override. > Now part two, I hope that we will get a bootstrap working one of these days but for that we need to get time. > > Stef > > On Nov 7, 2011, at 11:29 PM, Stefan Marr wrote: > >> Hi: >> >> I was wondering what the standard approach is to package rather invasive changes to core classes. >> >> >> Currently, I have everything in extension methods that override the existing methods in my own package. >> However, the monticello package is not actually loadable. So, I cannot just load my stuff into a new image via monticello. For instance, I modify #basicNew/#basicNew:, the Parser, the Encoder classes, etc. >> >> With my changes, these things depend on my own classes being properly initialized in the image. >> >> What is the best way to get that into a loadable/bootstrapable state? >> >> Do I need to split up all the stuff into different packages according to dependencies and then make sure that I can load those different packages in a well defined order? >> >> Or is there anything to tell Monticello to be smarter about loading the stuff? >> >> Thanks >> Stefan >> >> -- >> Stefan Marr >> Software Languages Lab >> Vrije Universiteit Brussel >> Pleinlaan 2 / B-1050 Brussels / Belgium >> http://soft.vub.ac.be/~smarr >> Phone: +32 2 629 2974 >> Fax: +32 2 629 3525 >> >> >> > > > -- Lukas Renggli www.lukas-renggli.ch

Nov. 7, 2011

Re: [Pharo-project] Best practices for overrides/extension methods with Monticello and correct packaging?

by StÃ©phane Ducasse

if you look in the scripttloatder you can tell the MC that it should apply a list of package one after the other and not (by default collect all the classes and apply all the change together). Now another smart move is to think (if the license allows it) how you can push the hooks that you need to the community like that you are more customization and less override. Now part two, I hope that we will get a bootstrap working one of these days but for that we need to get time. Stef On Nov 7, 2011, at 11:29 PM, Stefan Marr wrote: > Hi: > > I was wondering what the standard approach is to package rather invasive changes to core classes. > > > Currently, I have everything in extension methods that override the existing methods in my own package. > However, the monticello package is not actually loadable. So, I cannot just load my stuff into a new image via monticello. For instance, I modify #basicNew/#basicNew:, the Parser, the Encoder classes, etc. > > With my changes, these things depend on my own classes being properly initialized in the image. > > What is the best way to get that into a loadable/bootstrapable state? > > Do I need to split up all the stuff into different packages according to dependencies and then make sure that I can load those different packages in a well defined order? > > Or is there anything to tell Monticello to be smarter about loading the stuff? > > Thanks > Stefan > > -- > Stefan Marr > Software Languages Lab > Vrije Universiteit Brussel > Pleinlaan 2 / B-1050 Brussels / Belgium > http://soft.vub.ac.be/~smarr > Phone: +32 2 629 2974 > Fax: +32 2 629 3525 > > >

Nov. 7, 2011

Re: [Pharo-project] Task List

by Sean P. DeNigris

In trying to fix this, I came across "Issue 2695: Tasklist on Mac" [1]. I also found something weird that may be relevant - when a modifier key is pressed (cmd, option, ctrl), InputEventSensor>>handleEvent: receives mouse events (the buffer's first element is 1), not keyboard events (2 as the first element). [1] http://code.google.com/p/pharo/issues/detail?id=2695 -- View this message in context: http://forum.world.st/Task-List-tp4014056p4014104.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Nov. 7, 2011

Re: [Pharo-project] How to get the list of packages of a repository?

by Lukas Renggli

> Wouldn't make sense to have that code in a #allPackagesNames ? It would be kind of strange, because typically on a Gofer instance you need to specify the packages you want to deal with. Lukas > > Thanks! > > On Mon, Nov 7, 2011 at 6:02 PM, Lukas Renggli <renggli(a)gmail.com> wrote: >> >> Simpler: >> >> (Gofer new >> Â Â Â Â disablePackageCache; >> Â Â Â Â squeaksource: 'Seaside30'; >> Â Â Â Â allResolved) >> Â Â Â Â collect: [ :each | each packageName ] as: Set >> >> Lukas >> >> On 7 November 2011 21:21, jannik.laval <jannik.laval(a)gmail.com> wrote: >> > Hi Mariano, >> > You can have all packages in a repository with: >> > ==== >> > repository := MCHttpRepository >> > location: httpUrl >> > user: '' >> > password: '' >> > repository allVersionNames >> > ==== >> > Then you have to select all the last version of each package. >> > A method from Moose that have this behavior: >> > === >> > lastVersionOf: projectName >> > | versions | >> > versions := self fileNames select: [ :f | f beginsWith: projectName , >> > '-' ]. >> > ^ (versions asSortedCollection: >> > [ :v1 :v2 | >> > (v1 >> > copyFrom: (v1 indexOf: $.) + 1 >> > to: (v1 lastIndexOf: $.)) asInteger < (v2 >> > copyFrom: (v2 indexOf: $.) + 1 >> > to: (v2 lastIndexOf: $.)) asInteger ]) last >> > === >> > Cheers, >> > Jannik >> > On Nov 7, 2011, at 17:58 , Mariano Martinez Peck wrote: >> > >> > Hi guys. Is there a way to get a list of packages or packages names of a >> > squeaksource repo?Â For example, I would love to do: >> > >> > Gofer it >> > squeaksource: 'xxx'; >> > allPackages. >> > >> > is that possible? >> > >> > Thanks >> > >> > -- >> > Mariano >> > http://marianopeck.wordpress.com >> > >> > >> > --- >> > JannikÂ Laval >> > >> >> >> >> -- >> Lukas Renggli >> www.lukas-renggli.ch >> > > > > -- > Mariano > http://marianopeck.wordpress.com > > -- Lukas Renggli www.lukas-renggli.ch

Nov. 7, 2011