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

Re: [Pharo-project] Load OB in Pharo 1.2

by Marcus Denker

On Aug 17, 2010, at 7:31 PM, Lukas Renggli wrote: >> Thanks Lukas. I wasn't who remove that class neither who didn't deprecated. >> I am just trying to start building Dev images from now...otherwise, we will >> have to wait a lot of time once the core is released. > > I think there must be a delay between the release of the core and the > non-core images. I don't see how that can otherwise work. Of course it > makes sense to have some incremental adaption already upfront ... Hmm... one thing is clear: I want to use Refactoring and especially the Code Critique tool on 1.2. So I need to somehow load it. (2 pages of philosophical ramblings deleted... I should start a blog..) Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

Aug. 17, 2010

Re: [Pharo-project] Load OB in Pharo 1.2

by Lukas Renggli

> Thanks Lukas. I wasn't who remove that class neither who didn't deprecated. > I am just trying to start building Dev images from now...otherwise, we will > have to wait a lot of time once the core is released. I think there must be a delay between the release of the core and the non-core images. I don't see how that can otherwise work. Of course it makes sense to have some incremental adaption already upfront ... Lukas > > thanks for your commits > >> >> Lukas >> >> 2010/8/17 Mariano Martinez Peck <marianopeck(a)gmail.com>: >> > Hi Lukas. Trying to evaluate: >> > >> > (ConfigurationOfOmniBrowser project version: '1.1-baseline') load: >> > 'Core >> > RB' >> > >> > I am trying to load OB and RB in Pharo 1.2 >> > >> > I found still refernces to Preferences and some other problems. >> > >> > I attach a changeset to fix the ones I found. If you want to check them >> > lukas would be nice :) >> > >> > Thanks >> > >> > Mariano >> > >> > _______________________________________________ >> > Pharo-project mailing list >> > Pharo-project(a)lists.gforge.inria.fr >> > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > >> >> >> >> -- >> Lukas Renggli >> www.lukas-renggli.ch >> >> _______________________________________________ >> 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 > -- Lukas Renggli www.lukas-renggli.ch

Aug. 17, 2010

Re: [Pharo-project] Load OB in Pharo 1.2

by Mariano Martinez Peck

On Tue, Aug 17, 2010 at 5:41 PM, Lukas Renggli <renggli(a)gmail.com> wrote: > I cannot integrate that change-set because it breaks OB in Pharo 1.1. > > PluggableButtonMorphPlus was never deprecated and now you say it just > disappeared? :-( > > Thanks Lukas. I wasn't who remove that class neither who didn't deprecated. I am just trying to start building Dev images from now...otherwise, we will have to wait a lot of time once the core is released. thanks for your commits > Lukas > > 2010/8/17 Mariano Martinez Peck <marianopeck(a)gmail.com>: > > Hi Lukas. Trying to evaluate: > > > > (ConfigurationOfOmniBrowser project version: '1.1-baseline') load: 'Core > > RB' > > > > I am trying to load OB and RB in Pharo 1.2 > > > > I found still refernces to Preferences and some other problems. > > > > I attach a changeset to fix the ones I found. If you want to check them > > lukas would be nice :) > > > > Thanks > > > > Mariano > > > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > > > -- > Lukas Renggli > www.lukas-renggli.ch > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Aug. 17, 2010

[Pharo-project] I will do integrate some fixes now....

by StÃ©phane Ducasse

Aug. 17, 2010

Re: [Pharo-project] Pharocasts: Display Picasa photos

by Gary Chambers

Ask away if you'd like more examples of Morphic/Polymorph things... Even for me, that was the first time I used a Block as the model for a button! :-) Regards, Gary ----- Original Message ----- From: laurent laffont To: Pharo-project(a)lists.gforge.inria.fr Sent: Monday, August 16, 2010 7:31 PM Subject: Re: [Pharo-project] Pharocasts: Display Picasa photos This example is really interesting, I've just learn a lot of things. Laurent On Mon, Aug 16, 2010 at 2:10 PM, Gary Chambers <gazzaguru2(a)btinternet.com> wrote: Indeed, nice... Here's an adaptation for Flickr... | xmlStream xmlDoc photos builder clickBlock | xmlStream := 'http://api.flickr.com/services/feeds/photos_public.gne?id=12018791@N06&lang…' asUrl retrieveContents contentStream. xmlDoc := XMLDOMParser parseDocumentFrom: xmlStream. photos := OrderedCollection new. xmlDoc tagsNamed: #item do: [:item| | title thumbUrl photoUrl | title := (item firstTagNamed: #title) characterData. thumbUrl := ((item firstTagNamed: #media:thumbnail) attributeAt: #url) asUrl. photoUrl := ((item firstTagNamed: #media:content) attributeAt: #url) asUrl. photos add: title -> (Form fromBinaryStream: thumbUrl retrieveContents contentStream) -> photoUrl]. clickBlock := [:url :title | | scrollPane | scrollPane := GeneralScrollPane new scrollTarget: (builder newImage: (Form fromBinaryStream: url retrieveContents contentStream)). scrollPane openInWindow setLabel: title; extent: 600@400. scrollPane color: Color transparent]. builder := UITheme builder. ((builder newRow: (photos collect: [:aPhoto| (builder newButtonFor: clickBlock getState: nil action: #value:value: arguments: {aPhoto value. aPhoto key key} getEnabled: nil label: ((builder newColumn: { builder newImage: aPhoto key value. builder newLabel: aPhoto key key}) cellPositioning: #center; layoutInset: 10) help: nil)])) wrapDirection: #topToBottom; openInWindow) setLabel: (xmlDoc firstTagNamed: #title) characterData; extent: 700@680. Regards, Gary ----- Original Message ----- From: "GermÃ¡n Arduino" <garduino(a)gmail.com> To: <Pharo-project(a)lists.gforge.inria.fr> Cc: "A friendly place where any question about pharo is welcome" <pharo-users(a)lists.gforge.inria.fr> Sent: Sunday, August 15, 2010 11:14 PM Subject: Re: [Pharo-project] Pharocasts: Display Picasa photos Excellent! 2010/8/15 laurent laffont <laurent.laffont(a)gmail.com>: Learn: - how to get data from an URL - parse XML documents - build a GUI to display photos with Polymorph - how to prototype quickly with debugger and inspector http://pharocasts.blogspot.com/2010/08/see-how-to-get-data-from-url-parse-x… Cheers, Laurent Laffont http://pharocasts.blogspot.com/ http://magaloma.blogspot.com/ _______________________________________________ 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 _______________________________________________ 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. 17, 2010

Re: [Pharo-project] Load OB in Pharo 1.2

by Lukas Renggli

On 17 August 2010 18:43, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Yes lukas we cleaned and merged all the *Plus classes are now in their superclass. > and for classes we do not really have a nice deprecate mechanism. Why can't you put a deprecated warning into basicNew? That would be really helpful, because otherwise this will always cause troubles like this. Lukas -- Lukas Renggli www.lukas-renggli.ch

Aug. 17, 2010

Re: [Pharo-project] possible XML enh

by Alexandre Bergel

I will look at them this week end. I have a major deadline on Friday Cheers, Alexandre On 17 Aug 2010, at 12:34, StÃ©phane Ducasse wrote: > Hi > > I was browsing fixes in squeak and I saw > http://code.google.com/p/pharo/issues/detail?id=2822 > May be this can help to improve the XML package. > > Stef > > Fix printing of XMLElements; add tests for behavior. > > =============== Diff against XML-Parser-mtf.30 =============== > > Item was added: > + ----- Method: XMLParserTest>>testPrintElements (in category 'tests') ----- > + testPrintElements > + | node | > + node:= (XMLElement new) name: 'foo'; > + setAttributes: (Dictionary new); > + yourself. > + self assert: node asString withBlanksTrimmed = '<foo/>'. > + > + node:= (XMLElement new) name: 'foo'; > + setAttributes: (Dictionary newFromPairs: {'id'. '123'}); > + yourself. > + self assert: node asString withBlanksTrimmed = '<foo id="123"/>'. > + > + node:= (XMLElement new) name: 'foo'; > + addContent: (XMLStringNode string: 'Hello World'); > + setAttributes: (Dictionary new); > + yourself. > + self assert: node asString withBlanksTrimmed = '<foo>Hello World</foo>'. > + > + node:= (XMLElement new) name: 'foo'; > + addContent: (XMLStringNode string: 'Hello World'); > + setAttributes: (Dictionary newFromPairs: {'id'. '123'}); > + yourself. > + self assert: node asString withBlanksTrimmed = '<foo id="123">Hello World</foo>'. > + > + ! > > Item was changed: > ----- Method: XMLElement>>isEmpty (in category 'testing') ----- > isEmpty > + "Answer true if the receiver is empty" > + > + ^self elementsAndContents isEmpty! > - ^self elements isEmpty! > > Item was changed: > ----- Method: XMLElement>>printXMLOn: (in category 'printing') ----- > printXMLOn: writer > + "Print the receiver in XML form" > + > writer startElement: self name attributeList: self attributes. > (writer canonical not > + and: [self isEmpty]) > - and: [self isEmpty and: [self attributes isEmpty not]]) > ifTrue: [writer endEmptyTag: self name] > ifFalse: [ > writer endTag. > self elementsAndContentsDo: [:content | content printXMLOn: writer]. > writer endTag: self name]! > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Aug. 17, 2010

Re: [Pharo-project] adding ISO-8859-15 and CP-1252 support

by StÃ©phane Ducasse

henrik thanks for the feedback. do you have any ideas of simple comments that could help? Because this part of pharo is just dark :) Stef On Aug 17, 2010, at 4:55 PM, Henrik Johansen wrote: > > On Aug 16, 2010, at 9:49 30PM, Philippe Marschall wrote: > >> Hi >> >> I decided to write ISO-8859-15 and CP-1252 support [1] (mostly for >> selfish reasons so that Seaside on Pharo would support ISO-8859-15 and >> CP-1252). > > > More converters are always nice :D > Their code seems ok to me. >> >> A couple of notes: >> - the five unmapped bytes of CP-1252 (not ISO-8859-15, the comment is >> wrong) are mapped to the Unicode replacement character (U+FFFD) >> - a new Latin9 language environment is introduced >> - some minor clean up like removing unused class variables >> >> I'd appreciate it if somebody knowledgeable in these areas could review >> the changes. I'm especially unsure about the Latin9 language >> environment, but reusing Latin1 or Unicode seemed wrong. > > I'm not sure its too wrong, according to EncodedCharSet comment: > "The other confusion comes from the name of "Latin1" class. It used to mean the Latin-1 (ISO-8859-1) character set, but now it primarily means that the "Western European languages that are covered by the characters in Latin-1 character set." > I'd reckon the same holds true for Latin1Environment (Western ), Latin2Environment (Eastern), and Latin7Environment (Greek). I don't think CP1252/8859-15 warrants the same as they are basically alternative encodings to latin1 for western languages. > > Also: > - leadingChar is used in StrikeFontSet to choose different glyph sets. This allows for StrikeFonts supporting more than the default latin1 glyphs, seems to me it would be "wrong" to use the same one for two different encodings. > Not sure why this approach was taken rather than allowing additional strike font sets based on unicode code point ranges, then using leadingChar only to differentiate when the visual glyphs for those code points would be different. I suspect it maybe was developed to deal with Han unification first, then reused to support multiple character sets later. > > - LanguageEnvironment seems to have been used in conjunction with translation (note the entire old translation system was removed in Pharo and replaced by an external package), maybe to decide which encoding externally stored translation files should be read in as. > Then, having environments with overlapping supportedLanguages seem somewhat weird as well. > Modifying defaultEncodingName/systemConverterClass of Latin1Environment to use CP1252 for some Windows systems (as per Latin2) may be another approach, may or may not lead to unintended consequences elsewhere though, I did not investigate all uses. > > IMHO, for someone who wasn't involved in its developemnt, the whole multilingual package could use some cleaning, more class comments, and clearer statement of responsibilities. > > Cheers, > Henry > > TLDR; > More converters: yay! > More LanguageEnvironments: o_O, not sure > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Aug. 17, 2010

Re: [Pharo-project] Load OB in Pharo 1.2

by StÃ©phane Ducasse

Yes lukas we cleaned and merged all the *Plus classes are now in their superclass. and for classes we do not really have a nice deprecate mechanism. Stef > I cannot integrate that change-set because it breaks OB in Pharo 1.1. > > PluggableButtonMorphPlus was never deprecated and now you say it just > disappeared? :-( > > Lukas > > 2010/8/17 Mariano Martinez Peck <marianopeck(a)gmail.com>: >> Hi Lukas. Trying to evaluate: >> >> (ConfigurationOfOmniBrowser project version: '1.1-baseline') load: 'Core >> RB' >> >> I am trying to load OB and RB in Pharo 1.2 >> >> I found still refernces to Preferences and some other problems. >> >> I attach a changeset to fix the ones I found. If you want to check them >> lukas would be nice :) >> >> Thanks >> >> Mariano >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > > > -- > Lukas Renggli > www.lukas-renggli.ch > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Aug. 17, 2010

[Pharo-project] possible XML enh

by StÃ©phane Ducasse

Hi I was browsing fixes in squeak and I saw http://code.google.com/p/pharo/issues/detail?id=2822 May be this can help to improve the XML package. Stef Fix printing of XMLElements; add tests for behavior. =============== Diff against XML-Parser-mtf.30 =============== Item was added: + ----- Method: XMLParserTest>>testPrintElements (in category 'tests') ----- + testPrintElements + | node | + node:= (XMLElement new) name: 'foo'; + setAttributes: (Dictionary new); + yourself. + self assert: node asString withBlanksTrimmed = '<foo/>'. + + node:= (XMLElement new) name: 'foo'; + setAttributes: (Dictionary newFromPairs: {'id'. '123'}); + yourself. + self assert: node asString withBlanksTrimmed = '<foo id="123"/>'. + + node:= (XMLElement new) name: 'foo'; + addContent: (XMLStringNode string: 'Hello World'); + setAttributes: (Dictionary new); + yourself. + self assert: node asString withBlanksTrimmed = '<foo>Hello World</foo>'. + + node:= (XMLElement new) name: 'foo'; + addContent: (XMLStringNode string: 'Hello World'); + setAttributes: (Dictionary newFromPairs: {'id'. '123'}); + yourself. + self assert: node asString withBlanksTrimmed = '<foo id="123">Hello World</foo>'. + + ! Item was changed: ----- Method: XMLElement>>isEmpty (in category 'testing') ----- isEmpty + "Answer true if the receiver is empty" + + ^self elementsAndContents isEmpty! - ^self elements isEmpty! Item was changed: ----- Method: XMLElement>>printXMLOn: (in category 'printing') ----- printXMLOn: writer + "Print the receiver in XML form" + writer startElement: self name attributeList: self attributes. (writer canonical not + and: [self isEmpty]) - and: [self isEmpty and: [self attributes isEmpty not]]) ifTrue: [writer endEmptyTag: self name] ifFalse: [ writer endTag. self elementsAndContentsDo: [:content | content printXMLOn: writer]. writer endTag: self name]!

Aug. 17, 2010