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

[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

Re: [Pharo-project] bootable Pharo image

by StÃ©phane Ducasse

If you want to help cleaning the event we did some pre studies with igor and the idea is to be able to handle touch event with an pluggable event infrastructure. Stef On Nov 7, 2011, at 5:43 PM, S Krish wrote: > Sometimes small things can fire really big change.. > > This is a tiny but powerful kernel that can launch a thousand ideas.. > > I was working on a Android base as an idea.. / concept.. for touch screen.. with Pharo on top.. but Pharo / Squeak has a lot to mature to handle multi-touch. Give me that.. if that happens this concept is what will make a huge change in the future computing world.. > > On Mon, Nov 7, 2011 at 4:09 PM, Edgar J. De Cleene <edgardec2005(a)gmail.com> wrote: > > > > On 11/3/11 19:39 PM, "Pavel Krivanek" <pavel.krivanek(a)gmail.com> wrote: > > > Hi, > > > > I tried to prepare a bootable Pharo ISO image based on Tiny Core > > Linux. Namely on MicroCore (kernel 3.0.3) that was extended with WiFi > > support. There is standard Pharo 1.3 image with OSProcess and > > CommandShell installed on the Smalltalk side. The resultant image has > > about 37 MB. > > > > Download: > > http://www.windmap.cz/playground/pharo/pharo.iso > > > > If you want to add it directly to your Grub menu, you may do it > > without need of extra partition. To the grub.conf add something like: > > > > title Pharo > > root (hd0,1) > > kernel /boot/pharo/vmlinuz vga=791 quiet > > initrd /boot/pharo/tinycore.gz > > > > where vmlinuz and tinycore.gz are the only files needed from the ISO image. > > > > Remastering: > > > > unpack: > > zcat tinycore.gz | sudo cpio -i -H newc -d > > > > pack: > > find | cpio -o -H newc | gzip -2 > ../tinycore.gz > > > > better compression: > > advdef -z4 tinycore.gz > > > > create ISO (you need unpacked original ISO image): > > /bin/cp -pfr tinycore.gz boot > > mkdir -p newiso > > /bin/cp -pfr boot newiso > > mkisofs -l -J -R -V TC-custom -no-emul-boot -boot-load-size 4 \ > > -boot-info-table -b boot/isolinux/isolinux.bin \ > > -c boot/isolinux/boot.cat -o pharo.iso newiso > > > > Cheers, > > -- Pavel > > > > Pavel: > Many things delayed my trial , but today I was able to burn and try the ISO. > > WWWOOOOOOWWW > > The most amazing piece of Smalltalk related I saw in a long time. > > Just returning home from Smalltalks2011 , wish the next year you could come > to Argentina and I could thanks in flesh and give you as many beers you like > > BRAVO > > Edgar > > > >

Nov. 7, 2011

Re: [Pharo-project] systemChangeNotifier and protocols

by StÃ©phane Ducasse

not from the top of my head. Now I guess you know why we are working (help needed) on SystemAnnouncement to replace changeNotifier with announcement. Stef On Nov 7, 2011, at 4:58 PM, DeNigris Sean wrote: > From ezequiel lamonica Nov 07, 2011; 10:22am >> Hello everybody, >> >> I'm trying to find some message in the SystemChangeNotifier to recognize a new protocol added. >> >> I see this instance method in ClassOrganizer: >> >> notifyOfChangedCategoriesFrom: oldCollectionOrNil to: newCollectionOrNil >> >> (self hasSubject and: [oldCollectionOrNil ~= newCollectionOrNil]) >> ifTrue: [SystemChangeNotifier uniqueInstance classReorganized: self subject]. >> >> But, I don't see when the SystemChangeNotifier handles the new protocol and how added it. >> >> Any help? >

Nov. 7, 2011

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

by Lukas Renggli

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

Nov. 7, 2011

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

by jannik.laval

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

Nov. 7, 2011

Re: [Pharo-project] Instantiating from a Symbol

by Nicolas Cellier

2011/11/7 Sven Van Caekenberghe <sven(a)beta9.be>: > Hi Marcus, > > On 07 Nov 2011, at 15:29, Markus Rother wrote: > >> Hello everybody, >> >> 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. >> >> 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 > > Welcome! > > Traditionally, one would do this: > > Â Â Â Â (Smalltalk at: #String) new > > Smalltalk here is not a class, but a global variable whose value is a SystemDictionary mapping class names to class objects. > > Pharo is working towards less dependency on globals like these, so the new way would be like this: > > Â Â Â Â (self environment at: #String) new > > (Where environment essentially does 'Smalltalk globals'), > > HTH, > > Sven > For a few months, Smalltalk class -> SmalltalkImage (which in fact represents the Smalltalk system) And Smalltalk globals class -> SystemDictionary (the global namespace) Nicolas > > > >

Nov. 7, 2011