December 2013 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Pharo3 issues
by Stephan Eggermont Dec. 31, 2013

Dec. 31, 2013

Jannik wrote >- In a browser, when I did a change in the source code of a method, > then I select another method, the changes are lost, without asking if I want to save changes. Thanks Nicolai, for the fast results. I retested. Resolved, Fix to Include Stephan

1 0

FogBugz status change
by Nicolai Hess Dec. 31, 2013

Dec. 31, 2013

Can everybody change the status of an issue? I would like to change 12521 from *Resolved (Fix Reviewed by the Monkey**)* *to* Resolved (Fix To Include) Or how does reviewing work? Nicolai

8 14

Pharo on #code2013
by Yuriy Tymchuk Dec. 31, 2013

Dec. 31, 2013

Letâs promote Pharo by tweeting: âPharo #code2013â Cheers! Happy new year. Uko

1 0

pharo 3.0 image
by Johan Brichau Dec. 30, 2013

Dec. 30, 2013

What is the latest âworkingâ pharo 3 image? Every recent build I try to download opens with a blank screen and I cannot do anything. The latest build I downloaded some time ago was 30526 and that one opens fineâ¦ Ideas? Johan

8 15

Are #explorerContents and #hasContentsInExplorer obsolete ?
by Sven Van Caekenberghe Dec. 30, 2013

Dec. 30, 2013

Hi, It seems that #explorerContents and #hasContentsInExplorer are no longer used. Implementing a new Eye inspector with #addSpecialFields: seems to affect both the Inspector view as well as the Tree Inspector. So, should they be removed ? Sven

4 5

MessageBrowser doesn't play well with RGCommentDefinition as search results
by Nicolai Hess Dec. 30, 2013

Dec. 30, 2013

Hi, I am about to file in a whole bunch of issues regarding MessageBrowser. All are related to search result of the kind RGCommentDefinition. These are collected by SystemNavigation or doing a search: "class comments with it" or "method source with it". Most of you may not recognize these bugs, as the typically "senders of it", "implementors of it" search results doesn't suffer from these. (and doing search "class comments with it" isn't used that often from all, I think) But for newcomers searching strings through "method source with it" is an handy task for exploring the image. And this search mixes search results of RGCommentDefinition and RGMethodDefinition. And it is annoying for newcomers to stumble of not working buttons/menus without realizing that there is actually a difference in the search results. These bugs are: In MessageBrowser, search results of kind RGCommentDefinition - have no working context menu - use syntax highlighting for a class comment text - can not be changed (raising an error on accept) - Browse button opens the Systembrowser but it does not show the comment text, but the class definition - Senders button opens a MessageBrowser for selectors containing the symbol #Comment - Implementors button searches for implementors of a "Comment" selector (no search results) - Version button raises an error - switch source formatter to "Byte Code" or "Time stamp" raises an error I would add all issues under one parent issue (MessageBrowser doesn't play well with RGCommentDefinition) I don't consider all issues as "must fix", some are real bugs (all that raising an error) and some are more like enhancements (useless syntax highlight for comment text) But I would like to fix them all and maybe even all at once. What do you think? All for Pharo3, none for Pharo3, split them by bugfixes for 3 and "nice to have" for 4? Nicolai

2 1

Commit rights to Pharo repositories
by HernÃ¡n Morales Durand Dec. 29, 2013

Dec. 29, 2013

Hi, I want to publish configurations for Pharo 3.0 http://www.smalltalkhub.com/#!/~Pharo/MetaRepoForPharo30 Can you grant me commit rights? Could I be added to the Pharo team? username: hernan Cheers, HernÃ¡n

2 1

Tagging #catalogContactInfo?
by HernÃ¡n Morales Durand Dec. 29, 2013

Dec. 29, 2013

Hi Stef, Is there any format for defining #catalogContactInfo contents? For example ^ '[[Author:Walter White]] [[e-mail: blabla(a)bla.com]] [[website: http://www.www.www]]' Cheers, HernÃ¡n

2 1

Tanker and Pharo3
by Guillermo Polito Dec. 29, 2013

Dec. 29, 2013

Hi guys! I was taking a look at tanker to use it to load packages on a mini image. And I found some difficulties :). - First, the code does not load well in Pharo3. There are some classes/traits that changed and the class extensions do not want to load. I fixed that by adding some stub classes with the same name. And I was able to load the code - Then, almost all tests fail. The same problem is in the CI job ( https://ci.inria.fr/pharo-contribution/job/Tanker/PHARO=30,VERSION=bleeding…) So, I was having a look at them. I fixed many, but many other things scape from my not so deep understanding of tanker: * it uses the old class builder. I changed that reference for the OldClassBuilderAdapter * it tries to decompile code when sources are not available... So far I replaced that by the #codeForNoSource which actually does something different... * there is a problem with extension methods and local selectors. I don't yet understand where they are being built. Probably it has to do with RPackage-Tanker integration. * then some tanker tests make assumptions about the order of literals, which has changed (probably because of opal) Is it worth to invest some hours/days in tanker? :) Can I help? I have my changes but I cannot commit them, should we move it to Pharo or PharoExtras? Guille

2 1

Dec. 29, 2013

Thanks for your reactivity :) I will add the following to the draft of the XML chapter. Monty could you register to the pharo mailing-list because this is the place where people communicate? You put a big gmail filter that just show you mail about XML :) Stef > With Zinc patched using the fileOut attached (which I emailed to Sven) and the latest XMLParser packages, Satoshi's code works fine. But it takes a while to make the 12 (!) HTTP requests needed for the external DTD and external entities it includes. It is good to use the caching resolver for this sort of thing: > > resolver := DTDCachingEntityResolver new. > xml := '<?xml version="1.0" encoding="UTF-8" standalone="no"?> > <!DOCTYPE score-partwise PUBLIC > "-//Recordare//DTD MusicXML 3.0 Partwise//EN" > "http://www.musicxml.org/dtds/partwise.dtd"> > <score-partwise version="3.0"> > <part-list> > <score-part id="P1"> > <part-name>Music</part-name> > </score-part> > </part-list> > <part id="P1"> > <measure number="1"> > <attributes> > <divisions>1</divisions> > <key> > <fifths>0</fifths> > </key> > <time> > <beats>4</beats> > <beat-type>4</beat-type> > </time> > <clef> > <sign>G</sign> > <line>2</line> > </clef> > </attributes> > <note> > <pitch> > <step>C</step> > <octave>4</octave> > </pitch> > <duration>4</duration> > <type>whole</type> > </note> > </measure> > </part> > </score-partwise> > '. > (XMLDOMParser on: xml) > externalEntityResolver: resolver; > parseDocument. > > If you evaluate it, and then after, evaluate just the last three lines, it's faster the second time because the HTTP requests didn't have to be made again. > > I did remove one test you added that used the same external DTD as Satoshi, because the rest of the XML didn't comform to the DTD and still raised validation exceptions even though the "DNU #asciiValue" error is gone. Excellent! > I think it's best anyway not having unit tests make HTTP requests if posssible (especially not 12), otherwise you have random test failures because a server or network is down: > http://xunitpatterns.com/Unit%20Test%20Rulz.html Indeed when I wrote the test I had no idea what was the problem. > I try to test everything short of actual HTTP or File interaction (like the path resolution tests in testHTTPClientPaths/testFileClientPaths). > > I don't have enough time to author anything at the moment, but I appreciate the offer. If you take some notes let me know :) > And I appreciate the work you've done on Pharo and Squeak over the years. I learned Smalltalk through Pharo By Example, and there are probably many others who also did. > >> >> ----- Original Message ----- >> From: StÃ©phane Ducasse >> Sent: 12/28/13 05:15 AM >> To: monty >> Subject: Re: [Pharo-dev] problem while parsing xml >> >> Thanks a lot I forwarded your mail. >> This makes me thinking that it would be great to have a little documentation of the XML ecosystem in Pharo. >> If you are interested to co-author a book chapter with me it could be really great and fun. >> >> Stef >> >> >> >>> >>> Thanks for the CCs. I've identified the sources of the problem(s) and am working on it now and should have it fixed soon (though its not entirely confined to XMLParser, but the fixes outside are minimal). >>> >>> NOTE: You can always just disable resolvesExternalEntities: and isValidating: (or use parse:usingNamespaces:validation:externalEntities: with the last two args false) if they are causing problems. >>> >>>> ----- Original Message ----- >>>> From: StÃ©phane Ducasse >>>> Sent: 12/27/13 04:42 AM >>>> To: Pharo Development List >>>> Subject: Re: [Pharo-dev] problem while parsing xml >>>> >>>> ok I missed the example in the mail of satoshi I will try to have a look or at leat write a test. >>>> >>>> On 25 Dec 2013, at 19:04, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >>>> >>>>> >>>>> Hi Hernan >>>>> >>>>> how did you reproduce the bug? >>>>> Because it would be nice to fix it. >>>>> >>>>> Stef >>>>> >>>>> On 24 Dec 2013, at 18:48, HernÃ¡n Morales Durand <hernan.morales(a)gmail.com> wrote: >>>>> >>>>>> >>>>>> I have tried in Pharo 2.0 configurations from Config Browser (ConfigurationOfXMLParser-StephaneDucasse.16) and latest from http://www.smalltalkhub.com/mc/PharoExtras/XMLParser/main (ConfigurationOfXMLParser-monty.37) and both have this bug. >>>>>> HernÃ¡n >>>>>> >>>>>> 2013/12/24 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> >>>>>> Hi Satoshi >>>>>> >>>>>> Did you try with the latest configuration of XMLParser? >>>>>> Because I do not know what it is in Moose. >>>>>> Stef >>>>>> >>>>>> On 23 Dec 2013, at 18:26, NISHIHARA Satoshi <goonsh(a)gmail.com> wrote: >>>>>> >>>>>> > Hello >>>>>> > >>>>>> > using: Pharo3.0 Latest update: #30659 (it occurs same error to >>>>>> > Pharo2.0 Latest update: #20628) >>>>>> > (Moose 4.9 with XML-Parser (DamienCassou.143) has no_err) >>>>>> > >>>>>> > 1. load XMLParser (StephaneDucasse.16) from Configuration browser >>>>>> > 2. select and inspect it below: >>>>>> > ^ XMLDOMParser parse: '<?xml version="1.0" encoding="UTF-8" standalone="no"?> >>>>>> > <!DOCTYPE score-partwise PUBLIC >>>>>> > "-//Recordare//DTD MusicXML 3.0 Partwise//EN" >>>>>> > "http://www.musicxml.org/dtds/partwise.dtd"> >>>>>> > <score-partwise version="3.0"> >>>>>> > <part-list> >>>>>> > <score-part id="P1"> >>>>>> > <part-name>Music</part-name> >>>>>> > </score-part> >>>>>> > </part-list> >>>>>> > <part id="P1"> >>>>>> > <measure number="1"> >>>>>> > <attributes> >>>>>> > <divisions>1</divisions> >>>>>> > <key> >>>>>> > <fifths>0</fifths> >>>>>> > </key> >>>>>> > <time> >>>>>> > <beats>4</beats> >>>>>> > <beat-type>4</beat-type> >>>>>> > </time> >>>>>> > <clef> >>>>>> > <sign>G</sign> >>>>>> > <line>2</line> >>>>>> > </clef> >>>>>> > </attributes> >>>>>> > <note> >>>>>> > <pitch> >>>>>> > <step>C</step> >>>>>> > <octave>4</octave> >>>>>> > </pitch> >>>>>> > <duration>4</duration> >>>>>> > <type>whole</type> >>>>>> > </note> >>>>>> > </measure> >>>>>> > </part> >>>>>> > </score-partwise> >>>>>> > ' readStream. >>>>>> > >>>>>> > 3. and get DNU: SmallInteger>>asciiValue >>>>>> > >>>>>> > 'case of XMLZincClient>>#get: >>>>>> > 'http://www.musicxml.com/dtds/partwise.dtd' timeout: ... onError: ... >>>>>> > returns binaryStream? >>>>>> > >>>>>> > >>>>>> > -- >>>>>> > -- >>>>>> > "NISHIHARA Satoshi" >>>>>> > [:goonsh :nsh | ^ nishis perform: goonsh with: nsh] >>>>>> > <PharoDebug.log> >>>>>> >>>>>> >>> > > <ZnMimeType-isBinary.st>

1 0