- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Issue 3626 in pharo: Clipboard broken on Unix

by pharo＠googlecode.com

Comment #1 on issue 3626 by stephane...(a)gmail.com: Clipboard broken on Unix http://code.google.com/p/pharo/issues/detail?id=3626 integrated in 13031 Attachments: clipboard.1.cs 823 bytes

Jan. 31, 2011

[Pharo-project] Issue 3626 in pharo: Clipboard broken on Unix

by pharo＠googlecode.com

Status: FixedProposed Owner: stephane...(a)gmail.com Labels: Milestone-1.2 Milestone-1.3 New issue 3626 by stephane...(a)gmail.com: Clipboard broken on Unix http://code.google.com/p/pharo/issues/detail?id=3626 Copy and paste is broken on linux for pharo 1.2 core and 1.3

Jan. 31, 2011

Re: [Pharo-project] [ANN] Alien on Pharo 1.2

by Marcus Denker

On Jan 31, 2011, at 12:59 PM, Luc Fabresse wrote: > > I just did it. > Now ConfigurationOfAlien.32 is in the "Metacello Repository" on squeaksource. > Thanks Fernando for reminding me this step. > Do we set up a build server for it? > #Luc > > > 2011/1/31 Luc Fabresse <luc.fabresse(a)gmail.com> > Hi Fernando and others, > > Just a point, I am not the Alien maintener but since I use it a lot, I patched it this week and commit ted all in the Alien repo. > > So you are right, it could be useful to copy the latest ConfigurationOfAlien in the Metacello repo. > > #Luc > > > 2011/1/31 Fernando Olivero <fernando.olivero(a)usi.ch> > > Hi Luc, which is the latest ConfigurationOfAlien we should use? > The one in MetacelloRepo or the one in Alien? > > In the case its the Alien repo, should we save in the MetacelloRepo > also? To avoid confusion. > > Fernando > > On Sun, Jan 30, 2011 at 1:50 PM, Luc Fabresse <luc.fabresse(a)gmail.com> wrote: > > > > 2011/1/30 Tudor Girba <tudor.girba(a)gmail.com> > >> > >> That sounds really nice. > >> > >> Just a question: Is Alien only working on Mac? > > > > It just requires the I32ABI VM plugin which is included in the Cog VM as > > Eliot told me. > > So it should work on linux+cog but I didn't test it recently. > > Not sure this plugin is included in the regular unix VM. > > #Luc > > > >> > >> Cheers, > >> Doru > >> > >> > >> On 30 Jan 2011, at 13:05, Luc Fabresse wrote: > >> > >> > Hi all, > >> > > >> > I just committed new versions of Alien on squeaksource to make it run on > >> > 1.2 > >> > I also modified the ConfigurationOfAlien to easily load it: > >> > > >> > (ConfigurationOfAlien project version: 'Pharo 1.1') load > >> > > >> > (ConfigurationOfAlien project version: 'Pharo 1.2') load > >> > > >> > (ConfigurationOfAlien project version: 'Pharo 1.1') load: {'All'. > >> > 'MacOSX'} > >> > > >> > (ConfigurationOfAlien project version: 'Pharo 1.2') load: {'All'. > >> > 'MacOSX'} > >> > > >> > #Luc > >> > >> -- > >> www.tudorgirba.com > >> > >> "Speaking louder won't make the point worthier." > >> > >> > > > > > > > -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

Jan. 31, 2011

Re: [Pharo-project] [ANN] Alien on Pharo 1.2

by Luc Fabresse

I just did it. Now ConfigurationOfAlien.32 is in the "Metacello Repository" on squeaksource. Thanks Fernando for reminding me this step. #Luc 2011/1/31 Luc Fabresse <luc.fabresse(a)gmail.com> > Hi Fernando and others, > > Just a point, I am not the Alien maintener but since I use it a lot, I > patched it this week and commit ted all in the Alien repo. > > So you are right, it could be useful to copy the latest > ConfigurationOfAlien in the Metacello repo. > > #Luc > > > 2011/1/31 Fernando Olivero <fernando.olivero(a)usi.ch> > > Hi Luc, which is the latest ConfigurationOfAlien we should use? >> The one in MetacelloRepo or the one in Alien? >> >> In the case its the Alien repo, should we save in the MetacelloRepo >> also? To avoid confusion. >> >> Fernando >> >> On Sun, Jan 30, 2011 at 1:50 PM, Luc Fabresse <luc.fabresse(a)gmail.com> >> wrote: >> > >> > 2011/1/30 Tudor Girba <tudor.girba(a)gmail.com> >> >> >> >> That sounds really nice. >> >> >> >> Just a question: Is Alien only working on Mac? >> > >> > It just requires the I32ABI VM plugin which is included in the Cog VM >> as >> > Eliot told me. >> > So it should work on linux+cog but I didn't test it recently. >> > Not sure this plugin is included in the regular unix VM. >> > #Luc >> > >> >> >> >> Cheers, >> >> Doru >> >> >> >> >> >> On 30 Jan 2011, at 13:05, Luc Fabresse wrote: >> >> >> >> > Hi all, >> >> > >> >> > I just committed new versions of Alien on squeaksource to make it run >> on >> >> > 1.2 >> >> > I also modified the ConfigurationOfAlien to easily load it: >> >> > >> >> > (ConfigurationOfAlien project version: 'Pharo 1.1') load >> >> > >> >> > (ConfigurationOfAlien project version: 'Pharo 1.2') load >> >> > >> >> > (ConfigurationOfAlien project version: 'Pharo 1.1') load: {'All'. >> >> > 'MacOSX'} >> >> > >> >> > (ConfigurationOfAlien project version: 'Pharo 1.2') load: {'All'. >> >> > 'MacOSX'} >> >> > >> >> > #Luc >> >> >> >> -- >> >> www.tudorgirba.com >> >> >> >> "Speaking louder won't make the point worthier." >> >> >> >> >> > >> > >> >> >

Jan. 31, 2011

[Pharo-project] Issue 3625 in pharo: MessageNames search field: MessageNotUnderstood: TextEditor>>caret

by pharo＠googlecode.com

Status: New Owner: ---- New issue 3625 by thereluc...(a)fastmail.fm: MessageNames search field: MessageNotUnderstood: TextEditor>>caret http://code.google.com/p/pharo/issues/detail?id=3625 // Hi. It's the first time i submit an issue. Please tell me, if it's ok like this. // Or if i missed finding the same problem in the issues list or mailing list.. Pharo image: Pharo1.2rc2 [Latest update: #12327] Steps to reproduce: 1. in a workspace do: MessageNames openMessageNames 2. try to type something in the search field 3. MessageNotUnderstood: TextEditor>>caret Attachments: debuglog.txt 24.8 KB

Jan. 31, 2011

[Pharo-project] FW: Smalltalk Developer in Belgium

by Geert Claes

Je zal voornamelijk bij onze klant werken als Smalltalk Developer aan de ontwikkeling en aanpassing van software voor televisiestations. Benefits: brutoloon, bedrijfswagen, hospitalisatieverzekering, dagvergoeding per bij de klant gepresteerde werkdag, gsmabonnement, budget voor beroepsmatige aankopen ... More info: https://www.roots.be/job/smalltalk-developer www.roots.be/job/smalltalk-developer -- View this message in context: http://forum.world.st/FW-Smalltalk-Developer-in-Belgium-tp3248505p3248505.h… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Jan. 31, 2011

Re: [Pharo-project] Issue 3609 in pharo: Integrate RPackage

by pharo＠googlecode.com

Comment #6 on issue 3609 by marcus.d...(a)gmail.com: Integrate RPackage http://code.google.com/p/pharo/issues/detail?id=3609 fixed the permissions

Jan. 31, 2011

Re: [Pharo-project] Issue 3609 in pharo: Integrate RPackage

by pharo＠googlecode.com

Comment #5 on issue 3609 by cy.delau...(a)gmail.com: Integrate RPackage http://code.google.com/p/pharo/issues/detail?id=3609 Finally I does not have the rigth to edit the file rpackage.st.

Jan. 31, 2011

Re: [Pharo-project] does anybody knows who is using StandardToolSet?

by Tudor Girba

I am not sure I understand. As far as I understand, there would be a pool of different instance variables. So, why would there be any subclassing? Cheers, Doru On 31 Jan 2011, at 08:21, StÃ©phane Ducasse wrote: >> >> The answer of 'Smalltalk tools' should be a tool registry instance. >> >> The tool registry is a system-wide object where packages can register >> their tools. >> I don't remember all of the details, but the idea, when i implemented >> it was following: >> >> - you registering your tool(s) by sending: >> >> Smalltalk tools addTool: myTool verb: #myTool > > would be good to have > addTool: myTool named: #myTool kind: #codebrowser > > so that we can avoid to have one subclass per kind. > > Stef > -- www.tudorgirba.com "Being happy is a matter of choice."

Jan. 31, 2011

Re: [Pharo-project] does anybody knows who is using StandardToolSet?

by Igor Stasenko

On 31 January 2011 08:21, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >> >> The answer of 'Smalltalk tools' should be a tool registry instance. >> >> The tool registry is a system-wide object where packages can register >> their tools. >> I don't remember all of the details, but the idea, when i implemented >> it was following: >> >> - you registering your tool(s) by sending: >> >> Smalltalk tools addTool: myTool verb: #myTool > > would be good to have > Â Â Â Â addTool: myTool named: #myTool kind: #codebrowser > > so that we can avoid to have one subclass per kind. > can you elaborate a bit? i mean why you need to have two different keys for one tool? When you registering browser at #browser, then in this way everyone refer to it using 'Smalltalk tools browser' , and of course they expecting that given tool supports certain browser protocol, which means its already of kind of 'codebrowser'.. For cases, when you have multiple browsers installed and need to show user a choice which one to use (like standard browser vs OB one) this can be solved differently: Smalltalk tools addEntry: #availableBrowsers value: WeakSet new. Smalltalk tools availableBrowsers add: MyBrowserClass. Smalltalk tools availableBrowsers add: MyOtherBrowserClass. so, then you can enumerate available browsers by using: Smalltalk tools availableBrowsers. > Stef > > -- Best regards, Igor Stasenko AKA sig.

Jan. 31, 2011