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

Re: [Pharo-project] which Shout repository should we use?

by Tudor Girba

But, a simple instance variable rename would solve the problem for now. Why is that not good enough now and then remove it later? Cheers, Doru On 16 Aug 2010, at 18:25, Lukas Renggli wrote: > 2010/8/16 Mariano Martinez Peck <marianopeck(a)gmail.com>: >> >> >> On Sun, Aug 15, 2010 at 6:21 PM, StÃ©phane Ducasse >> <stephane.ducasse(a)inria.fr> wrote: >>> >>> this is a good question. >>> for now I would just update the configuration to point for the >>> repo of >>> lukas :) >> >> But now for example, I need to remove the style instVar in >> PluggableShoutMorph because in Pharo 1.2 it has already such instVar. >> But I don't know if I can commit or if Lukas would integrate such >> change in >> his repo beacuse that will break Shout to load in Pharo 1.1 (the >> image he >> uses) > > I will fix it as soon as the PharoCore 1.2 release candidate is out > and I am able to use the image. > >> so... lukas what do you think we should do? > > So either fix it in Pharo or create your own 'temporary' version of > Shout in the repository where you keep all the versions for building > the images. > > Lukas > > -- > 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 -- www.tudorgirba.com "We cannot reach the flow of things unless we let go."

Aug. 16, 2010

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

by laurent laffont

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 >

Aug. 16, 2010

Re: [Pharo-project] whileTrue: implementation

by merlyn＠stonehenge.com

>>>>> "Hernan" == Hernan Wilkinson <hernan.wilkinson(a)gmail.com> writes: Hernan> whileTrue: aBlock Hernan> self value ifTrue: [ Hernan> aBlock value. Hernan> thisContext restart ] That's an interesting implementation, but the current implementation is clean, and is there only because #perform: has to be able to do it. Maybe this definition could be added as a comment to the method though, to show how you would do it *if* it wasn't inlined. -- Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095 <merlyn(a)stonehenge.com> <URL:http://www.stonehenge.com/merlyn/> Smalltalk/Perl/Unix consulting, Technical writing, Comedy, etc. etc. See http://methodsandmessages.vox.com/ for Smalltalk and Seaside discussion

Aug. 16, 2010

[Pharo-project] whileTrue: implementation

by Hernan Wilkinson

Hi, when I'm teaching OO one of the most interesting subjects is the implementation of control flow structures with closures. Having to implement #ifTrue: only with objects and messages produces in some students the "click" we are looking for, the "ah!" that makes them see the real difference with procedural languages and most no pure object languages (java, c#, etc). When teaching the execution model, I use the #whileTrue: implementation to show them that it is also possible to implement such a thing with just objects and messages. The last semester to my surprise I saw that the #whileTrue: implementation in Pharo is cumbersome, at least for teaching porpoises, because it is based on the "hidden" detail that #whileTrue: is inlined, therefore never sent and its method never executed. The VisualWorks implementation is clearer because it is a recursive implementation that seems to work without knowing that #whileTrue: is inlined (and has a nice comment that explains that implementation detail). Anyway, just for teaching porpoises I thought that providing another implementation would be nice, an implementation based on the execution context, an implementation completely based on objects and messages. For example: whileTrue: aBlock self value ifTrue: [ aBlock value. thisContext restart ] I think it is an interesting example that allows the students to see how we can manipulate the execution environment from inside Smalltalk itself... Anyway, just a comment... not sure if it makes sense to change the implementation just because of this, but maybe putting a comment explaining this option would be nice. Bye, Hernan.

Aug. 16, 2010

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

by Nick Ager

Gary Chambers <gazzaguru2(a)btinternet.com> wrote: > http://www.squeaksource.com/@Ka2Wqd72TUsS6-Xj/xrbmFt3Z > > Hopefully, else search SqueakSource for "Camp Smalltalk London" > > or try: http://www.squeaksource.com/CampSmalltalkLondon > >Lots of cool things can be done simply... (c.f Camp Smalltalk London wrt. >> >>> Google Maps)... >>> >> >> Here's the message I posted on the mail list: Though it's been a couple of weeks since CampSmalltalk London, I've only just got round to creating a ConfigurationOfCampSmalltalkLondon which can be used to download the beginners tutorial Tim Mackinnon and I created. First some context. The beginners tutorial ran on the first day. We had 9 developers with a mixed background in Ruby/Java/C#/PHP etc. We started by going through the excellent ProfStef tutorial which we used as jump off point for frequent asides into the tools and code in Pharo. Next we gave them a simple exercise. You can download the code by grabbing ConfigurationOfCampSmalltalkLondon from http://www.squeaksource.com/MetacelloRepository.html and executing: (ConfigurationOfCampSmalltalkLondon project version: '1.0') load. The aim was to put into practice some of the concepts they'd learnt in the ProfStef tutorial - initially focusing on loops. The tutorial grabs live traffic information from the SE of the UK. Initially there is only one entry in the list viewable from their image at: http://localhost:8080/camp-smalltalk-london The first task was to change the code in CSLTransportInfo>>renderPage: to loop over the results and pass them to a custom renderer. Note we wanted to pass-on the joy of developing a web app in Smalltalk - the liveliness of the environment, code editing in the debugger etc - without first having to learn Seaside. So we hid the Seaside code behind some custom renderers. The second task was the change the renderer in CSLTransportInfo>>modelRenderer to be a CSLListItemRenderer. The task here was to notice the signature of the addItem method had changed and use the inspector and the browser to discover the relevant accessors on the result items. Finally they changed the renderer again for a CSLMapRenderer and went through a similar routine to step two, though this time the result of their labours was to transform a boring list into an impressive map - graphically showing traffic incidents. Those who were more advanced could then filter the results to look at say only incidents along particular roads etc. The tutorial session seemed to be well received. I don't know if anyone out there is planning to run an introduction to Smalltalk - if so they are more than welcome to use the code.

Aug. 16, 2010

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

by Gary Chambers

http://www.squeaksource.com/@Ka2Wqd72TUsS6-Xj/xrbmFt3Z Hopefully, else search SqueakSource for "Camp Smalltalk London" Regards, Gary ----- Original Message ----- From: "Torsten Bergmann" <astares(a)gmx.de> To: <pharo-project(a)lists.gforge.inria.fr> Sent: Monday, August 16, 2010 4:31 PM Subject: [Pharo-project] Pharocasts: Display Picasa photos > >Lots of cool things can be done simply... (c.f Camp Smalltalk London wrt. >>Google Maps)... > > Tell us more ... > > Bye > T. > -- > GMX DSL SOMMER-SPECIAL: Surf & Phone Flat 16.000 fÃ¼r nur 19,99 Â¿/mtl.!* > http://portal.gmx.net/de/go/dsl > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Aug. 16, 2010

Re: [Pharo-project] Contributors page (was little pictures of you)

by Igor Stasenko

On 15 August 2010 18:24, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >> >> Yes, definitely. I can say, in my own experience, that trying to fix >> bugs help me learn a lot of things >> about the environment itself (Are things that if I'm not looking at >> for fix bugs surelly will not look). > > This is cool I learned a lot doing that since squeak 3.3. or 3.2 > (In fact I started to talk about marcus about jazz when we were both harvesters > and never meet.) > >> Obviously, I'm not talking about igor and other people with a lot more >> knowledgment than me, only >> commenting my own experience. And by other hand, if I use Pharo, I >> feel the need of help on the >> development, it's the open source spirit. > > Thanks. > I think that taking care of a stuff that can help you for your projects is important in general. > For example people can ask themselves: why stef is spending so much time on ESUG (because this is a lot of time > and energy), well simple, when I discovered Smalltalk I went to the conf and it was dying (both the language > and the conference) so I thought either I complain: "oh my language is dying sniff sniff", "when I was young there > were a cool conference". Or I do something to try to make the future better. > Simple is n't it? Something you do not know if it will work but trying is the only chance we got. > Yes, it is. There is a little people who put as much energy into it (smalltalk in general) as you do, totally freely, without any business agenda. I can only applaud your efforts and wish you success. And, please continue :) >> About the pics page, I think that is very important to expose our >> names to possible companies >> requiring work, very important to freelancers as me. >> >> Just my opinion. > > This is an important one :) > Pharo is our software not mine. > > Stef > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Best regards, Igor Stasenko AKA sig.

Aug. 16, 2010

Re: [Pharo-project] Working on Pharo 1.2

by Sean P. DeNigris

StÃ©phane Ducasse wrote: > > Yes. I think that this is better to put it in SmalltalkImage. > Done, new version uploaded to inbox. -- View this message in context: http://forum.world.st/Working-on-Pharo-1-2-tp2322972p2327151.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Aug. 16, 2010

Re: [Pharo-project] Ideas of AutomaticMethodCategorizer ???

by Mariano Martinez Peck

On Sun, Aug 15, 2010 at 9:12 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr > wrote: > > On Aug 15, 2010, at 8:55 PM, Mariano Martinez Peck wrote: > > > Hi folks...while browsing AutomaticMethodCategorizer I found the place > where the rules are defined. It is cool becuase we can add the rules we > want. I am all ears. > > yes I would really like to have consistent categories. > Now we should pay attention that the automaticmethodcategory does not do > anythin when the category is * something. > > Stef > > > > For now, it is doing this: > > > > > > defaultCategorizationRules > > > > "The order is relevant, the categorizer uses the first rule matching > - DF" > > > > ^OrderedCollection new > > add: MethodCategorizationRule forAccessors; > > add: (MethodCategorizationRule whenSelectorMatches: 'initialize*' > categorizeIn: #initialization); > > #initialize > > > add: (MethodCategorizationRule whenSelectorMatches: 'is*' > categorizeIn: #testing); > > add: (MethodCategorizationRule whenSelectorMatches: 'has*' > categorizeIn: #testing); > > add: (MethodCategorizationRule whenSelectorMatches: '=' > categorizeIn: #comparing); > > add: (MethodCategorizationRule whenSelectorMatches: 'hash' > categorizeIn: #comparing); > > add: (MethodCategorizationRule whenSelectorMatches: 'default*' > categorizeIn: #defaults); > > add: (MethodCategorizationRule whenSelectorMatches: 'printOn:' > categorizeIn: #printing); > > add: (MethodCategorizationRule whenSelectorMatches: 'accept:' > categorizeIn: #'visitor accepting'); > > add: (MethodCategorizationRule whenSelectorMatches: 'visit*:' > categorizeIn: #visiting); > > add: (MethodCategorizationRule whenSelectorMatches: 'value' > categorizeIn: #evaluating); > > add: (MethodCategorizationRule > > whenSelectorMatches: 'test*' > > andClassInheritsFrom: TestCase > > categorizeIn: #tests); > > add: MethodCategorizationRule > usingMostUsedCategoryInSuperClasses; > > add: MethodCategorizationRule usingMostUsedCategoryInImage; > > yourself > > > One important thing I forgot to say is that the order is important here. Notice that the pattern rules are first and then the rules for the most used categories...this means that for example printOn: will be always in 'printing'. However, in the system most printOn: could be in 'print' category... So it is important what you want more...if specific patterns or maintain consistency with what you have in the system... cheers mariano > > > > > > We should improve this guy.... ideas to add/change? > > > > Cheers > > > > Mariano > > _______________________________________________ > > 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. 16, 2010

Re: [Pharo-project] which Shout repository should we use?

by Lukas Renggli

2010/8/16 Mariano Martinez Peck <marianopeck(a)gmail.com>: > > > On Sun, Aug 15, 2010 at 6:21 PM, StÃ©phane Ducasse > <stephane.ducasse(a)inria.fr> wrote: >> >> this is a good question. >> for now I would just update the configuration to point for the repo of >> lukas :) > > But now for example, I need to remove the style instVar in > PluggableShoutMorph because in Pharo 1.2 it has already such instVar. > But I don't know if I can commit or if Lukas would integrate such change in > his repo beacuse that will break Shout to load in Pharo 1.1 (the image he > uses) I will fix it as soon as the PharoCore 1.2 release candidate is out and I am able to use the image. > so... lukas what do you think we should do? So either fix it in Pharo or create your own 'temporary' version of Shout in the repository where you keep all the versions for building the images. Lukas -- Lukas Renggli www.lukas-renggli.ch

Aug. 16, 2010