- Pharo-dev - lists.pharo.org

Re: [Pharo-project] little pictures of you :)

by Mariano Martinez Peck

+1 to pictures in website -1 to facebook. I really have social netwroks and I won't subscribe. Maybe it is just me, buy maybe there are more But I really agree it is cool to have other's face. It was funny in ESUG or London Camp Smalltalk to recognize people you receive millions of mail but you didn't know evne his face hahhaha On Wed, Aug 11, 2010 at 1:55 PM, Hilaire Fernandes < hilaire.fernandes(a)gmail.com> wrote: > No, it forces you to get in this things. > > Hilaire > > Le 11/08/2010 13:27, Adrian Lienhard a Ã©crit : > > Wouldn't Facebook do exactly this? > > > > Adrian > > > > On Aug 11, 2010, at 12:47 , StÃ©phane Ducasse wrote: > > > >> Hi guys > >> > >> the pharo web site does not support that yet :) > >> but I would love to have some pictures of you because this is not that > fun to talk daily with people > >> when we do not even know their faces so we could start to build a pharo > fun community. > >> Let me know what you think. > >> > >> Stef > >> _______________________________________________ > >> Pharo-project mailing list > >> Pharo-project(a)lists.gforge.inria.fr > >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Aug. 11, 2010

Re: [Pharo-project] little pictures of you :)

by Norbert Hartl

I just left facebook and I'm not willing to get into this again. Norbert On 11.08.2010, at 13:27, Adrian Lienhard wrote: > Wouldn't Facebook do exactly this? > > Adrian > > On Aug 11, 2010, at 12:47 , StÃ©phane Ducasse wrote: > >> Hi guys >> >> the pharo web site does not support that yet :) >> but I would love to have some pictures of you because this is not that fun to talk daily with people >> when we do not even know their faces so we could start to build a pharo fun community. >> Let me know what you think. >> >> Stef >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Aug. 11, 2010

Re: [Pharo-project] little pictures of you :)

by Hilaire Fernandes

No, it forces you to get in this things. Hilaire Le 11/08/2010 13:27, Adrian Lienhard a Ã©crit : > Wouldn't Facebook do exactly this? > > Adrian > > On Aug 11, 2010, at 12:47 , StÃ©phane Ducasse wrote: > >> Hi guys >> >> the pharo web site does not support that yet :) >> but I would love to have some pictures of you because this is not that fun to talk daily with people >> when we do not even know their faces so we could start to build a pharo fun community. >> Let me know what you think. >> >> Stef >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Aug. 11, 2010

Re: [Pharo-project] little pictures of you :)

by Peter Hugosson-Miller

Indeed: http://www.facebook.com/group.php?gid=103975957018 Only 26 members at the moment, surely we can do better ;-) -- Cheers, Peter On Wed, Aug 11, 2010 at 1:27 PM, Adrian Lienhard <adi(a)netstyle.ch> wrote: > Wouldn't Facebook do exactly this? > > Adrian > > On Aug 11, 2010, at 12:47 , StÃ©phane Ducasse wrote: > > > Hi guys > > > > the pharo web site does not support that yet :) > > but I would love to have some pictures of you because this is not that > fun to talk daily with people > > when we do not even know their faces so we could start to build a pharo > fun community. > > Let me know what you think. > > > > Stef > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Aug. 11, 2010

Re: [Pharo-project] little pictures of you :)

by Adrian Lienhard

Wouldn't Facebook do exactly this? Adrian On Aug 11, 2010, at 12:47 , StÃ©phane Ducasse wrote: > Hi guys > > the pharo web site does not support that yet :) > but I would love to have some pictures of you because this is not that fun to talk daily with people > when we do not even know their faces so we could start to build a pharo fun community. > Let me know what you think. > > Stef > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Aug. 11, 2010

[Pharo-project] [update 1.2] #12088

by StÃ©phane Ducasse

12088 ----- - Issue 2683: new slice package should get inbox by default as repository. Thanks Carlo Teixeira. - Issue 2754: DateAndTime instance creation from a string or stream sets offset to 0. Thanks Sean De Nigris. - DateAndTime instance creation from strings and streams default to local offset if none is specified (e.g. via class >>readFrom: and class>>fromString:). - DateAndTime tests updated - testReadFromSecond renamed to testPrintStringSecond - added tests for the default offset condition described above - added test of class>>fromString: - Issue 2782: Monticello UI does not make newly added slice or package the selected package. Thanks Carlo Teixeira - Issue 2783: Bitmap>>compressGZip unused. - Issue 2784: More uppercase menues for file service menues. Gorgeous and dead simple but needed. Thanks Torsten Bergmann. Thanks guys! Stef

Aug. 11, 2010

[Pharo-project] looking for text about variableSubclass: and isPointers...

by StÃ©phane Ducasse

Hi guys some guys here need to get up to date about variableSubclass and friends. Do you remember some texts around? Stef

Aug. 11, 2010

[Pharo-project] little pictures of you :)

by StÃ©phane Ducasse

Hi guys the pharo web site does not support that yet :) but I would love to have some pictures of you because this is not that fun to talk daily with people when we do not even know their faces so we could start to build a pharo fun community. Let me know what you think. Stef

Aug. 11, 2010

Re: [Pharo-project] Fwd: Re: Squeaksource XML Parser - Enhanced support for CDATA Sections

by StÃ©phane Ducasse

> :funnily enough for me coalesce is far more obscure than preserve. >> > Might be the french in you :) Probably :) We can't mess up with our roots :) > >> Now my point was not for this specific message but I would like to get some guidelines to specify consistent API. >> And I'm always thorn apart when writing code if I should use s or not. >> > I think we all want to figure out how it is done best in general. Discussing about a single selector in one piece of code would hardly justify a longer thread :) > > To me this is really important. I read the Becks but can't even remember which of those. Because it's none of these things you read and you can remember afterwards. Well, at least in my cast this doesn't work and far too lazy to read it over and over. It is 4 pages so this is worth the effort. I will reread them and smalltalk with style. and probably Smalltalk by example. Stef

Aug. 11, 2010

Re: [Pharo-project] Fwd: Re: Squeaksource XML Parser - Enhanced support for CDATA Sections

by Norbert Hartl

On 11.08.2010, at 10:31, StÃ©phane Ducasse wrote: > :funnily enough for me coalesce is far more obscure than preserve. > Might be the french in you :) > Now my point was not for this specific message but I would like to get some guidelines to specify consistent API. > And I'm always thorn apart when writing code if I should use s or not. > I think we all want to figure out how it is done best in general. Discussing about a single selector in one piece of code would hardly justify a longer thread :) To me this is really important. I read the Becks but can't even remember which of those. Because it's none of these things you read and you can remember afterwards. Well, at least in my cast this doesn't work and far too lazy to read it over and over. Norbert > > On Aug 11, 2010, at 10:07 AM, Norbert Hartl wrote: > >> >> On 11.08.2010, at 00:56, jaayer wrote: >> >>> >>> >>> ---- On Tue, 10 Aug 2010 02:18:19 -0700 Norbert Hartl wrote ---- >>> >>>> >>>> But as I wrote in my description of the problem I would call it >>>> >>>> coalesceCDATASections: aBoolean >>>> >>>> or >>>> >>>> enableCoalescing >>>> disableCoalescing >>> >>> The downside of enable/disable pairs is the need for three message (two to modify, one to test and lazily initialize) rather than two. >>> >>>> The functionality that is described here is better known as coalescing. And it describes better what is going. If a parser is coalescing two things will happen. CDATA sections will be read in as text nodes and then subsequent text nodes are coalesing into a single text node. >>>> >>>> my 2 cents, >>>> >>>> Norbert >>> >>> I think "preserve" is better, if only because "coalesceCData" just implies a joining together of CDATA sections and says nothing about their status in the DOM tree as XMLString or XMLCData nodes. Although I am not wed to it. >>> >> I think it is hard to find a word that describes completely what ist going on. And I think that common sense/common usage is also kind of an argument. I didn't start to think of myself what would be the best describing word (quite hard as non-native speaker). If you search the net then you might see (as I did) that it is quite common that this effect is described as coalescing. That was my only reason to speak up because I think its recognition is better this way. >> If you know about coalescing than the state in DOM tree is pretty obvious. The nodes can coalesce only if they are of the same kind. While a cdata _is_ a text node all cdata nodes are converted to simple text nodes and then all of the text nodes coalesce into one. The state in the DOM is always that there is a single text node after coalescing. >> >> Norbert >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Aug. 11, 2010