August 2010 - Pharo-dev - lists.pharo.org

[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

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. 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. Stef 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

Aug. 11, 2010

Re: [Pharo-project] Inter-image communication

by StÃ©phane Ducasse

rst? RemoteSmalltalk? > > How would I, from one image, tell another image to execute something? > > I searched Google and the Squeak and Pharo lists for: > - "[Pharo|Squeak] inter-image communication" > - "[Pharo|Squeak] script" > > The results included various references to old projects that I never hear > mentioned now, and instructions on how to run code (via a .st as an argument > to the vm command line) when launching an image. > > Thanks. > Sean > -- > View this message in context: http://forum.world.st/Inter-image-communication-tp2320723p2320723.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > > _______________________________________________ > 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] Fixed: Issue 2754 - DateAndTime creation from string/stream using incorrect default offset

by StÃ©phane Ducasse

thanks for the explanation. I will integrate your changes. Stef >> what is the DateAndTime localOffset? "Answer the duration we are offset >> from UTC" >> > http://en.wikipedia.org/wiki/Coordinated_Universal_Time - > In casual use, when fractions of a second are not important, Greenwich Mean > Time (GMT) can be considered equivalent to UTC or UT1. In fact, saying "GMT" > often implies either UTC or UT1. For this reason, saying "GMT" is generally > avoided in technical contexts, with an unambiguous terminology of "UTC" or > "UT1" preferred instead. > > > StÃ©phane Ducasse wrote: >> >> Your changes basically uses DateAndTime localOffset when no offset is >> specified (and before it used zero). >> It sounds reasonable but I was wondering the impact. >> > Yes, that's correct. I changed it for two reasons: > 1. when someone says, "6pm," I don't think they ever mean GMT (unless, of > course, that's their local time). > 2. The non-[string|stream] instance creation methods (e.g. DateAndTime date: > Date today time: Time now) do not operate that way, and return a DateAndTime > like "2010-08-10T17:11:36-04:00" (with my local offset) > > HTH, > Sean > -- > View this message in context: http://forum.world.st/Fixed-Issue-2754-DateAndTime-creation-from-string-str… > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > > _______________________________________________ > 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] Fwd: Re: Squeaksource XML Parser - Enhanced support for CDATA Sections

by Norbert Hartl

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

Aug. 11, 2010

Re: [Pharo-project] TextMorph without being able to be edited?

by Carla F. Griggio

Fernando, that works fine in an updated 1.2 image :) 2010/8/9 Fernando olivero <oliverof(a)lu.unisi.ch> > Did you try in an updated 1.2 image? > > (Menu tools Software update) > > Please let me know, because is working fine for me in Gaucho, since a while > now. > And i'm using an updated 1.2 image. > > Saludos, > Fernando > > > On Aug 9, 2010, at 10:11 PM, Carla F. Griggio wrote: > > :D ! Great! Thanks. > > But it seems that a NewTextMorph doesn't understand autoFit: nor padding: > :( > > I don't really care about the padding now, but I'd like to have this morph > 'autofitted' :P How come that it works for you (Fernando) and not me? :S > I found that if I send #fitToParagraph to the NewTextMorph instance after I > set it's text, it fits OK. > > I still have to try Bill's suggestion. > > Thanks! > Carla > > On Mon, Aug 9, 2010 at 6:27 AM, StÃ©phane Ducasse < > stephane.ducasse(a)inria.fr> wrote: > >> Yes! >> >> On Aug 9, 2010, at 11:07 AM, Fernando olivero wrote: >> >> > Try NewTextMorph! >> > >> > t := NewTextMorph new. >> > t >> > borderWidth: 1; >> > borderColor: Color red; >> > color: Color white; >> > padding: 5 ; >> > readOnly: true; >> > autoFit: true ; >> > text: 'I present my text as read only ' asText ; >> > openInWorld. >> > >> > Fernando >> > On Aug 7, 2010, at 12:26 PM, Carla F. Griggio wrote: >> > >> >> Hi again, everyone! >> >> >> >> I think this might be really really silly, but I couldn't find a way to >> show a TextMorph without the ability to edit it's text. >> >> If I use a StringMorph to show a paragraph, it looks horrible, but if I >> use a TextMorph and click on it, a blue border appears and I'm able to edit >> the text, I don't want that to happen. >> >> >> >> Is there another morph for showing text that only shows text and >> nothing else? Or a property of TextMorph that I'm missing? >> >> >> >> >> >> Thanks! >> >> Carla >> >> <ATT00001..txt> >> > >> > _______________________________________________ >> > 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 >> > > <ATT00001..txt> > > > > _______________________________________________ > 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] Inter-image communication

by Sean P. DeNigris

How would I, from one image, tell another image to execute something? I searched Google and the Squeak and Pharo lists for: - "[Pharo|Squeak] inter-image communication" - "[Pharo|Squeak] script" The results included various references to old projects that I never hear mentioned now, and instructions on how to run code (via a .st as an argument to the vm command line) when launching an image. Thanks. Sean -- View this message in context: http://forum.world.st/Inter-image-communication-tp2320723p2320723.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Aug. 11, 2010