- Pharo-dev - lists.pharo.org

[Pharo-project] Troubles with #flushCache and #run:with:in:

by Lukas Renggli

Hi Eliot, I am using one of the latest VMs from your site (VM.r2434) and I continue to have subtle problems with objects as methods (#flushCache, #run:with:in:). The issue is that the test coverage in Pharo is kind of broken on Cog for a long time already. It reports methods as not covered that are clearly covered, and tests seem to randomly fail. I suspected that there is something wrong with the coverage code itself. So I started to experiment with TestCoverage>>flushCache and noticed that the current implementation TestCoverage>>flushCache self reference methodSymbol flushCache performs not that well: The set of not covered methods is wrong and many tests suddenly fail. If I replace it with TestCoverage>>flushCache self reference actualClass flushCache I actually get accurate coverage information, but there are still a few tests constantly failing. I tried to use all possible combinations of #flushCache (also calling it on the compiled method), but only flushing the cache on the class seems to work properly. So far so good, but I really wonder what the correct way is to flush the cache? :-) For my experiments I was using the package 'AST-Tests-Semantics'. This is a small package with lots of test methods that cover each method but one (RBSemanticAnnotationMisssing>>#isResumable). Now the "real" problem is that when running these tests in coverage mode, the same 4 tests always fail: RBSemanticTest>>testBlockScope RBSemanticTest>>testCascadeReceiver RBSemanticTest>>testClassVariableBinding RBSemanticTest>>testGlobalVariableBinding Not sure of how to debug that? Do you have an idea why these otherwise passing tests suddenly fail? If you want to try to reproduce you can use any Pharo image with the tests loaded, or use those that I used: http://jenkins.lukas-renggli.ch/job/Development/lastSuccessfulBuild/artifac… http://jenkins.lukas-renggli.ch/job/Development/lastSuccessfulBuild/artifac… Open the Test Runner, select 'AST-Tests-Semantics' and 'Run Coverage'. Any help or clarification would be appreciated :-) Lukas -- Lukas Renggli www.lukas-renggli.ch

July 1, 2011

Re: [Pharo-project] Please test Pharo 1.3!

by StÃ©phane Ducasse

> > > Dont know about the state of completion these days ... but it > would be nice if this would just be an option one sets on the editor. yes but if nobody looks it will not happen :)

July 1, 2011

Re: [Pharo-project] 1.3 profiler - nice stuff!

by Mariano Martinez Peck

On Fri, Jul 1, 2011 at 12:34 AM, Schwab,Wilhelm K <bschwab(a)anest.ufl.edu>wrote: > Recent mention of the profiler prodded me to take a look at the profiler in > 1.3. Very nice! Some "quick" changes that I think would be good: > > (1) Shout in the code pane; > (2) Use tabs to show the gc data or the code; > (3) Add a tab to show the result rather than using a modal notifier (which > probably quickly gets dismissed, and then missed<g>). > > Yes, that would be nice. Open a ticket :) > A non-quick change, if it's even possible... Some of the slickest Dolphin > goodies in existence include: Ian Bartholomew's ChunkBrowser (Pharo's lost > changes is close and useful, but not the same) and Profiler, the > SUnitBrowser (nicer than the SUnit test runner), and Ghoul. > > Ghoul is well named. It presents Dolphin crash dumps in a debugger-like > view: > > http://metagnostic.org/DolphinSmalltalk/Ghoul.html > > If there is, or could/should be enough data in a profile to do the same > thing, it would make an interesting addition. Then interacting with the > code includes the ability to see the values of variables. > > Bill > > -- Mariano http://marianopeck.wordpress.com

July 1, 2011

Re: [Pharo-project] Please test Pharo 1.3!

by Torsten Bergmann

> > > > - Script Manager is broken: adding a script produces an error > > > > Torsten, can you take a look? When I downloaded a fresh Pharo-dev 1.3 from Hudson this morning I was not able to reproduce this. ScriptManager worked without a problem. The only problem I noticed was that there was no styling (which is fixed by replacing MorphicTextEditor with PluggableTextMorph in a new "ScriptManager-Core-tbn.13"). Feel free to integrate this version. It would also nice if ScriptManager would support autocompletion but I got lost in all these completionController stuff... If anyone knows how to apply it feel free to have a look. Dont know about the state of completion these days ... but it would be nice if this would just be an option one sets on the editor. Bye T. -- NEU: FreePhone - kostenlos mobil telefonieren! Jetzt informieren: http://www.gmx.net/de/go/freephone

July 1, 2011

[Pharo-project] [update 1.4] #14022

by Marcus Denker

14022 ----- Issue 4475: Senders button of finder tool DNU browseSendersOf: http://code.google.com/p/pharo/issues/detail?id=4475 Issue 4457: Polymorph-ToolBuilder package need to be removed http://code.google.com/p/pharo/issues/detail?id=4457 (package not yet removed, just cleanup) -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

July 1, 2011

[Pharo-project] [update 1.3] #13281

by Marcus Denker

13281 ----- Issue 4475: Senders button of finder tool DNU browseSendersOf: http://code.google.com/p/pharo/issues/detail?id=4475 Issue 4473: About HTTP proxies, settings and MacOS http://code.google.com/p/pharo/issues/detail?id=4473 -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

July 1, 2011

Re: [Pharo-project] TWM and shortcuts

by Fernando Olivero

For the icons, you can use the external icon family importer i did Gofer it squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfExternalIconFamily'; load. (Smalltalk globals classNamed: 'ConfigurationOfExternalIconFamily') perform: #load. The attached file has a subset of Oxygen already imported. | file | file := FileDirectory default fileNamed: 'ExternalIconFamilyOxygen.st'. file fileIn. You can sample them evaluating: 'ExternalIconFamilyOxygen openAllIcons'. To learn more look at 'http://www.squeaksource.com/ExternalIconFamily'. I plan to eventually integrate nicer icons into Pharo1.4 using this toolset. As an example of how to use them, take a look at the new TranscriptMorph's in Pharo1.4. Till a the external icon toolset is integrated, i'm just copying and pasting the icon's contents, clearly a better solution is needed. Fernando On Wed, Jun 29, 2011 at 11:08 PM, laurent laffont <laurent.laffont(a)gmail.com> wrote: > Now in TWM > - shortcuts work with multiple world > - you can event switch to next world with Meta w, Meta w > May be someone has nice icons for the bar ? > > How I load my Pharo "desktop" in last 1.3 : > Gofer it > squeaksource: 'TilingWindowManager'; > package: 'ConfigurationOfTilingWindowManager'; > load. > > (Smalltalk at:#ConfigurationOfTilingWindowManager) loadDevelopment. > (ConfigurationOfAutotest project version: #development) load. > > (Smalltalk at:#TWMUITheme) beCurrent. > TaskbarMorph showTaskbar: false. > TasklistMorph keepOpen: true. > (Smalltalk at:#TWMBar) perform:#showTWMBar: with:true. > AutotestDashboard showAutotestDashboard: true. > Cheers, > Laurent Laffont -Â @lolgzs > > Pharo Smalltalk Screencasts: http://www.pharocasts.com/ > Blog: http://magaloma.blogspot.com/ > Developer group: http://cara74.seasidehosting.st >

July 1, 2011

Re: [Pharo-project] little challenge for sven and us

by StÃ©phane Ducasse

> Indeed. Actually the recent JS popular libraries coding style reminds > me more and more smalltalk. > Looks like they are inventing new wheel, going long road from creepy C > syntax and C programming style > to smalltalk. The problem igor is that they will get there and fast because the world is faster. Microsoft is creating a new lab at Zurich for example. And our nice little community did not move since at least one decade. Sometimes I'm immensely sad to see for example that while julian is working for cincom he does not lead an effort to bring Seaside to the next level. Company vision are puzzling me. Stef

July 1, 2011

Re: [Pharo-project] little challenge for sven and us

by StÃ©phane Ducasse

Yes I know. Now still we are bad at communication and at marketing what we have. Our community as a whole lacked a vision for so long .... We are trying but it is slow Stef On Jun 30, 2011, at 6:01 PM, Olivier Auverlot wrote: > Hi Stef, > > I don't think that the buzz around NodeJS comes from these samples of code. Yes, it's very easy to starting a project with NodeJS but the interest from NodeJS is that this server extends the usages of Javascript wich becomes an language useable on many platform, many OS for many usages. With Javascript, programmers can write client code in browsers, widgets for desktop computers, shell scripts with Rhino, mobile applications for Android or IOS, ... and now, programmers can write server code for web applications and web services. > > My two cents > > Olivier ;-) > www.auverlot.fr >> Hi guys >> >> apparently people get excited by nodeJS and I would like to know the equivalence of >> >> var http = require('http'); >> http.createServer(function (req, res) { >> res.writeHead(200, {'Content-Type': 'text/plain'}); >> res .end('Hello World\n'); >> }).listen(1337, "127.0.0.1"); >> >> console.log('Server running at >> http://127.0.0.1:1337/ >> '); >> To run the server, put the code into a file example.js and execute it with the node program: >> >> % node example.js >> Server running at >> http://127.0.0.1:1337/ >> >> >> >> Here is an example of a simple TCP server which listens on port 1337 and echoes whatever you send it: >> >> var net = require('net'); >> var server = net.createServer(function (socket) { >> socket.write("Echo server\r\n"); >> socket.pipe(socket); >> }); >> >> server.listen(1337, "127.0.0.1"); >> >> >> we should communicate better :) >> >> Stef >> > >

July 1, 2011

[Pharo-project] 1.3 profiler - nice stuff!

by Schwab,Wilhelm K

Recent mention of the profiler prodded me to take a look at the profiler in 1.3. Very nice! Some "quick" changes that I think would be good: (1) Shout in the code pane; (2) Use tabs to show the gc data or the code; (3) Add a tab to show the result rather than using a modal notifier (which probably quickly gets dismissed, and then missed<g>). A non-quick change, if it's even possible... Some of the slickest Dolphin goodies in existence include: Ian Bartholomew's ChunkBrowser (Pharo's lost changes is close and useful, but not the same) and Profiler, the SUnitBrowser (nicer than the SUnit test runner), and Ghoul. Ghoul is well named. It presents Dolphin crash dumps in a debugger-like view: http://metagnostic.org/DolphinSmalltalk/Ghoul.html If there is, or could/should be enough data in a profile to do the same thing, it would make an interesting addition. Then interacting with the code includes the ability to see the values of variables. Bill

June 30, 2011