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

Re: [Pharo-project] receiving tcp messages

by Sven Van Caekenberghe

Doru, On 24 Feb 2012, at 10:14, Tudor Girba wrote: > Hi, > > I would need to listen to a TCP/IP port and receive plain text. What > is the way to do that in Pharo these days? > > Cheers, > Doru > > -- > www.tudorgirba.com > > "Every thing has its own flow" Have a look at the ZnServer hierarchy, specifically ZnSingleThreadedServer which does not spawn threads for each incoming request (not used as such in Zn, but easier to understand) and ZnMultiThreadedServer which does spawn threads for each incoming request (the current default in Zn). Start with #listenLoop. The code is slightly more complicated that example code because of all the error handling, but I am sure you will be able to read it. HTH, Sven -- Sven Van Caekenberghe http://stfx.eu Smalltalk is the Red Pill

Feb. 24, 2012

Re: [Pharo-project] Increasing bots traffic

by Pavel Krivanek

On Fri, Feb 24, 2012 at 7:15 AM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > On Feb 23, 2012, at 10:46 PM, Nicolas Cellier wrote: > >> Just curious, what is the goal of Jenkins build reports >> - focus developers attention on failing tests > > The reports will stop as soon as the build is green. > > But in general, the *only* person who has *ever* > added a bug report because a test started to fail was me. > > Nobody looks at the failing tests! I understand your indignation but last week I tried to look at failing tests of 1.4 and make it green (however without full success because some are VM related) :-) Cheers, -- Pavel > > Nobody realises that when a test starts to fail. "It might have been > that change last week". Great. I want to know *immediatly* when > as change breaks a test. > > Â Â Â Â Marcus > > > -- > Marcus Denker -- http://marcusdenker.de > >

Feb. 24, 2012

[Pharo-project] [update 1.4] #14351

by Marcus Denker

14351 ----- Issue 5369: Add a menu item for running startup script http://code.google.com/p/pharo/issues/detail?id=5369 Issue 5314: Broken string morph shadow http://code.google.com/p/pharo/issues/detail?id=5314 Issue 5368: Add methods in AbstractTool http://code.google.com/p/pharo/issues/detail?id=5368 Issue 5367: Defensive Text could assert that runs are tailored with a good size http://code.google.com/p/pharo/issues/detail?id=5367 -- Marcus Denker -- http://marcusdenker.de

Feb. 24, 2012

Re: [Pharo-project] [Bug Tracker] Issues tagged 1.3

by Tudor Girba

Bill, Please look over the list to find the answer to your question. Cheers, Doru On Fri, Feb 24, 2012 at 10:24 AM, Schwab,Wilhelm K <bschwab(a)anest.ufl.edu> wrote: > Is the missing debugger on your list? Â I have found 1.3 (speaking as a friend here) to be unusable over this. Â I get some work done with it, and then debuggers stop opening, rendering the image useless (AFAIK). > > Bill > > ________________________________________ > From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] on behalf of Marcus Denker [marcus.denker(a)inria.fr] > Sent: Friday, February 24, 2012 2:57 AM > To: An open mailing list to discuss any topics related to an open-source Smalltalk > Subject: [Pharo-project] [Bug Tracker] Issues tagged 1.3 > > Hi, > > Just as another suggestion of something else to do to uselessly talk about what one would > do if one could do... here is something that needs to be done: > > Â Â Â Â http://code.google.com/p/pharo/issues/list?can=2&q=Milestone%3D1.3 > > Someone need to looks at each issue and as questions. > > Â Â Â Â - can this problem be repeated in the current last version of 1.3? > Â Â Â Â - is this already fixed in 1.4? if yes > Â Â Â Â Â Â Â Â -- is it so grave that the fix needs to be backported? > Â Â Â Â - was it already a bug for the last 10 years and it did not hurt? > Â Â Â Â Â Â Â Â -- Hint, hint: likely not important for fixing in 1.3 after it has been released. > Â Â Â Â Â Â Â Â Â Â (yet, it could be. And if the fix is easy and clearly not breaking anything) > Â Â Â Â - is there already a bug report about this issue on the tracker? > Â Â Â Â Â Â Â Â (you have no idea how many reports are duplicated entries...) > Â Â Â Â - What could be the reason for the problem? What could be a possible fix? > > > -- > Marcus Denker -- http://marcusdenker.de > > > -- www.tudorgirba.com "Every thing has its own flow"

Feb. 24, 2012

Re: [Pharo-project] [Bug Tracker] Issues tagged 1.3

by Marcus Denker

On Feb 24, 2012, at 10:25 AM, Schwab,Wilhelm K wrote: > Is the missing debugger on your list? I have found 1.3 (speaking as a friend here) to be unusable over this. I get some work done with it, and then debuggers stop opening, rendering the image useless (AFAIK). The list is what people reported. This is turn means: if people do not report a problem, it is not in the list of issues. Marcus -- Marcus Denker -- http://marcusdenker.de

Feb. 24, 2012

Re: [Pharo-project] [Bug Tracker] Issues tagged 1.3

by Schwab,Wilhelm K

Is the missing debugger on your list? I have found 1.3 (speaking as a friend here) to be unusable over this. I get some work done with it, and then debuggers stop opening, rendering the image useless (AFAIK). Bill ________________________________________ From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] on behalf of Marcus Denker [marcus.denker(a)inria.fr] Sent: Friday, February 24, 2012 2:57 AM To: An open mailing list to discuss any topics related to an open-source Smalltalk Subject: [Pharo-project] [Bug Tracker] Issues tagged 1.3 Hi, Just as another suggestion of something else to do to uselessly talk about what one would do if one could do... here is something that needs to be done: http://code.google.com/p/pharo/issues/list?can=2&q=Milestone%3D1.3 Someone need to looks at each issue and as questions. - can this problem be repeated in the current last version of 1.3? - is this already fixed in 1.4? if yes -- is it so grave that the fix needs to be backported? - was it already a bug for the last 10 years and it did not hurt? -- Hint, hint: likely not important for fixing in 1.3 after it has been released. (yet, it could be. And if the fix is easy and clearly not breaking anything) - is there already a bug report about this issue on the tracker? (you have no idea how many reports are duplicated entries...) - What could be the reason for the problem? What could be a possible fix? -- Marcus Denker -- http://marcusdenker.de

Feb. 24, 2012

[Pharo-project] receiving tcp messages

by Tudor Girba

Hi, I would need to listen to a TCP/IP port and receive plain text. What is the way to do that in Pharo these days? Cheers, Doru -- www.tudorgirba.com "Every thing has its own flow"

Feb. 24, 2012

Re: [Pharo-project] Increasing bots traffic

by Marcus Denker

On Feb 24, 2012, at 7:15 AM, Marcus Denker wrote: > > On Feb 23, 2012, at 10:46 PM, Nicolas Cellier wrote: > >> Just curious, what is the goal of Jenkins build reports >> - focus developers attention on failing tests > > The reports will stop as soon as the build is green. > > But in general, the *only* person who has *ever* > added a bug report because a test started to fail was me. > > Nobody looks at the failing tests! > For 1.4 I changed the config to -> not send to the list on broken builds -> send to the list when *more* tests ar failing then before. For 1.3 full I for now let it like it is, as the failing tests in Full really need to be fixed (and 1.3 build is only triggered on update, which happens very seldomly). Marcus -- Marcus Denker -- http://marcusdenker.de

Feb. 24, 2012

[Pharo-project] [Bug Tracker] Issues tagged 1.3

by Marcus Denker

Hi, Just as another suggestion of something else to do to uselessly talk about what one would do if one could do... here is something that needs to be done: http://code.google.com/p/pharo/issues/list?can=2&q=Milestone%3D1.3 Someone need to looks at each issue and as questions. - can this problem be repeated in the current last version of 1.3? - is this already fixed in 1.4? if yes -- is it so grave that the fix needs to be backported? - was it already a bug for the last 10 years and it did not hurt? -- Hint, hint: likely not important for fixing in 1.3 after it has been released. (yet, it could be. And if the fix is easy and clearly not breaking anything) - is there already a bug report about this issue on the tracker? (you have no idea how many reports are duplicated entries...) - What could be the reason for the problem? What could be a possible fix? -- Marcus Denker -- http://marcusdenker.de

Feb. 24, 2012

[Pharo-project] [Bug Tracker] Issues that need to be reviewed

by Marcus Denker

http://code.google.com/p/pharo/issues/list?can=2&q=status%3AFixReviewNeeded -- Marcus Denker -- http://marcusdenker.de

Feb. 24, 2012