June 2012 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] start thinking on summer release of Pharo 1.4

by Philippe Marschall

On 13.06.2012 11:08, Esteban Lorenzano wrote: > Hi, > > I started thinking on next release of Pharo 1.4 (which will be code named "summer", not an ugly number). It's only summer in the northern hemisphere. Eclipse renamed their winter releases because it isn't winter in February in half of the world. Cheers Philippe

June 16, 2012

Re: [Pharo-project] PackageOrganizer packages vs. categories

by Guillermo Polito

On Sat, Jun 16, 2012 at 2:44 PM, Sean P. DeNigris <sean(a)clipperadams.com>wrote: > > StÃ©phane Ducasse wrote > > > > sorry but I do not have the energy to discuss that publicly and via > email. > > The problem is that lot of people want a lotâ¦ and my energy is limited. > > > > I understand your frustration, but if we can't discuss important new > features on the developers list... wt#$@?! > Haha, He will not discuss, but we can :). The migration is also painful right now because system events are a mess. We have SystemChangeNotifier and SystemAnnouncer, and there is a nice hack to keep both working. SystemAnnouncer is registered to SystemChangeNotifier and old system events are magicly coerced, transformed(whatever name you want to put) into system announcements. And RPackage suffers because some clients of it, sends inconsistent events like: - method recategorized when the method was removed - a method removed event with an obsolete class that has no information - recategorizations with categories in nil??? So, my heart tells me that we have to clean that slowly also to lower the system's entropy. I've already moved some SystemChangeNotifier users to System announcer, there are left the senders of #notify:ofAllSystemChangesUsing: and some tests. So, there is a nice spot to attack. Once events are tammed, the Rpackage integration with the rest of the system will be cleaner and clear. > -- > View this message in context: > http://forum.world.st/PackageOrganizer-packages-vs-categories-tp4635069p463… > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > >

June 16, 2012

Re: [Pharo-project] PackageOrganizer packages vs. categories

by Sean P. DeNigris

StÃ©phane Ducasse wrote > > sorry but I do not have the energy to discuss that publicly and via email. > The problem is that lot of people want a lotâ¦ and my energy is limited. > I understand your frustration, but if we can't discuss important new features on the developers list... wt#$@?! -- View this message in context: http://forum.world.st/PackageOrganizer-packages-vs-categories-tp4635069p463… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

June 16, 2012

Re: [Pharo-project] PackageOrganizer packages vs. categories

by Sean P. DeNigris

EstebanLM wrote > > Marcus proposal is good: map RPackage with MCPackage... > That sounds right to me... Mapping packages 1:1 with categories seems like perpetuating the "category = package" hack I thought we were trying to finally fix... Sean -- View this message in context: http://forum.world.st/PackageOrganizer-packages-vs-categories-tp4635069p463… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

June 16, 2012

[Pharo-project] Sound in Gnu/Linux (1.4)

by Bernat Romagosa

Hi list, I'm trying to get sound working in Pharo 1.4 (one-click), but the procedure I used to follow in 1.3 is not working anymore. I copied squak's pulse plugin to Contents/Linux and ran the image with the -vm-sound-pulse flag, then DidIt: SoundService soundEnabled: true, but nothing. I also tried with alsa with worse results, the vm reports no such plugin exists although it's in the right directory. Any clues? Thanks! :) -- Bernat Romagosa.

June 16, 2012

Re: [Pharo-project] PackageOrganizer packages vs. categories

by Esteban Lorenzano

Marcus proposal is good: map RPackage with MCPackage, tag the subcategories (RPackage allow adding attributes). That solve all problems with few difficulties (and well... with time packages will adapt) this provides a transparent migration path, which is what we need. Esteban On Jun 16, 2012, at 12:06 PM, Mariano Martinez Peck wrote: > > > On Sat, Jun 16, 2012 at 5:41 AM, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > I was expecting "PackageOrganizer default packageOfClass: FileSystemError" to > return "FileSystem-Core" but it returned "FileSystem-Core-Kernel", which is > not a package. It's a category, but it's packaged in "FileSystem-Core". Is > this a bug? Will PackageOrganizer go away when RPackage takes over? > > > We have been discussing this with Esteban last Monday. Indeed, there is something that does not work. > With PackageInfo or whatever (before RPackage) you used to have a package and categories. > So for example, the *Monticello* package Fuel has several categories: Fuel-Clusters, Fuel-Collections, Fuel-Errors, etc. > From what I can see in RPackage, those categories are called packages as well. > > So... I can get the RPackage for each of those categories: > > (RPackageOrganizer default packageNamed: 'Fuel-Clusters') classes -> ok > (RPackageOrganizer default packageNamed: 'Fuel-Collections') classes -> ok > etc... > > The problem is that so far you *cannot* get a RPackage representing a Monticello package. This is because a Monticello package could be represented as a *list* of RPackages. > How do I get the classes of the monticello package Fuel? > (RPackageOrganizer default packageNamed: 'Fuel') classes -> does not work > > The problem is that 'Fuel' is considered as an individual RPackage (just as Fuel-Clusters, Fuel-Collections, etc). This problem is that > > MCPackage >> correspondingRPackage > > | symbol | > symbol := Symbol readFromString: '#', self name. > ^ RPackageOrganizer default packageNamed: symbol ifAbsent: [ nil ] > > answers *one* RPackage where actually should be a list. So for example for the MCPackage of 'Fuel' I should get a list of all RPackages (Fuel-Clusters, Fuel-Collections, etc). Then I can do the inject:into or whatever if I want to ask/calculate sutff (like #classes and #extensionMethods). > > Cheers > > > > > > Sean > > -- > View this message in context: http://forum.world.st/PackageOrganizer-packages-vs-categories-tp4635069.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > > > > > -- > Mariano > http://marianopeck.wordpress.com >

June 16, 2012

Re: [Pharo-project] PackageOrganizer packages vs. categories

by StÃ©phane Ducasse

sorry but I do not have the energy to discuss that publicly and via email. The problem is that lot of people want a lotâ¦ and my energy is limited. Stef On Jun 16, 2012, at 12:06 PM, Mariano Martinez Peck wrote: > > > On Sat, Jun 16, 2012 at 5:41 AM, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > I was expecting "PackageOrganizer default packageOfClass: FileSystemError" to > return "FileSystem-Core" but it returned "FileSystem-Core-Kernel", which is > not a package. It's a category, but it's packaged in "FileSystem-Core". Is > this a bug? Will PackageOrganizer go away when RPackage takes over? > > > We have been discussing this with Esteban last Monday. Indeed, there is something that does not work. > With PackageInfo or whatever (before RPackage) you used to have a package and categories. > So for example, the *Monticello* package Fuel has several categories: Fuel-Clusters, Fuel-Collections, Fuel-Errors, etc. > From what I can see in RPackage, those categories are called packages as well. > > So... I can get the RPackage for each of those categories: > > (RPackageOrganizer default packageNamed: 'Fuel-Clusters') classes -> ok > (RPackageOrganizer default packageNamed: 'Fuel-Collections') classes -> ok > etc... > > The problem is that so far you *cannot* get a RPackage representing a Monticello package. This is because a Monticello package could be represented as a *list* of RPackages. > How do I get the classes of the monticello package Fuel? > (RPackageOrganizer default packageNamed: 'Fuel') classes -> does not work > > The problem is that 'Fuel' is considered as an individual RPackage (just as Fuel-Clusters, Fuel-Collections, etc). This problem is that > > MCPackage >> correspondingRPackage > > | symbol | > symbol := Symbol readFromString: '#', self name. > ^ RPackageOrganizer default packageNamed: symbol ifAbsent: [ nil ] > > answers *one* RPackage where actually should be a list. So for example for the MCPackage of 'Fuel' I should get a list of all RPackages (Fuel-Clusters, Fuel-Collections, etc). Then I can do the inject:into or whatever if I want to ask/calculate sutff (like #classes and #extensionMethods). > > Cheers > > > > > > Sean > > -- > View this message in context: http://forum.world.st/PackageOrganizer-packages-vs-categories-tp4635069.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > > > > > -- > Mariano > http://marianopeck.wordpress.com >

June 16, 2012

[Pharo-project] RE : Re: start thinking on summer release of Pharo 1.4

by Philippe Back

I am experimenting with that right now. Seems to work. EnvoyÃ© depuis un mobile Samsung Esteban Lorenzano <estebanlm(a)gmail.com> a Ã©critÂ : Hi, you are asking for two things there: -a sound package for pharo 1.4 (I don't know if it exists, and in any case we cannot add it as a core package, you need to install it and see how it works by yourself) -a working sound plugin for iOS. TBH, while I'm including it in regular compilations, I never tested it, so I don't know if is working properly. Of course, to do games and others, is clear that we need a working sound system into iOS... . Esteban On Jun 15, 2012, at 11:36 PM, phil(a)highoctane.be wrote: > Well, spotlight is really cool indeed. Shift-Space XXX Enter. yay! > > But I like to have a view on several classes and typing HOPRÂ¨helps. > > Same when exploring the system for doing something (like > sound-synthesis for example). > > BTW, any new stuff on the MP3 front? I am looking at the sophie 1.0 > extract of yours. > > As of Pharo 1.4 Summer Release, having a somewhat cleaned up > Sound-synthesis in it would be nice. > > I am currently creating a little game in Smalltalk targeting the iPad > and a game without sound is not that of a game. > > For beginners and motivating people to move aboard the platform, sound > is important to have. > > KR > Philippe > > 2012/6/15 Sean P. DeNigris <sean(a)clipperadams.com>: >> >> philippeback wrote >>> >>> Have been using Nautilus and OB and albeit Nautilus is nicer looking, >>> I find my way better with OB. Especially with the top search bar and >>> categorizing into protocols. More buttons under the lists in OB but I >>> do prefer them actually. >>> >> >> Overall, I like Nautilus' workflow better, but I know what you mean about >> the buttons. Even with the visual feedback, I'm never quite sure if I'm "in" >> class-side mode, or I have to hit the button to "get" class-side mode. I was >> missing the search bar, but with spotlight, it's moot. >> >> Sean >> >> -- >> View this message in context: http://forum.world.st/start-thinking-on-summer-release-of-Pharo-1-4-tp46345… >> Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >> > > > > -- > Philippe Back > Dramatic Performance Improvements > Mob: +32(0) 478 650 140 | Fax: +32 (0) 70 408 027 Mail: > phil(a)highoctane.be | Web: http://philippeback.eu | Blog: > http://philippeback.be > > High Octane SPRL > rue cour Boisacq 101 > 1301 Bierges > Belgium >

June 16, 2012

Re: [Pharo-project] start thinking on summer release of Pharo 1.4

by Esteban Lorenzano

Hi, you are asking for two things there: -a sound package for pharo 1.4 (I don't know if it exists, and in any case we cannot add it as a core package, you need to install it and see how it works by yourself) -a working sound plugin for iOS. TBH, while I'm including it in regular compilations, I never tested it, so I don't know if is working properly. Of course, to do games and others, is clear that we need a working sound system into iOS... . Esteban On Jun 15, 2012, at 11:36 PM, phil(a)highoctane.be wrote: > Well, spotlight is really cool indeed. Shift-Space XXX Enter. yay! > > But I like to have a view on several classes and typing HOPRÂ¨helps. > > Same when exploring the system for doing something (like > sound-synthesis for example). > > BTW, any new stuff on the MP3 front? I am looking at the sophie 1.0 > extract of yours. > > As of Pharo 1.4 Summer Release, having a somewhat cleaned up > Sound-synthesis in it would be nice. > > I am currently creating a little game in Smalltalk targeting the iPad > and a game without sound is not that of a game. > > For beginners and motivating people to move aboard the platform, sound > is important to have. > > KR > Philippe > > 2012/6/15 Sean P. DeNigris <sean(a)clipperadams.com>: >> >> philippeback wrote >>> >>> Have been using Nautilus and OB and albeit Nautilus is nicer looking, >>> I find my way better with OB. Especially with the top search bar and >>> categorizing into protocols. More buttons under the lists in OB but I >>> do prefer them actually. >>> >> >> Overall, I like Nautilus' workflow better, but I know what you mean about >> the buttons. Even with the visual feedback, I'm never quite sure if I'm "in" >> class-side mode, or I have to hit the button to "get" class-side mode. I was >> missing the search bar, but with spotlight, it's moot. >> >> Sean >> >> -- >> View this message in context: http://forum.world.st/start-thinking-on-summer-release-of-Pharo-1-4-tp46345… >> Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >> > > > > -- > Philippe Back > Dramatic Performance Improvements > Mob: +32(0) 478 650 140 | Fax: +32 (0) 70 408 027 Mail: > phil(a)highoctane.be | Web: http://philippeback.eu | Blog: > http://philippeback.be > > High Octane SPRL > rue cour Boisacq 101 > 1301 Bierges > Belgium >

June 16, 2012

Re: [Pharo-project] PackageOrganizer packages vs. categories

by Mariano Martinez Peck

On Sat, Jun 16, 2012 at 5:41 AM, Sean P. DeNigris <sean(a)clipperadams.com>wrote: > I was expecting "PackageOrganizer default packageOfClass: FileSystemError" > to > return "FileSystem-Core" but it returned "FileSystem-Core-Kernel", which is > not a package. It's a category, but it's packaged in "FileSystem-Core". Is > this a bug? Will PackageOrganizer go away when RPackage takes over? > > We have been discussing this with Esteban last Monday. Indeed, there is something that does not work. With PackageInfo or whatever (before RPackage) you used to have a package and categories. So for example, the *Monticello* *package* Fuel has several *categories*: Fuel-Clusters, Fuel-Collections, Fuel-Errors, etc. >From what I can see in RPackage, those *categories* are called *packages*as well. So... I can get the RPackage for each of those categories: (RPackageOrganizer default packageNamed: 'Fuel-Clusters') classes -> ok (RPackageOrganizer default packageNamed: 'Fuel-Collections') classes -> ok etc... The problem is that so far you *cannot* get a RPackage representing a Monticello package. This is because a Monticello package could be represented as a *list* of RPackages. How do I get the classes of the monticello package Fuel? (RPackageOrganizer default packageNamed: 'Fuel') classes -> does not work The problem is that 'Fuel' is considered as an individual RPackage (just as Fuel-Clusters, Fuel-Collections, etc). This problem is that MCPackage >> correspondingRPackage | symbol | symbol := Symbol readFromString: '#', self name. ^ RPackageOrganizer default packageNamed: symbol ifAbsent: [ nil ] answers *one* RPackage where actually should be a list. So for example for the MCPackage of 'Fuel' I should get a list of all RPackages (Fuel-Clusters, Fuel-Collections, etc). Then I can do the inject:into or whatever if I want to ask/calculate sutff (like #classes and #extensionMethods). Cheers > Sean > > -- > View this message in context: > http://forum.world.st/PackageOrganizer-packages-vs-categories-tp4635069.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > > -- Mariano http://marianopeck.wordpress.com

June 16, 2012