- Pharo-dev - lists.pharo.org

Re: [Pharo-project] [aida] Code stats - Aida vs. Seaside vs. Iliad

by Mariano Martinez Peck

Thanks Janko for such useful package. In less than 5 minutes I have stats for my project ;) On Mon, Nov 15, 2010 at 2:30 PM, Friedrich Dominicus < frido(a)q-software-solutions.de> wrote: > Just a think I forgot: > There is this no if movement: > > > http://www.antiifcampaign.com/ > > I think the Smalltalkers are among the strongest supporters, and I just > mention this excellent boot of Andre Valloud > > > http://www.lulu.com/product/paperback/a-mentoring-course-on-smalltalk/37888… > > Just see the examples there and I was very suprised. I first found it > extreme but maybe it's just "right". > > Regards > Friedrich > > > > -- > Q-Software Solutions GmbH; Sitz: Bruchsal; Registergericht: Mannheim > Registriernummer: HRB232138; Geschaeftsfuehrer: Friedrich Dominicus > _______________________________________________ > Aida mailing list > Aida(a)aidaweb.si > http://lists.aidaweb.si/mailman/listinfo/aida > -- Mariano http://marianopeck.wordpress.com

April 21, 2011

Re: [Pharo-project] Smalltalk, git, files, the universe and everything...okay not everything:)

by Sven Van Caekenberghe

On 21 Apr 2011, at 04:47, Steven Baker wrote: > Monticello may have a poor UI, but Git has the worst possible UI, encourages awful practices, and just doesn't do the job well. +10 Most people find git hard to use, indeed. Monticello is not harder to use, you just have to understand what it is (a distributed version control system). It has limitations like any other system.

April 21, 2011

Re: [Pharo-project] Networking problems on Pharo 1.2.1

by Sven Van Caekenberghe

On 21 Apr 2011, at 09:26, Luc Fabresse wrote: > Yes SocketStream is useful but still, the socket base layer should be usable without problems ... +1 Both should work, both should be understandable by mere mortals like us.

April 21, 2011

Re: [Pharo-project] Networking problems on Pharo 1.2.1

by StÃ©phane Ducasse

+1 I would love to know the answer. On Apr 21, 2011, at 9:26 AM, Luc Fabresse wrote: > Hi, > > Yes SocketStream is useful but still, the socket base layer should be usable without problems ... > I do not know why #waitForAcceptFor: do not make it. > > #Luc > > > 2011/4/21 GÃ¶ran Krampe <goran(a)krampe.se> > On 04/21/2011 07:17 AM, Oscar E A Callau wrote: > Hi again, > > I found a solution (but not what was the problem); change the server code to the following: > > Just a tip: Please use SocketStream, it will help you when doing the actual sending/receiving. In almost every situation SocketStream is your friend. > > regards, GÃ¶ran > >

April 21, 2011

Re: [Pharo-project] Smalltalk, git, files, the universe and everything...okay not everything:)

by StÃ©phane Ducasse

Just a meta question that each of us can try to answer when looking at himself in the mirror. What do we do to get a better system? If everybody would do something simple everyday we would be more than busy. So yes MC UI is funky, now who tried to develop a new widget? Don't tell me that morphic is bad, it is not that bad so you can take UITheme examples and get started and do something. Everyday I like to see the updates working and this is a good feeling for me. Stef

April 21, 2011

Re: [Pharo-project] [Pharo-users] [COTDC] 52 - PCXReadWriter

by StÃ©phane Ducasse

open a bug entry and put your fix :) Stef On Apr 21, 2011, at 1:05 AM, Guillermo Polito wrote: > I am an Image ReadWriter supposed to be in charge of PCX file encoding and decoding. > > Actually, as my instances does not implement understandsImageFormat, they use the default ^false implementation and I cannot be used. > I don't have uses in the image also :). > > But in case I am fixed, the code to open a morph with a pcx image is: > > PCXReadWriter formFromFileNamed: 'anImage.pcx'. > > > ;) > Guille > > On Wed, Apr 20, 2011 at 3:17 PM, laurent laffont <laurent.laffont(a)gmail.com> wrote: > Today: PCXReadWriter > > > Comment Of The Day Contest - One Day One Comment > Rules: > #1: Each day a not commented class is elected. Each day the best comment will be integrated with name of the author(s). > #2: If you cannot comment it, deprecate it. > Results: http://code.google.com/p/pharo/wiki/CommentOfTheDayContest > > Laurent >

April 21, 2011

[Pharo-project] [update 1.3] #13168

by Marcus Denker

13168 ----- Issue 3996: alt+k opens a StringHolder and not a workspace Issue 1853: NetNameResolver localHostAddress returns public or private address instead of loopback address. Issue 3188: do we need SecurityManager? -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

April 21, 2011

[Pharo-project] [update 1.2] #12349

by Marcus Denker

12349 ----- Issue 1853: NetNameResolver localHostAddress returns public or private address instead of loopback address. Issue 3996: alt+k opens a StringHolder and not a workspace Next for 1.2.2: -> fix build 1.2 -> integrate Lukas' OB -> release. -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

April 21, 2011

Re: [Pharo-project] Networking problems on Pharo 1.2.1

by Luc Fabresse

Hi, Yes SocketStream is useful but still, the socket base layer should be usable without problems ... I do not know why #waitForAcceptFor: do not make it. #Luc 2011/4/21 GÃ¶ran Krampe <goran(a)krampe.se> > On 04/21/2011 07:17 AM, Oscar E A Callau wrote: > >> Hi again, >> >> I found a solution (but not what was the problem); change the server code >> to the following: >> > > Just a tip: Please use SocketStream, it will help you when doing the actual > sending/receiving. In almost every situation SocketStream is your friend. > > regards, GÃ¶ran > >

April 21, 2011

Re: [Pharo-project] Networking problems on Pharo 1.2.1

by GÃ¶ran Krampe

On 04/21/2011 07:17 AM, Oscar E A Callau wrote: > Hi again, > > I found a solution (but not what was the problem); change the server code to the following: Just a tip: Please use SocketStream, it will help you when doing the actual sending/receiving. In almost every situation SocketStream is your friend. regards, GÃ¶ran

April 21, 2011