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

[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

Re: [Pharo-project] we will start 1.3 really soon

by StÃ©phane Ducasse

On Jan 15, 2011, at 9:57 AM, Adrian Lienhard wrote: > Cool :) > > BTW, I have a question related to 1.2 from a user's perspective: could we generate a summary to help people migrate from 1.1.1 to 1.2? In particular, the question is which changes in 1.2 are not backwards compatible and may break my code? I've been a bit out of the loop during the last months... so at least for me this is not obvious ;). There's http://code.google.com/p/pharo/wiki/ActionsInPharoOneDotTwo but it doesn't tell the important bits. going over the issues tagged 1.2 and generate a report will take me at least a couple of hours.... so I'm not sure that I have the time to do it. Now if someone starts I can help improving the results. We can also take all the comments in the scriptloader methods. Stef > > Cheers, > Adrian > > On Jan 15, 2011, at 09:27 , StÃ©phane Ducasse wrote: > >> Hi guys >> >> there are some minors fixes to be addressed (like the preferences use in dev) but we will go 1.3 probably this evening and >> we will start to harvest a large list of pending issues. If you have seen fixes in squeak that you think are good please add a bug entry. >> After that we will plan for the big changes in 1.3 for me >> I would like to see >> - collection enh (finishing hashed collection) >> - weak structure support >> - announcement using weak structure >> - file system use >> - new package implementation (cyrille worked and will continue to really make sure everything works) >> - real beta of OPAL >> The goal is to have a release for 1.3 by June/July. >> >> Stef >> > >

Jan. 15, 2011

Re: [Pharo-project] we will start 1.3 really soon

by Janko MivÅ¡ek

Stef, you again forgot namespaces ... ;) Janko On 15. 01. 2011 09:27, StÃ©phane Ducasse wrote: > Hi guys > > there are some minors fixes to be addressed (like the preferences use in dev) but we will go 1.3 probably this evening and > we will start to harvest a large list of pending issues. If you have seen fixes in squeak that you think are good please add a bug entry. > After that we will plan for the big changes in 1.3 for me > I would like to see > - collection enh (finishing hashed collection) > - weak structure support > - announcement using weak structure > - file system use > - new package implementation (cyrille worked and will continue to really make sure everything works) > - real beta of OPAL > The goal is to have a release for 1.3 by June/July. > > Stef > -- Janko MivÅ¡ek AIDA/Web Smalltalk Web Application Server http://www.aidaweb.si

Jan. 15, 2011

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

by StÃ©phane Ducasse

On Jan 15, 2011, at 9:52 AM, 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 >>> >>> 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" yes this would be nice to have tool doing it for us. > > it sounds feasible for you? what do you think? > > HernÃ¡n >

Jan. 15, 2011

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

by StÃ©phane Ducasse

Previous names is a good idea We should adopt it! Stef On Jan 15, 2011, at 9:52 AM, 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 >>> >>> 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] Issue 3236 in pharo: Cuis DateAndTime Enhancement

by pharo＠googlecode.com

Updates: Labels: Milestone-1.3 Comment #2 on issue 3236 by stephane...(a)gmail.com: Cuis DateAndTime Enhancement http://code.google.com/p/pharo/issues/detail?id=3236 (No comment was entered for this change.)

Jan. 15, 2011