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

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

by Eliot Miranda

2010/7/29 Mariano Martinez Peck <marianopeck(a)gmail.com> > Hi folks. Hope Eliot is reading this thread. > Yes, I'm reading :) > 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. > > 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 > It is only initially aimed at x86. That's the most important platform by far from Teleplace's perspective and I suspect the majority of the community is on x86. But Cog was designed form the outset to be portable. The Cogit is architected to support other ISAs. See CogAbstractInstruction and its one subclass CogIA32Compiler. To port to another ISA you should subclass CogAbstractInstruction and implement the same protocol as CogIA32Compiler. I would love to see a CogARMCompiler and a CogPPCCompiler and encourage anyone with low-level expertise on those platforms to have a go. I'm always here to answer questions. 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. > I'm also thinking abut 64-bits but want to do 64-bits with a new object representation based on my 64-bit objrep for VisualWorks, which would include SmallFloat. Realistically this is a year out, because the 32-bit version of the new objrep and the pinning GC need to be implemented before I'll be able to do a 64-bit VM. But it's an obvious and logical direction to go in. 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... > ReentrantFFIPlugin (a.k.a. src/plugins/SqueakFFIPrims/SqueakFFIPrims.c) should work. But people need to build and test. 3) Is it stable for production use? For example, I read that with seaside > there are some crashes. > Well, it is the production VM at Teleplace so at least for one context the answer is certainly yes. There must be something obviously broken with sockets (is it all platforms or only linux?) because we use sockets intensively at Teleplace and only see problems on a single customer's machine which looks to be to do with virus protection. I'm on holiday next week and am rather busy right now, but perhaps later in August I can work with Lukas to try and sort out the socket issues. 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 ? > THis is a serious issue. I need to be nagged to document the system on my blog. I mean to get to this (perhaps in September?). Alas a Smalltalk JIT is a complex beast, significantly more complex than the interpreter, and is not the easiest thing to understand or debug. So even if it is well documented it'll be more difficult to fix than the interpreter, but that's a price one has to pay for this kind of performance. > > 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. > Cog is a fork of VMMaker. We may be able to merge at some stage, and Cog's Slang should still work with the old Interpreter. But for now, inevitably, it's a fork. I needed to add a lot of functionality to Slang to write Cog, and I didn't have the cycles to keep Interpreter up to date. That's life :) 6) Binaries. It seems the official released didn't come with binaries. So we > should compile it for each OS. > There is /no/ official release. Until Cog has stabilized and the VM maintainers have taken it up it's definitely unoffficial :) Ok..that's all my thoughts. I would really like to have a discussion here > and see what to do.....grrrrrr you are all in holidays, aren't you? hahah > two days to go :) > > cheers > > Mariano > best Eliot > > _______________________________________________ > 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

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

by Henrik Sperre Johansen

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 Cheers, Henry

July 29, 2010

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

by Mariano Martinez Peck

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

July 29, 2010

Re: [Pharo-project] Magma on 1.1 one click image

by Facundo Vozzi

Hi Ramiro, I don't think the image has to be sacred and untouched, we can remove 5 > lines from a workspace, it will be good for Pharo 1.1. > Or maybe, only for this version, add this line before that 5 lines: Scanner allowUnderscoreAsAssignment: true Aside from that minor detail, I am enormously happy and grateful to all for > this release. > Me too. > Cheers > regards, facundo > > > r > > _______________________________________________ > 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] there are still references to PluggableButtonMorphPlus

by Mariano Martinez Peck

I am in PharoCore 12066 and there are still references to PluggableButtonMorphPlus, which doesn't exist anymore: 1) MorphicToolBuilder >> buttonClass ^ PluggableButtonMorphPlus is it ok to change it to buttonClass ^ PluggableButtonMorph ? 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. ? 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. Thanks Mariano

July 29, 2010

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

by Mariano Martinez Peck

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 >

July 29, 2010

[Pharo-project] HTTP client library in Pharo?

by Andrei Stebakov

I've been trying to find a library for Pharo/Squeak which would handle GET/POST requests with the ability to manage cookies and deal with https servers. The HTTPSocket that's included in Pharo doesn't have cookies support. I tried to find any library that handles cookies and there came up CurlPlugin and SWHTTPClient. SWHTTPClient page has a broken link to the source code (http://map.squeak.org/package/15f42ec1-e93e-4bcf-ab2b-6746ae9d413f) CurlPlugin package for Win32 that I found on the main project page fails most of the tests and can't retrieve any http data. I also found WebClient/WebServer library at http://www.squeaksource.com/@QY3MLGU4hU3c8qcE/2xQek_iM which also fails most tests after installation. I wonder what people in smalltalk community are using when they need to do some web scraping when they need to keep some session in cookies? What would be the best library to invest time into (I am very new to Smalltalk)? Thank you, Andrei

July 29, 2010

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

by Alexandre Bergel

> 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 > > > > > On 29 Jul 2010, at 11:08, laurent laffont wrote: > > > > > Hi, > > > > > > Autotest use a wrapper to count hits on changed method. Take a look at Autotest>>#findRunAndShowTestsOf > > > > > > and replace: > > > > > > counter := AutotestHitCounter on: changedMethod. <- this wraps the method > > > [aTestResult := runner run: testMethods] > > > ensure: [counter uninstall]. > > > aTestResult hitCount: counter hitCount. > > > > > > by > > > > > > aTestResult := runner run: testMethods > > > > > > > > > to check that the problem is here. > > > > > > > > > I haven't tried Cog yet. Is it working out of the box ? > > > > > > > > > > > > Laurent > > > > > > > > > On Thu, Jul 29, 2010 at 10:48 AM, Tudor Girba <tudor.girba(a)gmail.com> wrote: > > > Ah, indeed! I forgot ... sorry for the noise :) > > > > > > Cheers, > > > Doru > > > > > > > > > > > > On 29 Jul 2010, at 10:45, Henrik Johansen wrote: > > > > > > On Jul 29, 2010, at 10:40 55AM, Tudor Girba wrote: > > > > > > Hi, > > > > > > It looks like Autotest is crashing on a Cog VM/image. Any ideas as to why that happen? > > > > > > Cheers, > > > Doru > > > > > > > > > If he went for using MethodWrappers as described below, it will crash on Cog, as it does not support objects as methods yet. > > > > > > Cheers, > > > Henry > > > > > > > > > > > > On 27 Jul 2010, at 10:11, Alexandre Bergel wrote: > > > > > > Indeed I also want to log for each test: > > > - min / max / mean execution time > > > - time to first failure > > > - % of errors/failures/success > > > - run count > > > > > > That would be cool > > > > > > so with these datas we know long tests. I think about wrapping run test methods with an object which then can collect these datas. Would you go this way ? > > > (Another way is to modify TestResult / TestCase, but it's more intrusive). > > > > > > Over the last few month I intensively used method wrapper (a.k.a object as compiled method). Time to time, the image just freezes or crashes. Maybe due to the garbage collector. Modifying SUnit should not be that complex. It would be nice to turn SUnit into something more extensible. One shoot two targets. > > > > > > > > > _______________________________________________ > > > Pharo-project mailing list > > > Pharo-project(a)lists.gforge.inria.fr > > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > > > -- > > > www.tudorgirba.com > > > > > > "One cannot do more than one can do." > > > > > > > > > > > > > > > > > > _______________________________________________ > > > Pharo-project mailing list > > > Pharo-project(a)lists.gforge.inria.fr > > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > > > _______________________________________________ > > > Pharo-project mailing list > > > Pharo-project(a)lists.gforge.inria.fr > > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > -- > > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > > Alexandre Bergel http://www.bergel.eu > > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > > > > > > > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

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 4:58 PM, Alexandre Bergel <alexandre(a)bergel.eu>wrote: > > Is Annoucements framework is synchronous or asynchronous ? If > synchronous, using Annoucements isn't less intrusive and more extensible ? > > :-) > synchronous. > http://code.google.com/p/pharo/issues/detail?id=2721 > SLICE-Issue-2721-AnnouncementsForSUnit-Alexandre_Bergel.1 in PharoInbox > > I quickly wrote this. I haven't used it yet. > 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. Laurent > > Cheers, > Alexandre > > > > > > On 29 Jul 2010, at 11:08, laurent laffont wrote: > > > > > Hi, > > > > > > Autotest use a wrapper to count hits on changed method. Take a look at > Autotest>>#findRunAndShowTestsOf > > > > > > and replace: > > > > > > counter := AutotestHitCounter on: changedMethod. <- this wraps > the method > > > [aTestResult := runner run: testMethods] > > > ensure: [counter uninstall]. > > > aTestResult hitCount: counter hitCount. > > > > > > by > > > > > > aTestResult := runner run: testMethods > > > > > > > > > to check that the problem is here. > > > > > > > > > I haven't tried Cog yet. Is it working out of the box ? > > > > > > > > > > > > Laurent > > > > > > > > > On Thu, Jul 29, 2010 at 10:48 AM, Tudor Girba <tudor.girba(a)gmail.com> > wrote: > > > Ah, indeed! I forgot ... sorry for the noise :) > > > > > > Cheers, > > > Doru > > > > > > > > > > > > On 29 Jul 2010, at 10:45, Henrik Johansen wrote: > > > > > > On Jul 29, 2010, at 10:40 55AM, Tudor Girba wrote: > > > > > > Hi, > > > > > > It looks like Autotest is crashing on a Cog VM/image. Any ideas as to > why that happen? > > > > > > Cheers, > > > Doru > > > > > > > > > If he went for using MethodWrappers as described below, it will crash > on Cog, as it does not support objects as methods yet. > > > > > > Cheers, > > > Henry > > > > > > > > > > > > On 27 Jul 2010, at 10:11, Alexandre Bergel wrote: > > > > > > Indeed I also want to log for each test: > > > - min / max / mean execution time > > > - time to first failure > > > - % of errors/failures/success > > > - run count > > > > > > That would be cool > > > > > > so with these datas we know long tests. I think about wrapping run test > methods with an object which then can collect these datas. Would you go this > way ? > > > (Another way is to modify TestResult / TestCase, but it's more > intrusive). > > > > > > Over the last few month I intensively used method wrapper (a.k.a object > as compiled method). Time to time, the image just freezes or crashes. Maybe > due to the garbage collector. Modifying SUnit should not be that complex. It > would be nice to turn SUnit into something more extensible. One shoot two > targets. > > > > > > > > > _______________________________________________ > > > Pharo-project mailing list > > > Pharo-project(a)lists.gforge.inria.fr > > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > > > -- > > > www.tudorgirba.com > > > > > > "One cannot do more than one can do." > > > > > > > > > > > > > > > > > > _______________________________________________ > > > Pharo-project mailing list > > > Pharo-project(a)lists.gforge.inria.fr > > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > > > _______________________________________________ > > > Pharo-project mailing list > > > Pharo-project(a)lists.gforge.inria.fr > > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > -- > > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > > Alexandre Bergel http://www.bergel.eu > > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > > > > > > > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > _______________________________________________ > 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

Re: [Pharo-project] Request for test

by Gary Chambers

Icon looks ok on Vista. App works nicely ;-) (English here, as it should be!) Regards, Gary ----- Original Message ----- From: Mariano Martinez Peck To: Pharo-project(a)lists.gforge.inria.fr Sent: Thursday, July 29, 2010 3:24 PM Subject: Re: [Pharo-project] Request for test same here. On Thu, Jul 29, 2010 at 3:42 PM, Max Leske <maxleske(a)gmail.com> wrote: mac os 10.6.4: Icon is grey with a blue triangle in it, app runs without problems. System language is english, app language was also english. Cheers, Max On 29.07.2010, at 15:38, Hilaire Fernandes wrote: > Dear all, > > I am preparing a DrGeo release. > > I will be very please if Windows and Mac user could test it for me please. > > I need to know if the application icon is looking like a triangle and if > DrGeo UI is in French for the French users. > > Here it is: http://people.ofset.org/hilaire/DrGeo.app.zip > > Thanks > > Hilaire > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ------------------------------------------------------------------------------ _______________________________________________ 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