[Pharo-dev] [SO] Can't launch Pharo2 on Windows 8.1
http://stackoverflow.com/questions/22468130/pharo-smalltalk-dont-open-windows-8
[Pharo-dev] Fwd: pharo sound should be working
Begin forwarded message: From: xavier MESSNER xmess...@gmail.com Subject: Re: [Pharo-dev] pharo sound should be working Date: 17 Mar 2014 22:12:30 GMT+1 To: Stéphane Ducasse stephane.duca...@inria.fr Salut Stéphane, Les modifications apportées corrigent le problème. Le son fonctionne correctement mais uniquement si le serveur sonore Pulseaudio n'est pas démarré, ce qui n'est pas le cas pour les distributions modernes ou orientées desktop. Pour avoir du son j'ai dû désactiver pulseaudio. Voici comment j'ai procédé. Dans ~/.pulse/client.conf autospawn = no Cela permet de ne pas relancer le service en automatique Ensuite killall pulseaudio Maintenant je suis dans une configuration idéale et j'ai pu rejouer la mélodie de pacman :) Seulement, si le serveur de son pulseaudio est lancé j'ai cela qui apparaît dans la console sound_Start(default) soundStart: snd_add_pcm_handler: Fonction non implantée sound_Start(default) soundStart: snd_add_pcm_handler: Fonction non implantée Je suis bien parti de la dernière version de la vm disponible comme demané. A mon avis lorsqu'on utilise pulseaudio, il y a conflit avec la vm qui elle veut utiliser alsa. Xavier. 2014-03-17 20:03 GMT+01:00 Stéphane Ducasse stephane.duca...@inria.fr: xavier peux-tu reessayer? Begin forwarded message: From: Esteban Lorenzano esteba...@gmail.com Subject: Re: [Pharo-dev] pharo sound should be working Date: 17 Mar 2014 15:45:06 GMT+1 To: Pharo Development List pharo-dev@lists.pharo.org Reply-To: Pharo Development List pharo-dev@lists.pharo.org can you check with the latest vm now? btw… you need to install: sudo apt-get install libasound2-plugins:i386 in order to prevent warnings. On 15 Mar 2014, at 00:03, Nicolai Hess nicolaih...@web.de wrote: 2014-03-14 21:43 GMT+01:00 Esteban Lorenzano esteba...@gmail.com: Hi, so I committed some changes to allow soundplugin to work on the pharovm. can you please download and test in your platforms? Works on windows (remember, in linux you need libasound2 dependency installed) it does not work on linux Ubuntu 12.04.2 LTS (I have installed libasound2). Why don't we include the pulse config again and build the vm-sound-pulse module as well? As I described it in the issue 12493, vm-sound-oss is buildable too. But current linux distribution don't provide the older OSS sound system. (it worked for me with ubuntu 10.04 but not with 12.04) cheers, Esteban
Re: [Pharo-dev] pharo sound should be working
Nicolai, can this be your problem? btw… I can give a try to pulse module, but now now, and not for pharo3… time time time (and you know… it would be an enhancement, not a bug fix… so is for pharo4 :) ) Esteban On 18 Mar 2014, at 09:43, Pharo4Stef pharo4s...@free.fr wrote: Begin forwarded message: From: xavier MESSNER xmess...@gmail.com Subject: Re: [Pharo-dev] pharo sound should be working Date: 17 Mar 2014 22:12:30 GMT+1 To: Stéphane Ducasse stephane.duca...@inria.fr Salut Stéphane, Les modifications apportées corrigent le problème. Le son fonctionne correctement mais uniquement si le serveur sonore Pulseaudio n'est pas démarré, ce qui n'est pas le cas pour les distributions modernes ou orientées desktop. Pour avoir du son j'ai dû désactiver pulseaudio. Voici comment j'ai procédé. Dans ~/.pulse/client.conf autospawn = no Cela permet de ne pas relancer le service en automatique Ensuite killall pulseaudio Maintenant je suis dans une configuration idéale et j'ai pu rejouer la mélodie de pacman :) Seulement, si le serveur de son pulseaudio est lancé j'ai cela qui apparaît dans la console sound_Start(default) soundStart: snd_add_pcm_handler: Fonction non implantée sound_Start(default) soundStart: snd_add_pcm_handler: Fonction non implantée Je suis bien parti de la dernière version de la vm disponible comme demané. A mon avis lorsqu'on utilise pulseaudio, il y a conflit avec la vm qui elle veut utiliser alsa. Xavier. 2014-03-17 20:03 GMT+01:00 Stéphane Ducasse stephane.duca...@inria.fr: xavier peux-tu reessayer? Begin forwarded message: From: Esteban Lorenzano esteba...@gmail.com Subject: Re: [Pharo-dev] pharo sound should be working Date: 17 Mar 2014 15:45:06 GMT+1 To: Pharo Development List pharo-dev@lists.pharo.org Reply-To: Pharo Development List pharo-dev@lists.pharo.org can you check with the latest vm now? btw… you need to install: sudo apt-get install libasound2-plugins:i386 in order to prevent warnings. On 15 Mar 2014, at 00:03, Nicolai Hess nicolaih...@web.de wrote: 2014-03-14 21:43 GMT+01:00 Esteban Lorenzano esteba...@gmail.com: Hi, so I committed some changes to allow soundplugin to work on the pharovm. can you please download and test in your platforms? Works on windows (remember, in linux you need libasound2 dependency installed) it does not work on linux Ubuntu 12.04.2 LTS (I have installed libasound2). Why don't we include the pulse config again and build the vm-sound-pulse module as well? As I described it in the issue 12493, vm-sound-oss is buildable too. But current linux distribution don't provide the older OSS sound system. (it worked for me with ubuntu 10.04 but not with 12.04) cheers, Esteban
Re: [Pharo-dev] FileSystem-Git status update
Thanks a lot for this work. I don't know for others but I hope it will streamline my development workflow :) On Fri, Mar 14, 2014 at 8:38 PM, Esteban Lorenzano esteba...@gmail.comwrote: On 14 Mar 2014, at 13:00, Vincent Blondeau vincent.blond...@polytech-lille.net wrote: Le 14/03/2014 11:11, Max Leske a écrit : Hi everyone I promised to keep you posted about the progress, so here goes: - Esteban and I worked together yesterday and we got callbacks working - I will now do some cleanup so that its actually possible to work on libgit2 (some bindings have changed between versions 0.18 and 0.20 and I need to find out which) - Esteban and I will sit together again on Monday and prepare work for others / implement the object model on top of libgit2. I hope that we can separate tasks so that multiple people can work in parallel In my opinion we should be able to create local repositories, perform commits, switch branches and do checkouts by tuesday next week. Optimistically, fetch and push should also work by the end of the week. But that’s really just conjecture and I’ll keep you all posted. Just a reminder: at the moment we are working to get Git running with NativeBoost *at all*. Plans for abstraction, Monticello - Git, Github etc. should certainly be discussed, but don’t expect those things to be there at the end of next week. Max That's seems cool ! As you will use NativeBoost, do you plan to do it works under Windows 7 ? yep. Guys… the default answer to that is always: yes. Any package/addition is useless if it does not works in all the supported platforms (with possible exception of mobile platforms). Said so… you always has to start from some place… :) Esteban Vincent
[Pharo-dev] get.pharo.org behind proxy
Hi guys, While trying to get pharo using the zeroconf scripts I had some problems due to the proxy server. Is there any way of specifying the proxy to be used. I've tried something like: curl -x server:port get.pharo.org/20+vm | bash but it does not work Cheers -- Dr. Ciprian TEODOROV Ingénieur de Recherche tél : 06 08 54 73 48 mail : ciprian.teodo...@gmail.com www.teodorov.ro
[Pharo-dev] Better catalog builder
Hi guys I improved the catalog builder to take into more sources of configurations. I will add an Error log to identify potential problems. Stef
Re: [Pharo-dev] WhatsUp from: 2014-03-17 until: 2014-03-31
### Here's what I've been up to since the last WhatsUp: Pillar http://www.smalltalkhub.com/#!/~Pier/Pillar - inspector http://www.youtube.com/watch?v=6PrTaROp05c - refactorings - bug fixing Pier - meeting with Stephan Eggermont on how to collaborate for Pier/Pillar Pharo Launcher http://www.smalltalkhub.com/#!/~Pharo/PharoLauncher - the new launcher is 10 times faster when browsing jenkins jobs, give it a try - more improvements Phratch packaging for Ubuntu https://launchpad.net/~pharo/+archive/stable/ - initial release for recent Ubuntu versions ### What's next, until 2014-03-31 (*): Pillar - new stable release Phratch packaging for Ubuntu https://launchpad.net/~pharo/+archive/stable/ - release for Ubuntu Precise -- Damien Cassou http://damiencassou.seasidehosting.st Success is the ability to go from one failure to another without losing enthusiasm. Winston Churchill
Re: [Pharo-dev] get.pharo.org behind proxy
On Tue, Mar 18, 2014 at 10:51 AM, Ciprian Teodorov ciprian.teodo...@gmail.com wrote: curl -x server:port get.pharo.org/20+vm | bash but it does not work this should work for standard proxies I think. Read curl man page for details, there are plenty of --proxy-* options -- Damien Cassou http://damiencassou.seasidehosting.st Success is the ability to go from one failure to another without losing enthusiasm. Winston Churchill
[Pharo-dev] Catalog entry of ConfigurationOfPunQLite is broken
Hi I improved the CatalogBuilder to be more robust but Catalog entry of ConfigurationOfPunQLite is broken Startup Error: MessageNotUnderstood: ByteStringput: ByteString(Object)doesNotUnderstand: #put: ConfigurationOfPunQLite classcatalogKeyClassesAndExample CatalogBuilderbuildKeyClassesFor:on: CatalogBuildercatalogCardBodyFor: in Block: [:s | ... Thanks
Re: [Pharo-dev] get.pharo.org behind proxy
On 18 Mar 2014, at 10:51, Ciprian Teodorov ciprian.teodo...@gmail.com wrote: Hi guys, While trying to get pharo using the zeroconf scripts I had some problems due to the proxy server. Is there any way of specifying the proxy to be used. I've tried something like: curl -x server:port get.pharo.org/20+vm | bash but it does not work The reason this does not work is because the script returned by the first curl call, which is fed to bash, contains more downloads. Try setting the http_proxy environment variable (see man curl) to cover the subsequent calls as well. Cheers -- Dr. Ciprian TEODOROV Ingénieur de Recherche tél : 06 08 54 73 48 mail : ciprian.teodo...@gmail.com www.teodorov.ro
[Pharo-dev] Looking for a project reloader tool
Hi guys I’m starting to get bored to always reload my projects in new images. I would like to have a simple button to say Save script to reload on a project Does any of you implement such behavior? Else I will do it. Stef
Re: [Pharo-dev] Looking for a project reloader tool
On Tue, Mar 18, 2014 at 11:08 AM, Pharo4Stef pharo4s...@free.fr wrote: Does any of you implement such behavior? Else I will do it. Martin wrote a nice script for Epicea that he describes as: You can create a file with this content http://ws.stfx.eu/41W9PEFII4UW in your preferences directory*. This (cute) script installs Epicea after 3 seconds after opening a fresh image; during that time, a big centered cancel button is displayed to help you in a eventual case in which you don't want Epicea to be loaded. *: the preferences directory is a mechanism of Pharo offers for personal scripts. You can know your preferences directory by evaluating this code: FileLocator preferences asFileReference. http://smalltalkhub.com/#!/~MartinDias/Epicea -- Damien Cassou http://damiencassou.seasidehosting.st Success is the ability to go from one failure to another without losing enthusiasm. Winston Churchill
Re: [Pharo-dev] get.pharo.org behind proxy
thanks Sven, it worked like a charm... I was setting HTTP_PROXY instead of http_proxy... On Tue, Mar 18, 2014 at 11:04 AM, Sven Van Caekenberghe s...@stfx.euwrote: On 18 Mar 2014, at 10:51, Ciprian Teodorov ciprian.teodo...@gmail.com wrote: Hi guys, While trying to get pharo using the zeroconf scripts I had some problems due to the proxy server. Is there any way of specifying the proxy to be used. I've tried something like: curl -x server:port get.pharo.org/20+vm | bash but it does not work The reason this does not work is because the script returned by the first curl call, which is fed to bash, contains more downloads. Try setting the http_proxy environment variable (see man curl) to cover the subsequent calls as well. Cheers -- Dr. Ciprian TEODOROV Ingénieur de Recherche tél : 06 08 54 73 48 mail : ciprian.teodo...@gmail.com www.teodorov.ro -- Dr. Ciprian TEODOROV Ingénieur de Recherche tél : 06 08 54 73 48 mail : ciprian.teodo...@gmail.com www.teodorov.ro
Re: [Pharo-dev] Looking for a project reloader tool
One way to do this (restore all your own stuff in a new image) is to use a single configuration ... On 18 Mar 2014, at 11:08, Pharo4Stef pharo4s...@free.fr wrote: Hi guys I’m starting to get bored to always reload my projects in new images. I would like to have a simple button to say Save script to reload on a project Does any of you implement such behavior? Else I will do it. Stef
Re: [Pharo-dev] Looking for a project reloader tool
yes but my projects are often not related. I will try to add a menu in the configurationBrowser to generate nice information such as Gofer it smalltalkhubUser: 'MartinDias' project: 'Epicea'; configuration; loadStable. Gofer it smalltalkhubUser: 'DamienCassou' project: 'Pier-Gutemberg'; package: 'ConfigurationOfCatalog'; load. Stef On 18 Mar 2014, at 11:14, Sven Van Caekenberghe s...@stfx.eu wrote: One way to do this (restore all your own stuff in a new image) is to use a single configuration ... On 18 Mar 2014, at 11:08, Pharo4Stef pharo4s...@free.fr wrote: Hi guys I’m starting to get bored to always reload my projects in new images. I would like to have a simple button to say Save script to reload on a project Does any of you implement such behavior? Else I will do it. Stef
Re: [Pharo-dev] Looking for a project reloader tool
Nice (it is also a single configuration load). BTW, there is something broken with the browser/non-browser detection of the Shared Smalltalk Workspaces server, to force HTML rendering and proper syntax coloring, you can use: http://ws.stfx.eu/41W9PEFII4UW?format=html On 18 Mar 2014, at 11:13, Damien Cassou damien.cas...@gmail.com wrote: On Tue, Mar 18, 2014 at 11:08 AM, Pharo4Stef pharo4s...@free.fr wrote: Does any of you implement such behavior? Else I will do it. Martin wrote a nice script for Epicea that he describes as: You can create a file with this content in your preferences directory*. This (cute) script installs Epicea after 3 seconds after opening a fresh image; during that time, a big centered cancel button is displayed to help you in a eventual case in which you don't want Epicea to be loaded. *: the preferences directory is a mechanism of Pharo offers for personal scripts. You can know your preferences directory by evaluating this code: FileLocator preferences asFileReference. http://smalltalkhub.com/#!/~MartinDias/Epicea -- Damien Cassou http://damiencassou.seasidehosting.st Success is the ability to go from one failure to another without losing enthusiasm. Winston Churchill
Re: [Pharo-dev] Looking for a project reloader tool
On 18 Mar 2014, at 11:42, Pharo4Stef pharo4s...@free.fr wrote: yes but my projects are often not related. What I mean is: make a meta Metacello configuration, ConfigurationOfStef, that loads everything you need by dependency. I will try to add a menu in the configurationBrowser to generate nice information such as Gofer it smalltalkhubUser: 'MartinDias' project: 'Epicea'; configuration; loadStable. Gofer it smalltalkhubUser: 'DamienCassou' project: 'Pier-Gutemberg'; package: 'ConfigurationOfCatalog'; load. That would be a nice add on. Stef On 18 Mar 2014, at 11:14, Sven Van Caekenberghe s...@stfx.eu wrote: One way to do this (restore all your own stuff in a new image) is to use a single configuration ... On 18 Mar 2014, at 11:08, Pharo4Stef pharo4s...@free.fr wrote: Hi guys I’m starting to get bored to always reload my projects in new images. I would like to have a simple button to say Save script to reload on a project Does any of you implement such behavior? Else I will do it. Stef
Re: [Pharo-dev] Looking for a project reloader tool
On Tue, Mar 18, 2014 at 11:46 AM, Sven Van Caekenberghe s...@stfx.euwrote: On 18 Mar 2014, at 11:42, Pharo4Stef pharo4s...@free.fr wrote: yes but my projects are often not related. What I mean is: make a meta Metacello configuration, ConfigurationOfStef, that loads everything you need by dependency. Once, Mariano convinced me to do it this way and it was fine. Additionally, Metacello groups can be used to define multiple unrelated working environments. Currently, I like to use .st startup scripts to define automatic small actions, and trigger Metacello for more complex actions. Martín
Re: [Pharo-dev] Looking for a project reloader tool
Sven Van Caekenberghe wrote: On 18 Mar 2014, at 11:42, Pharo4Stef pharo4s...@free.fr wrote: yes but my projects are often not related. What I mean is: make a meta Metacello configuration, ConfigurationOfStef, that loads everything you need by dependency. I will try to add a menu in the configurationBrowser to generate nice information such as Gofer it smalltalkhubUser: 'MartinDias' project: 'Epicea'; configuration; loadStable. Gofer it smalltalkhubUser: 'DamienCassou' project: 'Pier-Gutemberg'; package: 'ConfigurationOfCatalog'; load. That would be a nice add on. Stef On 18 Mar 2014, at 11:14, Sven Van Caekenberghe s...@stfx.eu wrote: One way to do this (restore all your own stuff in a new image) is to use a single configuration ... On 18 Mar 2014, at 11:08, Pharo4Stef pharo4s...@free.fr wrote: Hi guys I’m starting to get bored to always reload my projects in new images. I would like to have a simple button to say Save script to reload on a project Does any of you implement such behavior? Else I will do it. Stef Maybe the Configuration Browser could tag configurations to be loaded in every new image. If the Startup scripts set a shared global package cache directory [1], that information could be stored there. btw, How common is it to have a shared global package cache directory. Should that be default? What would detract from that? cheers -ben [1] http://marianopeck.wordpress.com/2012/05/19/pharo-tips-and-tricks/
Re: [Pharo-dev] WhatsUp from: 2014-03-17 until: 2014-03-31
Le 17/03/2014 22:49, Max Leske a écrit : - $NEXT_STEPS_TOWARDS_WORLD_DOMINATION - annoy Esteban some more with libgit2 - get other people to work on LibGit This is the project we should look at? http://smalltalkhub.com/#!/~StefanMarr/LibGit/commits - move the repository to the FileSystem-Git-Dev team - get fetch / pull working - try to get the LibGit build working with Moose Thierry -- Thierry Goubier CEA list Laboratoire des Fondations des Systèmes Temps Réel Embarqués 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95
Re: [Pharo-dev] Looking for a project reloader tool
Le 18/03/2014 15:10, Ben Coman a écrit : Maybe the Configuration Browser could tag configurations to be loaded in every new image. If the Startup scripts set a shared global package cache directory [1], that information could be stored there. Hum, then this means that if you work on multiple projects in separate images, all of them will load the same configurations? btw, How common is it to have a shared global package cache directory. Should that be default? What would detract from that? I don't know but it seems that recent Pharo3 build have a tendency to create (or to share) a common cache. Or does that happens when you export settings? Thierry -- Thierry Goubier CEA list Laboratoire des Fondations des Systèmes Temps Réel Embarqués 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95
[Pharo-dev] Just found, i can compile this:
extent: newExtent vertical ifTrue: [ newExtent := self defaultWidth @ newExtent y ] ifFalse: [ newExtent := newExtent x @ self defaultWidth ]. super extent: newExtent Can you verify it? Arguments should be not assignable. -- Best regards, Igor Stasenko.
Re: [Pharo-dev] Just found, i can compile this:
Indeed, I can compile: Cfoo: arg ^ arg := 3 And 'C new foo: 1' returns 3... On 18 mars 2014, at 15:16, Igor Stasenko siguc...@gmail.com wrote: extent: newExtent vertical ifTrue: [ newExtent := self defaultWidth @ newExtent y ] ifFalse: [ newExtent := newExtent x @ self defaultWidth ]. super extent: newExtent Can you verify it? Arguments should be not assignable. -- Best regards, Igor Stasenko.
Re: [Pharo-dev] Just found, i can compile this:
similiar to issue 12419 https://pharo.fogbugz.com/default.asp?12419 block arguments should be read only 2014-03-18 15:21 GMT+01:00 Camille Teruel camille.ter...@gmail.com: Indeed, I can compile: Cfoo: arg ^ arg := 3 And 'C new foo: 1' returns 3... On 18 mars 2014, at 15:16, Igor Stasenko siguc...@gmail.com wrote: extent: newExtent vertical ifTrue: [ newExtent := self defaultWidth @ newExtent y ] ifFalse: [ newExtent := newExtent x @ self defaultWidth ]. super extent: newExtent Can you verify it? Arguments should be not assignable. -- Best regards, Igor Stasenko.
Re: [Pharo-dev] Just found, i can compile this:
Hello, For blockClosures it is normal, block closure arguments have always been assignable since smalltalk-80. We could add a warning to discourage it, but we cannot forbid it, or we will not be able to load lots of frameworks and libraries that use it. So 12419https://pharo.fogbugz.com/default.asp?12419 is not a bug to me, it's a feature. For methods it is a bug, thanks for noticing. I will check. 2014-03-18 15:45 GMT+01:00 Nicolai Hess nicolaih...@web.de: similiar to issue 12419 https://pharo.fogbugz.com/default.asp?12419 block arguments should be read only 2014-03-18 15:21 GMT+01:00 Camille Teruel camille.ter...@gmail.com: Indeed, I can compile: Cfoo: arg ^ arg := 3 And 'C new foo: 1' returns 3... On 18 mars 2014, at 15:16, Igor Stasenko siguc...@gmail.com wrote: extent: newExtent vertical ifTrue: [ newExtent := self defaultWidth @ newExtent y ] ifFalse: [ newExtent := newExtent x @ self defaultWidth ]. super extent: newExtent Can you verify it? Arguments should be not assignable. -- Best regards, Igor Stasenko.
Re: [Pharo-dev] Just found, i can compile this:
Why arguments should be read only? They are just temporary variables with an initial value. 2014-03-18 15:45 GMT+01:00 Nicolai Hess nicolaih...@web.de: similiar to issue 12419 block arguments should be read only 2014-03-18 15:21 GMT+01:00 Camille Teruel camille.ter...@gmail.com: Indeed, I can compile: Cfoo: arg ^ arg := 3 And 'C new foo: 1' returns 3... On 18 mars 2014, at 15:16, Igor Stasenko siguc...@gmail.com wrote: extent: newExtent vertical ifTrue: [ newExtent := self defaultWidth @ newExtent y ] ifFalse: [ newExtent := newExtent x @ self defaultWidth ]. super extent: newExtent Can you verify it? Arguments should be not assignable. -- Best regards, Igor Stasenko. smime.p7s Description: S/MIME cryptographic signature
Re: [Pharo-dev] Just found, i can compile this:
On 18.03.2014, at 18:17, Camille Teruel camille.ter...@gmail.com wrote: On 18 mars 2014, at 17:02, Clément Bera bera.clem...@gmail.com wrote: Hello, For blockClosures it is normal, block closure arguments have always been assignable since smalltalk-80. I never noticed, that's a weird 'feature'. We could add a warning to discourage it, but we cannot forbid it, or we will not be able to load lots of frameworks and libraries that use it. So 12419 is not a bug to me, it's a feature. You mean that there exist code out there that rely on being able to store in an argument? Always assume the worst case scenario :p For methods it is a bug, thanks for noticing. I will check. 2014-03-18 15:45 GMT+01:00 Nicolai Hess nicolaih...@web.de: similiar to issue 12419 block arguments should be read only 2014-03-18 15:21 GMT+01:00 Camille Teruel camille.ter...@gmail.com: Indeed, I can compile: Cfoo: arg ^ arg := 3 And 'C new foo: 1' returns 3... On 18 mars 2014, at 15:16, Igor Stasenko siguc...@gmail.com wrote: extent: newExtent vertical ifTrue: [ newExtent := self defaultWidth @ newExtent y ] ifFalse: [ newExtent := newExtent x @ self defaultWidth ]. super extent: newExtent Can you verify it? Arguments should be not assignable. -- Best regards, Igor Stasenko.
[Pharo-dev] RPackageOrganizer unregisterPackageNamed:
RPackageOrganizer has protocol 'public registration' with methods: #registerPackageNamed: and #unregisterPackageNamed: So I presume I am free to evaluate the following as separate steps)... 1. RPackageOrganizer default registerPackageNamed: 'MyTest'. --package is created okay 2. Object subclass: #MyTestClass instanceVariableNames: '' classVariableNames: '' category: 'MyTest'. --class is created okay 3. RPackageOrganizer default unregisterPackageNamed: 'MyTest'. --package disappears okay 4. RPackageOrganizer default registerPackageNamed: 'MyTest'. --package created okay 5. Object subclass: #MyTestClass instanceVariableNames: '' classVariableNames: '' category: 'MyTest'. --class does not appear However if I go... 6a. Smalltalk removeKey: #MyTestClass . 6b. Object subclass: #MyTestClass instanceVariableNames: '' classVariableNames: '' category: 'MyTest'. --then the class does appear Should I need to be cleaning up manually per step 6a? cheers -ben
Re: [Pharo-dev] Just found, i can compile this:
2014-03-18 18:31 GMT+01:00 Max Leske maxle...@gmail.com: On 18.03.2014, at 18:17, Camille Teruel camille.ter...@gmail.com wrote: On 18 mars 2014, at 17:02, Clément Bera bera.clem...@gmail.com wrote: Hello, For blockClosures it is normal, block closure arguments have always been assignable since smalltalk-80. I never noticed, that's a weird 'feature'. We could add a warning to discourage it, but we cannot forbid it, or we will not be able to load lots of frameworks and libraries that use it. So 12419 https://pharo.fogbugz.com/default.asp?12419 is not a bug to me, it's a feature. You mean that there exist code out there that rely on being able to store in an argument? Yes there are code like that, we encountered them in Opal's regression tests (I don't remember exactly but they are in Pharo, Moose or/and seaside). As Christophe said, arguments are temporary variables with an initial value for block closures (and right now for methods too, but it's a officially bug). Perhaps it is not a bug to allow that for methods. It's another feature. The expected behavior is the same as block closures: MyClassfoo | t | (self example: t) logCr. ^ t MyClassexample: arg arg := 1. ^ arg When evaluating MyClass new foo, 1 is logged on the transcript but the return value is nil, because an argument is a temporary variable with an initial value. On the bug tracker we noted to add a setting for these cases. That's the solution anyway... Always assume the worst case scenario :p For methods it is a bug, thanks for noticing. I will check. 2014-03-18 15:45 GMT+01:00 Nicolai Hess nicolaih...@web.de: similiar to issue 12419 https://pharo.fogbugz.com/default.asp?12419 block arguments should be read only 2014-03-18 15:21 GMT+01:00 Camille Teruel camille.ter...@gmail.com: Indeed, I can compile: Cfoo: arg ^ arg := 3 And 'C new foo: 1' returns 3... On 18 mars 2014, at 15:16, Igor Stasenko siguc...@gmail.com wrote: extent: newExtent vertical ifTrue: [ newExtent := self defaultWidth @ newExtent y ] ifFalse: [ newExtent := newExtent x @ self defaultWidth ]. super extent: newExtent Can you verify it? Arguments should be not assignable. -- Best regards, Igor Stasenko.
Re: [Pharo-dev] RPackageOrganizer unregisterPackageNamed:
package management and classes are orthogonal: you can have a class in the system outside the package structure. so yes.. removing a class from system will certainly remove them from package structure… but not the opposite: unregistering a package is just that: unregistering a package (the classes will remain). rpackage api needs to be revisited (yet once again) un pharo4… but for now, is like that :) Esteban On 18 Mar 2014, at 18:34, Ben Coman b...@openinworld.com wrote: RPackageOrganizer has protocol 'public registration' with methods: #registerPackageNamed: and #unregisterPackageNamed: So I presume I am free to evaluate the following as separate steps)... 1. RPackageOrganizer default registerPackageNamed: 'MyTest'. --package is created okay 2. Object subclass: #MyTestClass instanceVariableNames: '' classVariableNames: '' category: 'MyTest'. --class is created okay 3. RPackageOrganizer default unregisterPackageNamed: 'MyTest'. --package disappears okay 4. RPackageOrganizer default registerPackageNamed: 'MyTest'. --package created okay 5. Object subclass: #MyTestClass instanceVariableNames: '' classVariableNames: '' category: 'MyTest'. --class does not appear However if I go... 6a. Smalltalk removeKey: #MyTestClass . 6b. Object subclass: #MyTestClass instanceVariableNames: '' classVariableNames: '' category: 'MyTest'. --then the class does appear Should I need to be cleaning up manually per step 6a? cheers -ben
Re: [Pharo-dev] Just found, i can compile this:
On Tue, Mar 18, 2014 at 10:10 AM, Christophe Demarey christophe.dema...@inria.fr wrote: Why arguments should be read only? They are just temporary variables with an initial value. Read the blue book. It was a decision of the language designers to forbid assignment to arguments to allow debugging. The assignment to block arguments is a side-effect of the old BlockContext implementation of blocks where block arguments were mapped onto temporary variables of the home context. It is an anachronism and should be forbidden also. 2014-03-18 15:45 GMT+01:00 Nicolai Hess nicolaih...@web.de: similiar to issue 12419 https://pharo.fogbugz.com/default.asp?12419 block arguments should be read only 2014-03-18 15:21 GMT+01:00 Camille Teruel camille.ter...@gmail.com: Indeed, I can compile: Cfoo: arg ^ arg := 3 And 'C new foo: 1' returns 3... On 18 mars 2014, at 15:16, Igor Stasenko siguc...@gmail.com wrote: extent: newExtent vertical ifTrue: [ newExtent := self defaultWidth @ newExtent y ] ifFalse: [ newExtent := newExtent x @ self defaultWidth ]. super extent: newExtent Can you verify it? Arguments should be not assignable. -- Best regards, Igor Stasenko. -- best, Eliot
Re: [Pharo-dev] Just found, i can compile this:
Hi Clément, On Tue, Mar 18, 2014 at 9:02 AM, Clément Bera bera.clem...@gmail.comwrote: Hello, For blockClosures it is normal, block closure arguments have always been assignable since smalltalk-80. We could add a warning to discourage it, but we cannot forbid it, or we will not be able to load lots of frameworks and libraries that use it. So 12419https://pharo.fogbugz.com/default.asp?12419 is not a bug to me, it's a feature. For methods it is a bug, thanks for noticing. I will check. Well, in VW and Squeak it is disallowed, but there is a flag one can set to allow it. I think it best to disallow. One can always rewrite the code, and indeed create an automatic rewriter, The pattern is quite simple, and was applied to the Smalltalk-80 V2 code base when VisualWorks' predecessor ObjectsWorks 2.3 moved to ObjectWorks 2.4 which had proper closures: someMethod [:blockTemp| ... blockTemp := expr ... = someMethod | blockTemp | [:blockTempx| blockTemp := blockTempx. ... blockTemp := expr ... One would occasionally see this pattern also: someMethod | blockTemp | [:blockTemp| ... ] blockTemp := expr ... = someMethod | blockTemp | [:blockTempx| blockTemp := blockTempx. ... ] blockTemp := expr ... So disallowing it and providing a rewriting tool is an option. But I think the flag is best, with its default setting being to ban assignments to block arguments. HTH 2014-03-18 15:45 GMT+01:00 Nicolai Hess nicolaih...@web.de: similiar to issue 12419 https://pharo.fogbugz.com/default.asp?12419 block arguments should be read only 2014-03-18 15:21 GMT+01:00 Camille Teruel camille.ter...@gmail.com: Indeed, I can compile: Cfoo: arg ^ arg := 3 And 'C new foo: 1' returns 3... On 18 mars 2014, at 15:16, Igor Stasenko siguc...@gmail.com wrote: extent: newExtent vertical ifTrue: [ newExtent := self defaultWidth @ newExtent y ] ifFalse: [ newExtent := newExtent x @ self defaultWidth ]. super extent: newExtent Can you verify it? Arguments should be not assignable. -- Best regards, Igor Stasenko. -- best, Eliot
Re: [Pharo-dev] pharo sound should be working
Yes! That works. 2014-03-18 9:50 GMT+01:00 Esteban Lorenzano esteba...@gmail.com: Nicolai, can this be your problem? btw... I can give a try to pulse module, but now now, and not for pharo3... time time time (and you know... it would be an enhancement, not a bug fix... so is for pharo4 :) ) Esteban On 18 Mar 2014, at 09:43, Pharo4Stef pharo4s...@free.fr wrote: Begin forwarded message: *From: *xavier MESSNER xmess...@gmail.com *Subject: **Re: [Pharo-dev] pharo sound should be working* *Date: *17 Mar 2014 22:12:30 GMT+1 *To: *Stéphane Ducasse stephane.duca...@inria.fr Salut Stéphane, Les modifications apportées corrigent le problème. Le son fonctionne correctement mais uniquement si le serveur sonore Pulseaudio n'est pas démarré, ce qui n'est pas le cas pour les distributions modernes ou orientées desktop. Pour avoir du son j'ai dû désactiver pulseaudio. Voici comment j'ai procédé. Dans ~/.pulse/client.conf autospawn = no Cela permet de ne pas relancer le service en automatique Ensuite killall pulseaudio Maintenant je suis dans une configuration idéale et j'ai pu rejouer la mélodie de pacman :) Seulement, si le serveur de son pulseaudio est lancé j'ai cela qui apparaît dans la console sound_Start(default) soundStart: snd_add_pcm_handler: Fonction non implantée sound_Start(default) soundStart: snd_add_pcm_handler: Fonction non implantée Je suis bien parti de la dernière version de la vm disponible comme demané. A mon avis lorsqu'on utilise pulseaudio, il y a conflit avec la vm qui elle veut utiliser alsa. Xavier. 2014-03-17 20:03 GMT+01:00 Stéphane Ducasse stephane.duca...@inria.fr: xavier peux-tu reessayer? Begin forwarded message: *From: *Esteban Lorenzano esteba...@gmail.com *Subject: **Re: [Pharo-dev] pharo sound should be working* *Date: *17 Mar 2014 15:45:06 GMT+1 *To: *Pharo Development List pharo-dev@lists.pharo.org *Reply-To: *Pharo Development List pharo-dev@lists.pharo.org can you check with the latest vm now? btw... you need to install: sudo apt-get install libasound2-plugins:i386 in order to prevent warnings. On 15 Mar 2014, at 00:03, Nicolai Hess nicolaih...@web.de wrote: 2014-03-14 21:43 GMT+01:00 Esteban Lorenzano esteba...@gmail.com: Hi, so I committed some changes to allow soundplugin to work on the pharovm. can you please download and test in your platforms? Works on windows (remember, in linux you need libasound2 dependency installed) it does not work on linux Ubuntu 12.04.2 LTS (I have installed libasound2). Why don't we include the pulse config again and build the vm-sound-pulse module as well? As I described it in the issue 12493, vm-sound-oss is buildable too. But current linux distribution don't provide the older OSS sound system. (it worked for me with ubuntu 10.04 but not with 12.04) cheers, Esteban
[Pharo-dev] [ANN] ArchLinux pharo-vm / pharo-launcher packages
Hi ArchLinux users, you can now install pharo vm on Arch with: $ yaourt pharo-vm-latest then $ pharo /path/to/your/image There's also a pharo-launcher package that depends on pharo-vm: $ yaourt pharo-launcher then $ pharo-launcher or use your favorite desktop main menu and click on the Pharo icon AUR entries: https://aur.archlinux.org/packages/pharo-vm-latest/ https://aur.archlinux.org/packages/pharo-launcher/ PKGBUILDs are versionned on https://github.com/lolgzs/pharo-aur Thanks for testing ! Regards, Laurent
Re: [Pharo-dev] Just found, i can compile this:
On 18 Mar 2014, at 17:02, Clément Bera bera.clem...@gmail.com wrote: Hello, For blockClosures it is normal, block closure arguments have always been assignable since smalltalk-80. No this is wrong. We could add a warning to discourage it, but we cannot forbid it, or we will not be able to load lots of frameworks and libraries that use it. No they should not So 12419 is not a bug to me, it's a feature. No this is a bug. For methods it is a bug, thanks for noticing. I will check. 2014-03-18 15:45 GMT+01:00 Nicolai Hess nicolaih...@web.de: similiar to issue 12419 block arguments should be read only 2014-03-18 15:21 GMT+01:00 Camille Teruel camille.ter...@gmail.com: Indeed, I can compile: Cfoo: arg ^ arg := 3 And 'C new foo: 1' returns 3... On 18 mars 2014, at 15:16, Igor Stasenko siguc...@gmail.com wrote: extent: newExtent vertical ifTrue: [ newExtent := self defaultWidth @ newExtent y ] ifFalse: [ newExtent := newExtent x @ self defaultWidth ]. super extent: newExtent Can you verify it? Arguments should be not assignable. -- Best regards, Igor Stasenko.
Re: [Pharo-dev] WhatsUp from: 2014-03-17 until: 2014-03-31
On 18.03.2014, at 15:13, Goubier Thierry thierry.goub...@cea.fr wrote: Le 17/03/2014 22:49, Max Leske a écrit : - $NEXT_STEPS_TOWARDS_WORLD_DOMINATION - annoy Esteban some more with libgit2 - get other people to work on LibGit This is the project we should look at? http://smalltalkhub.com/#!/~StefanMarr/LibGit/commits Yes, that’s the one. It’s still pretty unstable so I don’t recommend that you look at it yet. That should change in the next couple of days though (as might the location of the repository actually…). I’ll keep you posted and will let you know once it makes sense for others to work on it. Max - move the repository to the FileSystem-Git-Dev team - get fetch / pull working - try to get the LibGit build working with Moose Thierry -- Thierry Goubier CEA list Laboratoire des Fondations des Systèmes Temps Réel Embarqués 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95
[Pharo-dev] Removing tools
Hi, this is an initial attempt to produce an image without development tools. Currently it leaves Workspace and Transcript in the image, has no obsolete classes and six Undeclared. The image size is still quite big, 16.1 MB. Tested on #30798. Do not forget to share your improvements ;-) Cheers, -- Pavel shrink.st Description: Binary data
[Pharo-dev] Couchbase client
Is there a Couchbase client for Pharo? If it there is one it isn't listed in the clients list (http://www.couchbase.com/communities/all-client-libraries). Regards! Esteban A. Maringolo
Re: [Pharo-dev] Couchbase client
I don't know the exact difference between the clients of Couchbase and CouchDB. I know Couchbase forked from CouchDB, and the REST API is the same. Hopefully the CouchDB client will work. Thank you! Esteban A. Maringolo 2014-03-18 20:01 GMT-03:00 Chris Cunningham cunningham...@gmail.com: I've used this one in Pharo (at least, on Pharo 2.0): http://www.squeaksource.com/SCouchDB.html -cbc On Tue, Mar 18, 2014 at 3:48 PM, Esteban A. Maringolo emaring...@gmail.com wrote: Is there a Couchbase client for Pharo? If it there is one it isn't listed in the clients list (http://www.couchbase.com/communities/all-client-libraries). Regards! Esteban A. Maringolo
Re: [Pharo-dev] WhatsUp from: 2014-03-17 until: 2014-03-31
Cool! Doru On Mon, Mar 17, 2014 at 9:14 AM, Stephan Eggermont step...@stack.nl wrote: Added Pier3 to MetaRepoForPharo30 Stephan -- www.tudorgirba.com Every thing has its own flow
Re: [Pharo-dev] WhatsUp from: 2014-03-17 until: 2014-03-31
### Here's what I've been up to since the last WhatsUp: - Documented how the GTInspector integrates seamlessly how to handle the DB http://www.humane-assessment.com/blog/dynamic-exploration-of-a-postgres-db-with-the-gtinspector/ - A little blog post about measuring and visualizing nil checks (with the new CodeCity) http://www.humane-assessment.com/blog/analyzing-the-density-of-nil-checks/ - Worked on supporting class examples in GTInspector - Worked on an initial support for contextual presentations in GTInspector - Got accepted for a 60 minutes slot at NDC Oslo to give a presentation entitled: Pharo: Playing with live objects http://ndcoslo.oktaset.com/t-13914 ### What's next, until 2014-03-31 (*): - start to prepare a presentation for speakerconf.com about GToolkit - release GToolkit for Pharo 3 (MetaRepoForPharo30) -- www.tudorgirba.com Every thing has its own flow
Re: [Pharo-dev] WhatsUp from: 2014-03-17 until: 2014-03-31
+1 Doru On Mon, Mar 17, 2014 at 8:01 PM, Pharo4Stef pharo4s...@free.fr wrote: seas...@rmod.lille.inria.fr wrote: Hi! We're sending this automatic email twice a month, to give the community an opportunity to easily know what's happening and to coordinate efforts. Just answer informally, and feel free to spawn discussions thereafter! ### Here's what I've been up to since the last WhatsUp: * Had a dozen or so bug fixes integrated. Surprised myself by how far I could dig into the system and it still made sense. I've learnt a lot about corners of the system I'd normally never poke around in. Its been fun. And this is cool :) ### What's next, until 2014-03-31 (*): Squash more bugs. -- www.tudorgirba.com Every thing has its own flow
