- Pharo-dev - lists.pharo.org

Re: [Pharo-project] [update 1.2] #12305

by Esteban Lorenzano

Hi, I really don't like the orange theme to become the default pharo theme... is to "alien" for me, and I'm sure it will be also for newcomers. May I suggest to let the standard glamour theme as the default, and keep the orange just as an option? Cheers, Esteban El 15/01/2011, a las 4:05p.m., StÃ©phane Ducasse escribiÃ³: > why not :) > even if the orange is too orange :) > Stef > >> Why don't you call the GLMOrangeUITheme the PharoTheme or something in this direction? >> >> Cheers, >> Doru >> >> >> On 14 Jan 2011, at 15:46, StÃ©phane Ducasse wrote: >> >>> 12305 >>> ----- >>> >>> - GLMOrangeUITheme beCurrent. >>> - Issue 3417: BehaviorTest>>#testAllLocalCallsOn fails. >>> >>> Stef >>> >> >> -- >> www.tudorgirba.com >> >> "Reasonable is what we are accustomed with." >> >> > >

Jan. 15, 2011

Re: [Pharo-project] [Pharo-users] Where do I find KeyedSet?

by Levente Uzonyi

On Sat, 15 Jan 2011, HernÃ¡n Morales Durand wrote: > Hi Stef > > 2011/1/15 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: >> >> On Jan 14, 2011, at 6:24 PM, HernÃ¡n Morales Durand wrote: >> >>> Try PluggableSet Note that KeyedSet has nothing to do with PluggableSet. PluggableSet is a set where you can specify the hash and equality of two objects with blocks. This gives you great flexibility without creating a subclass of Set. KeyedSet is like a dictionary, but the keys of the objects are not stored in the data structure, because the objects know it themselves. This means that the data structure will have a smaller memory footprint. Levente >>> >>> http://www.mail-archive.com/pharo-project@lists.gforge.inria.fr/msg22890.ht… >>> >>> Is there a way for you guys to deprecate deleted classes or mantain a >>> record of deleted behaviors? (IIRC VW did this from 2.x versions) >> >> We try but we do not have the engineers of VW. >> Now find somebody that pay us just 3 engineers full time for two years and you will not >> recognized pharo and its process. > > I know we are very few, but what about this idea, instead of just > deleting a class we may adopt these simple rules: > > 1 - If deleting a class add the deleted class name somewhere (in a method?) > 2 - If renaming a class, make the class to know its previous names > like #previousNames > (Norberto Manzanos implemented this for his own package management and > I think is a great idea) > > doesn't require tools, just some consensus and maybe a modified > #deleteClass to enforce this "policy" > > it sounds feasible for you? what do you think? > > HernÃ¡n > >

Jan. 15, 2011

Re: [Pharo-project] [update 1.2] #12305

by StÃ©phane Ducasse

why not :) even if the orange is too orange :) Stef > Why don't you call the GLMOrangeUITheme the PharoTheme or something in this direction? > > Cheers, > Doru > > > On 14 Jan 2011, at 15:46, StÃ©phane Ducasse wrote: > >> 12305 >> ----- >> >> - GLMOrangeUITheme beCurrent. >> - Issue 3417: BehaviorTest>>#testAllLocalCallsOn fails. >> >> Stef >> > > -- > www.tudorgirba.com > > "Reasonable is what we are accustomed with." > >

Jan. 15, 2011

Re: [Pharo-project] [update 1.2] #12305

by Tudor Girba

Why don't you call the GLMOrangeUITheme the PharoTheme or something in this direction? Cheers, Doru On 14 Jan 2011, at 15:46, StÃ©phane Ducasse wrote: > 12305 > ----- > > - GLMOrangeUITheme beCurrent. > - Issue 3417: BehaviorTest>>#testAllLocalCallsOn fails. > > Stef > -- www.tudorgirba.com "Reasonable is what we are accustomed with."

Jan. 15, 2011

Re: [Pharo-project] Need help about Sockets

by Levente Uzonyi

On Sat, 15 Jan 2011, Adrien BARREAU wrote: > > Hi all, > > I'm trying to use the Sockets in Pharo but I don't understand some points. > I tried that piece of code: > > | s c rcv | > Socket initializeNetwork. > rcv := String new: 400. > s := Socket new. > s listenOn: 12345. The problem is here. You should use #listenOn:backlogSize: if you want to accept (multiple) connections. #listenOn: is a "special" method that uses the same socket for listening and receiveing data. See the method comments for details. Here's a small example how to use #listenOn:. Copy it to a workspace and print it: server := Socket new. semaphore := Semaphore new. [ [ server listenOn: 12345. server semaphore wait. "wait for the client to connect" server waitForData. data := server receiveData. semaphore signal ] ensure: [ server closeAndDestroy ] ] fork. client := Socket new. client connectTo: #[127 0 0 1] port: 12345. client sendData: 'Hello!'. client closeAndDestroy. data Levente > c := s waitForAcceptFor: 30. > c dataAvailable ifTrue: [ c receiveDataInto: rcv ] ifFalse: [ self halt ]. > > waitForAcceptFor: waits a connection, so I opened a telnet client on localhost:12345. It works, but the "accept" primitive always failed. > I tried to find some code where it's used: ConnectionQueue>>listenLoop. > I assume that method works (but it has no sender), and I don't understand what is different between it and my code. > > Perhaps I don't try to use the Sockets the good way? > > Adrien. >

Jan. 15, 2011

[Pharo-project] Need help about Sockets

by Adrien BARREAU

Hi all, I'm trying to use the Sockets in Pharo but I don't understand some points. I tried that piece of code: | s c rcv | Socket initializeNetwork. rcv := String new: 400. s := Socket new. s listenOn: 12345. c := s waitForAcceptFor: 30. c dataAvailable ifTrue: [ c receiveDataInto: rcv ] ifFalse: [ self halt ]. waitForAcceptFor: waits a connection, so I opened a telnet client on localhost:12345. It works, but the "accept" primitive always failed. I tried to find some code where it's used: ConnectionQueue>>listenLoop. I assume that method works (but it has no sender), and I don't understand what is different between it and my code. Perhaps I don't try to use the Sockets the good way? Adrien.

Jan. 15, 2011

Re: [Pharo-project] Issue 3540 in pharo: Latest versions in DevImages Workspace

by pharo＠googlecode.com

Updates: Status: Accepted Cc: guillermopolito Labels: Milestone-1.2-DevImage Comment #1 on issue 3540 by marianopeck: Latest versions in DevImages Workspace http://code.google.com/p/pharo/issues/detail?id=3540 thanks Janko. Indeed, that's true.

Jan. 15, 2011

[Pharo-project] Issue 3540 in pharo: Latest versions in DevImages Workspace

by pharo＠googlecode.com

Status: New Owner: ---- New issue 3540 by janko.mi...(a)gmail.com: Latest versions in DevImages Workspace http://code.google.com/p/pharo/issues/detail?id=3540 Hi, If you open DEVImageWorkspaces openExternalProjectWorkspace in latest 1.2 build, there are still old versions, this should be corrected at least to: ... ((Smalltalk at: #ConfigurationOfSeaside30) project version: '3.0.3') load. ... ((Smalltalk at: #ConfigurationOfAida) project version: '6.2') load.

Jan. 15, 2011

Re: [Pharo-project] Issue 3471 in pharo: [Failing Test] OBCmdAutoCategorizeWithAMCTest.testOBAutocategorizeCommandOverride

by pharo＠googlecode.com

Updates: Status: Fixed Comment #5 on issue 3471 by laurent....(a)gmail.com: [Failing Test] OBCmdAutoCategorizeWithAMCTest.testOBAutocategorizeCommandOverride http://code.google.com/p/pharo/issues/detail?id=3471 (No comment was entered for this change.)

Jan. 15, 2011

Re: [Pharo-project] Issue 3522 in pharo: wiki like help contents

by pharo＠googlecode.com

Updates: Labels: -Milestone-1.3 Milestone-1.2 Comment #10 on issue 3522 by stephane...(a)gmail.com: wiki like help contents http://code.google.com/p/pharo/issues/detail?id=3522 I want that in 1.2 :) so in the next integration

Jan. 15, 2011