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

Re: [Pharo-project] Redirect CI link
by Marcus Denker Sept. 3, 2011

Sept. 3, 2011

On Aug 30, 2011, at 8:45 PM, Torsten Bergmann wrote: > Anyone able to redirect "http://ci.pharo-project.org" > from old hudson https://pharo-ic.lille.inria.fr/hudson/ > to new Jenkins https://ci.lille.inria.fr/pharo/ > Oh, yes, we will change that (might take a bit as Adrian is on Holidays) > > Would also be nice if "bugs.pharo-project.org" would > point to the issue tracker as well (similar to "issues.pharo-project.org") > ok. > Thanks > T. > -- > Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir > belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de > -- Marcus Denker -- http://marcusdenker.de

1 1

Re: [Pharo-project] [squeak-dev] Contexts must only be created with newForMethod: ...
by Mariano Martinez Peck Sept. 2, 2011

Sept. 2, 2011

Hi Chris. Yes, I have this problem when materializing MethodContext instances in Fuel. I've solved it adding the method: ContextPart class >> newFromFrameSize: aFrameSize ^ super basicNew: aFrameSize but it is a hack. So yes, if there is no real reason to do the opposite, I would change #basicNew: Cheers On Mon, Aug 1, 2011 at 8:27 PM, Chris Muller <ma.chris.m(a)gmail.com> wrote: > .. but #newForMethod: requires more in the API than it really uses. > It only checks the methods #frameSize to determine what basicSized > MethodContext to create - it doesn't actually set its method from the > one passed in. > > newForMethod: aMethod > --- (comment snipped for brevity) --- > ^ super basicNew: aMethod frameSize > > So, would it be ok to relax MethodContext class>>basicNew: to something > like: > > basicNew: size > ^ (size = CompiledMethod smallFrameSize or: [ size = > CompiledMethod fullframeSize ]) > ifTrue: [ super basicNew: size ] > ifFalse: [ self error: 'Contexts must be ', > CompiledMethod smallFrameSize, ' or ', CompiledMethod fullframeSize, ' > bytes.' ] > > -- Mariano http://marianopeck.wordpress.com

2 2

[Pharo-project] Build failed in Hudson: Pharo 1.3 #255
by marcus.denker＠inria.fr Sept. 1, 2011

Sept. 1, 2011

See <https://pharo-ic.lille.inria.fr/hudson/job/Pharo%201.3/255/> ------------------------------------------ D?marr? par le projet amont "Pharo Core 1.3" de num?ro de build 400 Construction ? distance sur pharo-build.lille.inria.fr [Pharo 1.3] $ /bin/sh -xe /tmp/hudson6883078532781447625.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:

1 2

[Pharo-project] DrGeo release 11.08
by Hilaire Fernandes Sept. 1, 2011

Sept. 1, 2011

I am pleased to announce release 11.08 of DrGeo for GNU-Linux/Windows/Mac OSX. As always the application is distributed under the form of an unique universal portable bundle for the three systems. http://www.ofset.org/drgeo ChangeLog * Release 11.08 - Thanks to the Pharo Smalltalk community for its continuous support - Special greeting to Henrik. * #2929 Simplify the way to load a sketch: now the user selects the sketch to open from a preview list * User can open sketch from an examples repository or from its own 'MySketches' repository. Change accordingly the load and save file operation. * In the toolbar, new icon button to create a blank sketch, keep or open an existing sketch * DrGeo is now touchpad friendly for a better user experience on tablet PC * #13010 Secure the edited free value * #12785 undo/redo angle: lost arc * #12782 Use smaller font to print 3 points angle * #12786 label should be selectable first * #12784 Assist to name object * Rendering speed improvements * Properly save sketch as UTF-8 file

2 2

[Pharo-project] editing methods without header
by Tudor Girba Sept. 1, 2011

Sept. 1, 2011

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

3 2

Re: [Pharo-project] [Pharo-users] PLEASE HELP testing Pharo 1.3 One Click [WAS] Pharo 1.3 release
by Marcus Denker Sept. 1, 2011

Sept. 1, 2011

On Aug 31, 2011, at 8:22 PM, Lukas Renggli wrote: > The image contains outdated versions of RB and OB that miss some > critical fixes. How can I know? It is is build using the latest MetaCello config... if the config needs to be updated, it needs to be updated. It does not happen by itself. > Also there some proposed fixes don't seem to be > included <http://code.google.com/p/pharo/issues/list?q=milestone%3D1.3> > yet? > No... I have not yet found the energy to do that. Marcus -- Marcus Denker -- http://marcusdenker.de

9 19

[Pharo-project] Scriptable CompileMethod interface
by Camillo Bruni Sept. 1, 2011

Sept. 1, 2011

Today on the train I was a bit bored on what I can do with CompiledMethodsâ¦ It seems like there are no inspection methods on CompiledMethods. Now I lets say I use Pharo from the command line (we're almost thereâ¦) then I would like to have a small interface to browse and navigate through methodsâ¦ (Object >> #at:) overrides "return all direct overrides of this method" (Bag >> #at:) super "return the method I override" (Bag >> #at:) superChain "return all implementations in superclasses" (Object >> #name) senders (Object >> #name) implementors instead of doing something like SystemNavigation default allCallsOn: #name "(BTW I would prefer allSendersOf: #name)" What do you think? Does this make sense or not? cami

3 5

[Pharo-project] what's the standard way of finding out from Smalltalk if one is running headless?
by Eliot Miranda Aug. 31, 2011

Aug. 31, 2011

I thought to test things like Display extent & DisplayScreen actualScreenDepth but these either fall back to values in the pre-headless image or don't fail and answer the actual display depth, even though the VM is running headless (at least on Mac they do). -- best, Eliot

4 3

Re: [Pharo-project] Pharo 1.3 release
by Marcus Denker Aug. 31, 2011

Aug. 31, 2011

On Aug 31, 2011, at 7:54 PM, Sven Van Caekenberghe wrote: > > On 31 Aug 2011, at 18:29, Igor Stasenko wrote: > >> Update (for the impatient) >> >> Marcus and i made a beta version of one-click image, which can be >> downloaded from here: >> >> https://gforge.inria.fr/frs/download.php/28922/Pharo-1.3-OneClick.zip >> >> works on: mac, ubuntu, windoze > > Super! > > Some small remarks (we want this to be perfect, don't we): No, honestly I just want to be ablet to release at all... Perfection (TM) is for the next release. > on Mac OS X, the About menu should be changed to 'About Pharo', the Help menu should be changed to 'Pharo Help'; some items on the World menu have no icon, most notably the System Browser and Transcript. > Patches are welcome... keep in mind that system menu related things might require VM changes and might take a while. > Also, I think that it would be very cool if a normal user like me can take the image and run all unit tests and be amazed that they all pass: that would really inspire new users and instill a quality feeling. > Known bug, has something to do with networking. http://code.google.com/p/pharo/issues/detail?id=4495 Marcus -- Marcus Denker -- http://marcusdenker.de

5 12

[Pharo-project] PLEASE HELP testing Pharo 1.3 One Click [WAS] Pharo 1.3 release
by Mariano Martinez Peck Aug. 31, 2011

Aug. 31, 2011

On Wed, Aug 31, 2011 at 6:29 PM, Igor Stasenko <siguctua(a)gmail.com> wrote: > Update (for the impatient) > > Marcus and i made a beta version of one-click image, which can be > downloaded from here: > > https://gforge.inria.fr/frs/download.php/28922/Pharo-1.3-OneClick.zip > > So...this is the last pending thing for Pharo 1.3. Can you help us and test it ? > works on: mac, ubuntu, windoze > > > > -- > Best regards, > Igor Stasenko AKA sig. > > -- Mariano http://marianopeck.wordpress.com

2 1