July 2010 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] CogVM as official Pharo VM?

by Serge Stinckwich

2010/7/29 Mariano Martinez Peck <marianopeck(a)gmail.com>: > Hi folks. Hope Eliot is reading this thread. > > It is time to think in Pharo 1.2 and we need to discuss if we want to have > CogVM as the standard Pharo VM. Thank you Mariano this important issue for the future of Pharo. > Most of us have tried it and found it incredible fast. So it would be very > good to take advantage of it.Â But I think there are a couple of things to > be discussed: > > 1) Cog VM seems to be aimed for x86 and 32 bits. You can read Eliot quotes: > "The Cog VM is a just-in-time compiler that currently supports only x86 > > No effort has been made to maintain 64-bit compatibility.Â Apologies, this > was unaffordable." > > So...how much important is this for us? do we care? and if we want to do it, > is it "doable" ?Â is it less doable than the normal squeak VM ? > > I really would like to have 64bits VM + 64bits images in a near future...but > hat's just my thoguhts. > > 2) The status of the external plugins. Are they working with Cog ?Â Not only > the "core plugings" but FFI, OSProcess (I read some problems with it), > TrueType, etc... > > 3) Is it stable for production use?Â For example, I read that with seaside > there are some crashes. For crashed related to socket, i know that Noury and Luc are working on a new implementation of sockets, so maybe if it is ready it could be included in 1.2 version. > 4) Depends on heroes. I never liked this idea. It has nothing to do with > Eliot. He is very cool and helpful. But I wonder, do we understand the new > VM and the changes? are we able to handle and fix it even without eliot ? > > 5) Integration to VMMaker. I saw that they started to merge cog (actually, I > think only stack vm?) to the trunk of VMMaker. This is really good news. I > hope everything is there and merged. > > 6) Binaries. It seems the official released didn't come with binaries. So we > should compile it for each OS. I think both binaries should be provided for 1.2 and also OneClick images with standard and Cog VM, in order to maximize the number of tests for the new VM. If we really want to push this, someone should take care of all of this. Regards, -- Serge Stinckwich UMI UMMISCO 209 (IRD/UPMC), Hanoi, Vietnam Every DSL ends up being Smalltalk http://doesnotunderstand.org/

July 30, 2010

[Pharo-project] [ANN] Magma 1.1r2

by Chris Muller

I am pleased to announce a new release of Magma containing my updates since 1.1r1: - All underscore assignments have now been updated to ANSI assignments. - When opening the server, a file called "_open" is created in the repository directory, to indicate the repository is open. The file is deleted when the repository is closed gracefully. This is intended to help protect from accidentally letting two OS processes open the same repository files. - Resurrected MagmaDictionary! It is just like a Dictionary except that it inherits the properties of Magma's LargeCollections, such as size and concurrency. - Added Collection>>#asMagmaArray and MagmaArray>>#add:. - Added check for an additional way to run Squeak in headless mode: the "-vm-display-null" option. - Added MagmaSessionRequest class>>#signalNewReadStrategy: so that domains may signal new ReadStrategies to any listening sessions. - Added MagmaLocalLocation>>#findSession, a convenient counterpart to #newSession that first checks there is already a session open on that location and, if so, use that one. Otherwise, create and answer a new one. - Support for persistent, simple BlockClosures (e.g., with only references to arguments, not "self", any instVars or globals). - Choose automatically between an appropriate MaDictionary subclass, depending on whether the new Weak-Finalization mechanism from Igor is supported. - Several other minor fixes. The following represent the 1.1r2 configuration, in load-dependent order: "Magma client" { 'Collections-BTree-lr.73.mcz'. 'Ma exception handling-cmm.36.mcz'. 'Ma base additions-cmm.174.mcz'. 'MaFixedWidthReport-cmm.7.mcz'. 'Ma Statistics-cmm.24.mcz'. 'Ma files additions-cmm.13.mcz'. 'Ma contextual search-cmm.34.mcz'. 'Ma special collections-cmm.114.mcz'. 'WriteBarrier-cmm.28.mcz'. 'Ma Squeak domain-cmm.34.mcz'. 'Ma proxy support-cmm.42.mcz'. 'Ma traverse object graphs-cmm.31.mcz'. 'Ma object serialization-cmm.234.mcz'. 'Ma client server-cmm.215.mcz'. 'Magma client-cmm.490.mcz' } "for Magma server add" , {'Magma server-cmm.406.mcz'. } "for Magma tester add" , { 'Ma Armored Code-cmm.148.mcz'. 'Ma special collections tester-cmm.14.mcz'. 'Ma object serialization tester-cmm.32.mcz'. 'Magma tester-cmm.367.mcz' } These package versions are available in the "MagmaTester" project of squeaksource.com. - Chris

July 29, 2010

[Pharo-project] Pharo 1.1 host menu os x

by Michael Roberts

I gave the latest release a spin and it seams quit doesn't work (again). old reference -> http://code.google.com/p/pharo/issues/detail?id=1068 can someone confirm? if so do we want a new issue or reopen the old one? Also the host menu is not consistent with the world menu. for example the tools menu is different. Script manager is in one but not the other. The help browser text references it which is why i noticed. I haven't looked at the implementation. is there a way they are supposed to be kept in sync? cheers, Mike

July 29, 2010

Re: [Pharo-project] Extending SUnit [was Re: Autotest, proof-of-concept [was: About TDD and Pharo]]

by Alexandre Bergel

> Maybe it's just me, or could we not add Announcement to the end of every Announcement subclass name though? > Like with the window announcement, I like them better as verbs describing the event, f.ex. > someAnnouncer on: TestStarted do: [] > someAnnouncer on: TestEnded send: #x to: y Someone else vote for this? Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

July 29, 2010

Re: [Pharo-project] [Survey] Assess the cycles in your software

by Laval Jannik

Hi all, Just a small reminder for people who wants to participate. Thank you for your collaboration. Cheers, Jannik On Jul 19, 2010, at 08:36 , Laval Jannik wrote: > Hi Pharoers, and Smalltalkers in general, > > Have you seen waited to assess the cycles in your software? Now you can :) > > We request some of you to perform an experiment using DSM to see your software package structure and to fix cycles between packages. Our tool shows dependencies between packages and highlight some bad dependencies generating structure cycles. It also helps to understand dependencies. > > Your goal is to fill a survey using our tool. > I prepared a mini-tutorial about DSM and eDSM. It can help you to understand the visualization tool. > > To ease the use of our tool, I loaded it in a PharoCore1.2. And there are two archives available: > - the first contains an image with our tool with a model of Pharo loaded in it, so you can play with our tool on pharo itself. It can be downloaded here: http://dl.dropbox.com/u/7739334/dsmWithPharo.zip. Pay attention, the image is slow. > - the second contains the same thing without the model of Pharo. Here, you have to load your code, then populate a moose model and use the tool. It can be downloaded here: http://dl.dropbox.com/u/7739334/dsmWithoutPharo.zip > The two archives contain the tutorial and the survey. If you are a pharo integrator, we suggest you to take the one with Pharo model loaded, else the other. > > To use our tool, load your tool in Pharo. Then do "MoosePanel open", and import your software in Moose by "import from Smalltalk image". When it is imported, select your project in the list on the left of MoosePanel, and select "all model packages" on the list on center. > > Then, you have two choices: > - you can scan all your project: right click on "all model packages" and do DSM. > - or select "all model packages" then select some packages in the next list and right click, do DSM. > > After that, you can perform the survey (with reading of the tutorial). We need your answers for the end of August. So, you have two months to do it. > > If you have any question, just let me know. > > Best regards, > Jannik. > > --- > Jannik Laval > PhD Student - Rmod Team - INRIA > Certified Project Management Associate (IPMA) > http://www.jannik-laval.eu > http://rmod.lille.inria.fr > --- >

July 29, 2010

Re: [Pharo-project] Extending SUnit [was Re: Autotest, proof-of-concept [was: About TDD and Pharo]]

by laurent laffont

On Thu, Jul 29, 2010 at 7:42 PM, Henrik Sperre Johansen < henrik.s.johansen(a)veloxit.no> wrote: > On 29.07.2010 17:45, Alexandre Bergel wrote: > >> Wow ! Fast !. >>> >>> That means it should be easy now to do a lot of exciting stuff. Show >>> tests progression, errors/failures as soon as they occur, log several >>> things, drink cocktails, meet beautiful girls ....that's really cool. >>> >> I will be in winter time in 1 week time. We have to enjoy now >> >> Alexandre >> > Nice! > Maybe it's just me, or could we not add Announcement to the end of every > Announcement subclass name though? > Like with the window announcement, I like them better as verbs describing > the event, f.ex. > someAnnouncer on: TestStarted do: [] > someAnnouncer on: TestEnded send: #x to: y > +1. I propose TestCaseAnnouncement -- TestCaseStarted -- TestCaseEnded Shouldn't we put announce in TestResult>>runCase: instead of TestCase>>runCase ? This way we can pass the result to the Annoucement object. Actually, self announce: SUTestEndAnnouncement. is not in the ensure: block. So if the test fails there's no annoucement sent. Cheers, Laurent > > Cheers, > Henry > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

July 29, 2010

[Pharo-project] [update 1.2] #12070

by Marcus Denker

12070 ----- Issue 2723: TestRunner UI does not provide fly by help for buttons Issue 2724: Window button fly by help should start with uppercase Issue 2725: Debugger context menu items do not start with uppercase letter Issue 2726: Fly by help of debugger buttons should start with uppercase -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

July 29, 2010

Re: [Pharo-project] there are still references to PluggableButtonMorphPlus

by Marcus Denker

On Jul 29, 2010, at 7:35 PM, Mariano Martinez Peck wrote: > I am in PharoCore 12066 and there are still references to PluggableButtonMorphPlus, which doesn't exist anymore: > > As much as I understand what Stef did with Gary is to start to merge all those many many button classes into one. They removed all the *Plus ones, for example. The standard Pluggable one can now do what the Plus did. > 1) MorphicToolBuilder >> buttonClass > ^ PluggableButtonMorphPlus > > is it ok to change it to > > buttonClass > ^ PluggableButtonMorph > > ? > yes, did that. > 2) UITheme >> newButtonIn: aThemedMorph for: aModel getState: stateSel action: actionSel arguments: args getEnabled: enabledSel getLabel: labelSel help: helpText > > > |b| > b := PluggableButtonMorphPlus > on: aModel > getState: stateSel > action: actionSel > label: labelSel. > > .... > > is it ok to change it to > > |b| > b := PluggableButtonMorph > on: aModel > getState: stateSel > action: actionSel > label: labelSel. > > ? > I did that. > > 3) MorphicToolBuilderTests >> expectedFailures > "Polymorph override of PluggableButtonMorphPlus>>update: makes color not being updated anymore in respond to sending #changed:. Was this an intentional change and this test is obsolete?" > ^ #(testGetButtonColor) > > > I don't know how this one should be. But it should be updated, at least the class name. > Yes, the classname should be fixed. -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

July 29, 2010

Re: [Pharo-project] PluggableThemedOverflowPanelMorph(Object)>>doesNotUnderstand: #statusColor

by Marcus Denker

On Jul 29, 2010, at 7:38 PM, Mariano Martinez Peck wrote: > ok...as martin said, recompiling (change and save) PluggableButtonMorph>>#update: > did the trick...weird. Now we need to include this fix ASAP in the stream.. > I did: -> fix all refrences to PluggableButtonPlus (and all other Undeclared) -> recompile the image. Works. > cheers > > mariano > > On Thu, Jul 29, 2010 at 7:23 PM, Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: > We need help to solve this problem....I cannot do anything as I need the TestRunner. > > WE have http://code.google.com/p/pharo/issues/detail?id=2717 > > and http://code.google.com/p/pharo/issues/detail?id=2700 > > I tried a Compiler recompileAll but still have the same problem. > > Cheers > > Mariano > > > On Mon, Jul 26, 2010 at 11:02 PM, Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: > Just try open a TestRunner. You will get a DNU and that won't let you even debug the error. > > Pharo core version: PharoCore-1.2-12061 > > I attach PharoDebug.log > PluggableThemedOverflowPanelMorph(Object)>>doesNotUnderstand: #statusColor > > Issue: http://code.google.com/p/pharo/issues/detail?id=2717 > > Cheers > > Mariano > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

July 29, 2010

[Pharo-project] [update 1.2] #12069

by Marcus Denker

12069 ----- Issue 1699: A File out of existing code aborts when canceled Issue 2722: Fix some Undeclared References in 12068 Issue 2700: Bug opening TestRunner in 12062 and 12061 -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

July 29, 2010