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

Re: [Pharo-project] SmalltalkImage current reportCPUandRAM > DNU

by phil＠highoctane.be

Ah, I did 10004 already and did a clone in 10013.. sorry. Phil 2013/3/13 Marcus Denker <marcus.denker(a)inria.fr>: > > On Mar 12, 2013, at 10:42 AM, phil(a)highoctane.be wrote: > >> LogFullTally.txt cannot be produced. >> >> Weird that Smalltalk vm getParameters would give such a strange >> collection as shown in the left explorer. >> > > we fixed that already for #spyEvery:on:, the same needs to be done for the other > methods that have the same (duplicated?) code. > > Please add a issue tracker, else this will be lost. > >> Phil >> <Log-MemoryStats.txt><PharoScreenshot.png><Log-ProcessList.txt><Log-ThePig.txt> > >

March 13, 2013

Re: [Pharo-project] SmalltalkImage current reportCPUandRAM > DNU

by Marcus Denker

On Mar 12, 2013, at 10:42 AM, phil(a)highoctane.be wrote: > LogFullTally.txt cannot be produced. > > Weird that Smalltalk vm getParameters would give such a strange > collection as shown in the left explorer. > we fixed that already for #spyEvery:on:, the same needs to be done for the other methods that have the same (duplicated?) code. Please add a issue tracker, else this will be lost. > Phil > <Log-MemoryStats.txt><PharoScreenshot.png><Log-ProcessList.txt><Log-ThePig.txt>

March 13, 2013

Re: [Pharo-project] where to report vm crashes? (while running Moose tests)

by Igor Stasenko

On 12 March 2013 19:44, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: > > 3. Pharo has forked the VM to include a) NativeBoost and b) ephemerons and > c) new FileSystem primitives. > a) is cool, but I don't like the x86 specificity. I want a cross-platform > FFI, so I'm not excited enough to include NB in my port. Just let me remind you that (x86 specificity) is completely on image side. The VM side changes are minimal and 100% not platform specific. Making NB image-side implementation platform-unspecific is another story.. but as i said before i see no reason to do it unless there's a version of Cog which runs on some other platform :) There is plans and some work started on getting there, by making a platform-neutral low-level DSL, which can be used for generating native code. -- Best regards, Igor Stasenko.

March 13, 2013

Re: [Pharo-project] WhatsUp from: 2013-03-11 until: 2013-03-24

by Alexandre Bergel

> Hi! We're sending this automatic email twice a month, to give the community an opportunity to easily know what's happening and to coordinate efforts. Just answer informally, and feel free to spawn discussions thereafter! Cool idea! > ### Here's what I've been up to since the last WhatsUp: > > - $HEROIC_ACHIEVEMENTS_OR_DISMAL_FAILURES_OR_SIMPLE_BORING_NECESSARY_TASKS - Fixing many bugs in Roassal - Writing the chapter on Roassal - Working on the Loom thread profiler > ### What's next, until 2013-03-24 (*): > > - $NEXT_STEPS_TOWARDS_WORLD_DOMINATION - Reviewing the ZeroConf chapter - Working on the Rizel profiler Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

March 13, 2013

[Pharo-project] Debugger-driven development (was Re: WhatsUp from: 2013-03-11 until: 2013-03-24)

by Frank Shearar

On 12 March 2013 22:41, Stephan Eggermont <stephan(a)stack.nl> wrote: > ### Here's what I've been up to since the last WhatsUp: > - Accepted proposal to show debugger-driven TDD at Devnology meetup April 3 in Eindhoven (+Willem van den Ende) I'd love to hear more about your presentation. I've been thinking how to run a kind've live-coding demonstration at work, showing how a Smalltalk debugger is so clearly superior to what other folk have. (Squeak trunk now lets you create methods not just on an MNU but also where people have things like "self subclassResponsibility", "self notYetImplemented" or "self shouldBeImplemented" flags such that you can debug-edit-and-continue.) frank

March 12, 2013

Re: [Pharo-project] [Pharo-users] about communication and collaboration

by Norbert Hartl

that's great! Another missing piece of the infrastructure! Nobert Am 12.03.2013 um 16:02 schrieb StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: > Dear Pharoers > > last january I visited another lab and I realised that the Pharo Team was not good at systematically telling what we were doing. > I got quite frustrated by that situation, especially because we are working hard to build a better system. > So we brainstormed when I came back and we want to apply the same ideas that what we do for our research team. > > For our research team every monday we get a simple mail that tell us to say to the others what we did and what we > plan to do. Simple, easy. > Then after people of the rmod team can discuss if they want more. > > We want to do the same with pharo. > Often this is not that we are not doing things. Often we are doing boring, tedious stupid but $^%&&*^ important tasks and we want that you know it. > In addition we want to share on what we are weekly working. So that you can be more engaged to > join and collaborate with us. > > So we will launch an experience and see. For now we will send a notification every two weeks. > > the Pharo Team

March 12, 2013

Re: [Pharo-project] WhatsUp from: 2013-03-11 until: 2013-03-24

by Stephan Eggermont

### Here's what I've been up to since the last WhatsUp: - Added a storymap view to StoryBoard. Stories can now be added to a goal of a stakeholder. (+Diego Lont) - Accepted proposal to show debugger-driven TDD at Devnology meetup April 3 in Eindhoven (+Willem van den Ende) - Created proposal for a distributed issue tracker GSoC with Diego - Did a spike for a distributed issue tracker with Diego - Convinced Diego to go to Pharo & Moose Days and show TutorialBrowser & Data Conversion with MOOSE - Did a spike with a gherkin glamour browser, tried moving it to latest pharo/MOOSE/vm :) ### What's next, until 2013-03-24 (*): - publish distributed issue tracker spike - prepare presentations with Diego - parse gherkin files, visualize as roassal nested polymetric views Stephan

March 12, 2013

Re: [Pharo-project] Latest pharo issue with Eliot's latest Cog

by Tudor Girba

Hi Stephan, Thanks for your testing time :) Cheers, Doru On Mar 12, 2013, at 9:12 PM, Stephan Eggermont <stephan(a)stack.nl> wrote: > Esteban wrote: >> Pharo 2.0 does not work with Eliot builds (and it will not work in some scenarios). >> In this case, the main reason is that we rebuild (and use) FilePlugin and it is not >> incorporated in Eliot branch of the vm... so the FileDialogWindow will take years to open if opens at all. >> You need to use one of our VM builds (anyone from last 6 months to now should work) > > Ah, I didn't know the differences were already so that we need a Pharo-specific vm. > > nbcog-mac-latest.zip from 27-11-2012 doesn't crash. > 15883 run, 15493 passes, 2 skipped, 88 expected failures, 207 failures, 95 errors, 0 unexpected passes > > Would it be possible to have the vm warning more informative? Something like > "expected FilePlugIn, ..."? > > Stephan -- www.tudorgirba.com "It's not what we do that matters most, it's how we do it."

March 12, 2013

Re: [Pharo-project] access to pharoextras repository

by Tudor Girba

Great! Doru On Mar 12, 2013, at 10:14 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Hi doru > > I addressed your point in > XMLParser > XMLWriter > OPAX > Pastell > Soup > > and I will pay attention that default always load the tests too. > > Stef > -- www.tudorgirba.com "Every thing should have the right to be different."

March 12, 2013

Re: [Pharo-project] WhatsUp from: 2013-03-11 until: 2013-03-24

by Tudor Girba

Actually, I would love to get this mechanism also for Moose. Would it be possible? Cheers, Doru On Mar 12, 2013, at 10:15 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > > On Mar 12, 2013, at 9:04 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > >> Hi, >> >> First of all, I think this is a very cool initiative. > > > thanks > I really hope that it will improve our sharing and community building :) > > Stef > > >> >>> ### Here's what I've been up to since the last WhatsUp: >> >> - Working on getting Moose to work on Pharo 2.0 >> - Extended (and documented) the CommandLineHandler to run multiple tests based on context specific requirements >> - Attracted sponsors for PharoConf + MooseDay to make the event free to attend >> - Annoyed people with requests for giving talks and tutorial at PharoConf + MooseDay >> - Brainstormed and reviewed with Andrei around a very cool (really :)) and modular debugger model >> >>> ### What's next, until 2013-03-24 (*): >>> >>> - $NEXT_STEPS_TOWARDS_WORLD_DOMINATION >>> >>> (*) we'll be expecting results by then ;) >> >> - Find a solution for running Moose on a Pharo 2.0-compatible VM >> - Organize the PharoConf + MooseDay >> >> Cheers, >> Doru >> >> >> -- >> www.tudorgirba.com >> >> "Things happen when they happen, >> not when you talk about them happening." >> >> > > -- www.tudorgirba.com "In a world where everything is moving ever faster, one might have better chances to win by moving slower."

March 12, 2013