- Pharo-dev - lists.pharo.org

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

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

by Stefan Marr

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] How to get the list of packages of a repository?

by Mariano Martinez Peck

Excellent. Thanks guys :) Wouldn't make sense to have that code in a #allPackagesNames ? 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

Nov. 7, 2011

[Pharo-project] Task List

by Sean P. DeNigris

I think the task list would be much more useful and easy to use if we follow Mac OS X's interaction semantics. Currently, in Pharo's non-keepOpen mode, the morph disappears every time you unpress the arrow key, so you're limited to a brief tease as the morph flashes for an instant, or trying to play roulette and unpress the arrow at just the right time as the tasks scroll by at lightning speed. In the keepOpen mode, the morph stays in place until you make your choice, which is nice, but making the choice requires an extra key press (enter). On the Mac, the shortcut opens the UI, which stays open as you hold the modifier key and repeatedly press the shortcut character key. When the modifier key is unpressed, the choice is accepted. Sean -- View this message in context: http://forum.world.st/Task-List-tp4014056p4014056.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Nov. 7, 2011

[Pharo-project] [update 1.4] #14221

by StÃ©phane Ducasse

14221 ----- - Issue 4941: Failing Test: ArrayTest. Thanks Clara Allende. http://code.google.com/p/pharo/issues/detail?id=4941 - Issue 4985: Object>>log: -> Object>>trace: (part one) http://code.google.com/p/pharo/issues/detail?id=4985 - Issue 4982: FlatMessageListBrowser error on remove http://code.google.com/p/pharo/issues/detail?id=4982 Stef

Nov. 7, 2011

Re: [Pharo-project] Instantiating from a Symbol

by StÃ©phane Ducasse

Warm welcome Markus! > I am fairly new to ST and have been following this list since a few weeks. > > A very brief introduction of myself: > I am a 32 year old student of informatics with a degree in political sciences. Currently i am located in Regensburg, Germany. Most of my previous programming was in python, along with some php and javascript. > > 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 > > Such that: > #Foo asClass new -> a Foo > whereas asClass is the method I am looking for. > > I am using Pharo 1.3. > > I did not find any description of what I want to achieve on the internet. > > Many thanks in advance, > Markus >

Nov. 7, 2011