- Pharo-dev - lists.pharo.org

[Pharo-project] [update 1.4] #14116

by StÃ©phane Ducasse

14116 ----- - Issue 4746: Improving PluggableListMorph. Thanks Benjamin van Ryseghem. http://code.google.com/p/pharo/issues/detail?id=4746 Stef

Sept. 1, 2011

[Pharo-project] [update 1.4] #14115

by StÃ©phane Ducasse

14115 ----- - Ring enhancements. Thanks Veronica Uquillas-Gomez and Benjamin van Ryseghem Stef

Sept. 1, 2011

[Pharo-project] [update 1.4] #14114

by StÃ©phane Ducasse

14114 ----- - Issue 4664: SystemAnnouncement is ready for integration. http://code.google.com/p/pharo/issues/detail?id=4664 - Issue 4618: Integration of RBEngine http://code.google.com/p/pharo/issues/detail?id=4618 Stef

Sept. 1, 2011

[Pharo-project] [update 1.4] #14114

by StÃ©phane Ducasse

14114 ----- - Issue 4664: SystemAnnouncement is ready for integration. http://code.google.com/p/pharo/issues/detail?id=4664 - Issue 4618: Integration of RBEngine http://code.google.com/p/pharo/issues/detail?id=4618 Stef ------------------------ Dr. StÃ©phane Ducasse -- Directeur de Recherche (Senior Researcher) INRIA - USTL - CNRS UMR 8022 stephane.ducasse(a)inria.fr http://stephane.ducasse.free.fr http://rmod.lille.inria.fr/ **NEW ***Tel 00 33 (0)3 20 43 42 56 - Fax 33 3 59 57 78 50 40, avenue Halley, Parc Scientifique de la Haute Borne, BÃ¢t.A, Park Plaza, Villeneuve d'Ascq, FR-59650, France.

Sept. 1, 2011

[Pharo-project] Build failed in Hudson: Pharo 1.3 #256

by marcus.denker＠inria.fr

See <https://pharo-ic.lille.inria.fr/hudson/job/Pharo%201.3/256/> ------------------------------------------ D?marr? par l'utilisateur denker Construction ? distance sur pharo-build.lille.inria.fr [Pharo 1.3] $ /bin/sh -xe /tmp/hudson134379665166826684.sh + /builds/builder/build13.sh -i Core1.3 -s dev3 -s pharo/version -o Pharo-1.3 [version] 1.3 #13300 + /builds/builder/build13.sh -i Pharo-1.3 -s testrunner -s delHDLintReport -s runalltests -o Pharo-1.3-AfterRunningTests + zip -r Pharo-1.3.zip Pharo-1.3/Pharo-1.3.changes Pharo-1.3/PharoV10.sources Pharo-1.3/Pharo-1.3.image updating: Pharo-1.3/Pharo-1.3.changes (deflated 79%) updating: Pharo-1.3/PharoV10.sources (deflated 76%) updating: Pharo-1.3/Pharo-1.3.image (deflated 57%) + zip -r Pharo-1.3-AfterRunningTests.zip Pharo-1.3-AfterRunningTests/Pharo-1.3-AfterRunningTests.changes Pharo-1.3-AfterRunningTests/Pharo-1.3-AfterRunningTests.image updating: Pharo-1.3-AfterRunningTests/Pharo-1.3-AfterRunningTests.changes (deflated 80%) updating: Pharo-1.3-AfterRunningTests/Pharo-1.3-AfterRunningTests.image (deflated 57%) + /builds/builder/build-oneclick.sh -i Pharo-1.3 -o PharoOneClick1.3 -n PharoOneClick1.3 -v 1.3 -c Pharo -t Pharo + sh /builds/builder/pharo-shell-scripts/SavePharo13.sh Archiving artifacts Enregistrement des r?sultats des tests ERROR: Failed to archive test reports hudson.util.IOException2: remote file operation failed: <https://pharo-ic.lille.inria.fr/hudson/job/Pharo%201.3/ws/> at hudson.remoting.Channel@18af45f9:pharo-build.lille.inria.fr at hudson.FilePath.act(FilePath.java:752) at hudson.FilePath.act(FilePath.java:738) at hudson.tasks.junit.JUnitParser.parse(JUnitParser.java:66) at hudson.tasks.junit.JUnitResultArchiver.parse(JUnitResultArchiver.java:108) at hudson.tasks.junit.JUnitResultArchiver.perform(JUnitResultArchiver.java:120) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) at hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:601) at hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:580) at hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:558) at hudson.model.Build$RunnerImpl.post2(Build.java:158) at hudson.model.AbstractBuild$AbstractRunner.post(AbstractBuild.java:528) at hudson.model.Run.run(Run.java:1264) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:122) Caused by: hudson.util.IOException2: Failed to read <https://pharo-ic.lille.inria.fr/hudson/job/Pharo%201.3/ws/Pharo-1.3-AfterRu…> at hudson.tasks.junit.TestResult.parse(TestResult.java:198) at hudson.tasks.junit.TestResult.parse(TestResult.java:139) at hudson.tasks.junit.TestResult.<init>(TestResult.java:102) at hudson.tasks.junit.JUnitParser$ParseResultCallable.invoke(JUnitParser.java:95) at hudson.tasks.junit.JUnitParser$ParseResultCallable.invoke(JUnitParser.java:70) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2028) at hudson.remoting.UserRequest.perform(UserRequest.java:114) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:270) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) Caused by: org.dom4j.DocumentException: Error on line 288 of document file:///builds/workspace/Pharo%201.3/Pharo-1.3-AfterRunningTests/Zinc-Tests-Test.xml : XML document structures must start and end within the same entity. Nested exception: XML document structures must start and end within the same entity. at org.dom4j.io.SAXReader.read(SAXReader.java:482) at org.dom4j.io.SAXReader.read(SAXReader.java:264) at hudson.tasks.junit.SuiteResult.parse(SuiteResult.java:94) at hudson.tasks.junit.TestResult.parse(TestResult.java:183) ... 14 more Caused by: org.xml.sax.SAXParseException: XML document structures must start and end within the same entity. at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:195) at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.fatalError(ErrorHandlerWrapper.java:174) at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:388) at com.sun.org.apache.xerces.internal.impl.XMLScanner.reportFatalError(XMLScanner.java:1414) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.endEntity(XMLDocumentFragmentScannerImpl.java:905) at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.endEntity(XMLDocumentScannerImpl.java:605) at com.sun.org.apache.xerces.internal.impl.XMLEntityManager.endEntity(XMLEntityManager.java:1393) at com.sun.org.apache.xerces.internal.impl.XMLEntityScanner.load(XMLEntityScanner.java:1763) at com.sun.org.apache.xerces.internal.impl.XMLEntityScanner.skipChar(XMLEntityScanner.java:1416) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:2792) at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:648) at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next(XMLNSDocumentScannerImpl.java:140) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:511) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:808) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:737) at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:119) at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1205) at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:522) at org.dom4j.io.SAXReader.read(SAXReader.java:465) ... 17 more Description set:

Sept. 1, 2011

Re: [Pharo-project] editing methods without header

by Lukas Renggli

> To maintain syntax highlighting: You have to call by SHOUT by hand, > adding and Â eliminating the selector+arguments line to/from the > resulting styled text. You don't have to do anything by hand: Set Shout to "workspace-mode" in #shoutAboutToStyle: and provide a dictionary with bindings for the arguments and the instance variables. Likely this currently doesn't work properly, but http://code.google.com/p/pharo/issues/detail?id=4609 should fix that. Lukas -- Lukas Renggli www.lukas-renggli.ch

Sept. 1, 2011

[Pharo-project] [update 1.4] #14113

by StÃ©phane Ducasse

14113 ----- - Issue 4724: polymorph fixes. Thanks Gary Chambers. http://code.google.com/p/pharo/issues/detail?id=4724 - ring compatibility method in CompiledMethod Stef

Sept. 1, 2011

Re: [Pharo-project] editing methods without header

by Fernando Olivero

What i've did is to use a NewTextMorph, displaying as the contents, the method's body source; and on each edition (which is announced by the new text morph), reapply the shout styling. To maintain syntax highlighting: You have to call by SHOUT by hand, adding and eliminating the selector+arguments line to/from the resulting styled text. If TextMorph announces edition also, you could use the same trick there. Fernando On Thu, Sep 1, 2011 at 12:29 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Hi, > > Currently, when we edit a method, we use one text morph that includes both the header and the body of the method. > > I am searching for an easy way to edit only the body of the methods, but still have completion and syntax highlighting. > > Any ideas of how to approach this? > > Cheers, > Doru > > > -- > www.tudorgirba.com > > "Be rather willing to give than demanding to get." > > > > >

Sept. 1, 2011

Re: [Pharo-project] Testing Pharo OneClick 1.3

by Damien Cassou

On Thu, Sep 1, 2011 at 9:57 AM, HernÃ¡n Morales Durand <hernan.morales(a)gmail.com> wrote: > Open Monticello Browser > Hit +Config > Hit Ok > Hit Cancel > Hit Cancel > Hit Cancel > ... I think HernÃ¡n refers to the dialog which asks for a username. This information is mandatory and you can't cancel. Don't know if this is a bug. Other reports are in the following issues: http://code.google.com/p/pharo/issues/detail?id=4741 http://code.google.com/p/pharo/issues/detail?id=4742 http://code.google.com/p/pharo/issues/detail?id=4744 http://code.google.com/p/pharo/issues/detail?id=4745 -- Damien Cassou http://damiencassou.seasidehosting.st "Lambdas are relegated to relative obscurity until Java makes them popular by not having them." James Iry

Sept. 1, 2011

Re: [Pharo-project] Testing Pharo OneClick 1.3

by Damien Cassou

I'm taking care of creating issues On Thu, Sep 1, 2011 at 9:57 AM, HernÃ¡n Morales Durand <hernan.morales(a)gmail.com> wrote: > Sorry no time to open tickets. > > Open Monticello Browser > Hit +Config > Hit Ok > Hit Cancel > Hit Cancel > Hit Cancel > ... > > OBSystemBrowser openOnClass: Behavior > select ObsoleteSubclasses class variable > hit mouse right-button > > Create a category > Create a class inside this category > Create another category (empty) > Rename the first category to be the second one > Nothing happens > > Tools -> Recover Lost Changes > Select any of the last 5 entries > MNU > > SystemNavigation default browseAllUnimplementedCalls. > MNU > > HernÃ¡n > > -- Damien Cassou http://damiencassou.seasidehosting.st "Lambdas are relegated to relative obscurity until Java makes them popular by not having them." James Iry

Sept. 1, 2011