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

Re: [Pharo-project] Complex number support discussion

by csrabak＠bol.com.br

Aug. 16, 2009

Re: [Pharo-project] Complex number support discussion

by csrabak＠bol.com.br

Aug. 16, 2009

Re: [Pharo-project] [update] 10414

by Adrian Lienhard

I get 6.8MB ;) Cool! Are there any other known classes with methods that use that much memory and are not essential? I wonder how much we could save if methods with the source of bitmaps (like #warningIconContents) would be removed or saved in the changes/ sources files (would be possible if stored as comments). Cheers, Adrian On Aug 16, 2009, at 04:27 , Marcus Denker wrote: > > On 13.08.2009, at 16:26, Adrian Lienhard wrote: > >> update #10414 >> ----------------- >> 310+311: Reorganize unit tests in a more modular way such that they >> can be unloaded >> >> Now all unit tests are in the packages "Tests", "CollectionsTests", >> "KernelTests", "MorphicTests", etc. The key point of this >> reorganization is to make these packages really modular, i.e., they >> can be unloaded without leaving obsolete classes behind. I also made >> sure that SUnit with its GUI is unloadable. >> >> If you execute in a Pharo-core image: >> >> ScriptLoader new cleanUpForProduction; cleanUpForRelease >> >> you get an image without tests and SUnit that is 8.0 MB on disk. >> > > And after deleting the ScriptLoader class, it's only 6.9 MB. > > Marcus > > > -- > Marcus Denker - http://marcusdenker.de > PLEIAD Lab - Computer Science Department (DCC) - University of Chile > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Aug. 16, 2009

[Pharo-project] Fwd: Class browser with changing title.

by StÃ©phane Ducasse

Begin forwarded message: > From: Colin Putney <cputney(a)wiresong.ca> > Date: August 16, 2009 7:15:26 PM CEDT > To: StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > Subject: Re: [Pharo-project] Class browser with changing title. > > > On 16-Aug-09, at 9:17 AM, StÃ©phane Ducasse wrote: > >> Ah ok then the fix should be sent to omnibrowse mailing-list >> >> I do not know what is the process colin is following for enh >> inclusion >> >> <ClassBrowserchange.1.cs> > > Hi StÃ©phane, > > Casual contributions like Henrik's should be posted to the OB > mailing list. For larger contributions, I'll invite the developer to > commit directly to my wiresong repository, with discussion on the > mailing list. > > I'm a little puzzled by this change set, though. OB already updates > the window title when the selection is changed... is this behavior > broken on Pharo? > > Colin

Aug. 16, 2009

Re: [Pharo-project] Analog to Dolphin's #forkMainIfMain?

by StÃ©phane Ducasse

On Aug 16, 2009, at 12:07 PM, Igor Stasenko wrote: > 2009/8/16 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: >> Bill (and igor) >> >> I would love to continue to remove Project from the image so the >> "spawnProcessIfThisIsUI:self activeProcess." >> should probably find another host. Do you have an idea about the >> class >> that could be the natural place to define >> such a method? >> if so can you propose a change? >> > > IMO WorldState is the way to go. > Since you removing Project, then you couldn't have multiple worlds, > right? yes projects are totally broken in pharo. > >> Stef >> >> >> On Aug 16, 2009, at 5:57 AM, Schwab,Wilhelm K wrote: >> >>> Sig, all, >>> >>> I have been preparing MC packages with classes and method designed >>> to soften the blow of moving much of my domain code to Pharo. In >>> this case, I have some sends of ProcessorSchedler>>forkMainIfMain, >>> so I created that method. Initially, I made it emtpy, and then >>> based on what you helpe me find, I tried >>> >>> ProcessorScheduler>>forkMainIfMain >>> Project spawnProcessIfThisIsUI:self activeProcess. >>> >>> >>> The above gets called from something that then immediately waits on >>> a semaphore that is signalled by one of two threads. One of the >>> threads waits on a timer, the other tries to evaluate a block; >>> creating a background worker thread that will run for a limited >>> time. There is a test case that tries various combinations, some of >>> which should succeed and some should time out. I have used these >>> things in production in Dolphin for some time. >>> >>> In Dolphin, #forkMainIfMain allows the UI to be responsive during >>> these tests, but trying the above in Pharo turns ugly. There are >>> problems that appear to related to two UI processes - running short >>> of events or something like that. The tests run for only a few >>> seconds, though I suppose I could try to allow enough time to look >>> around, but then I'm probably not the right person to do the looking >>> anyway. >>> >>> DUMB question: the argument to #spawnProcessIfThisIsUI: is named >>> suspendedProcess. Do I need to ensure the process in question is >>> indeed suspended before entering the method? If so, then I start >>> wondering how to get there from #forkMainIfMain, but it's a little >>> late for my brain to take on that question. >>> >>> One thing is certain: what I tried did not work. There were errors >>> from the event loop and even some screen scarring. >>> >>> Bill >>> >>> >>> -----Original Message----- >>> From: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr >>> ] On Behalf Of Igor Stasenko >>> Sent: Saturday, August 15, 2009 3:29 PM >>> To: Pharo-project(a)lists.gforge.inria.fr >>> Subject: Re: [Pharo-project] Analog to Dolphin's #forkMainIfMain? >>> >>> 2009/8/15 Schwab,Wilhelm K <bschwab(a)anest.ufl.edu>: >>>> Is there anything in Pharo that starts a new main thread to carry >>>> on for one that is about to get blocked? It might be that Pharo >>>> does not need it, since sockets are serviced by the VM, where >>>> Dolphin (at least prior to overlapped calls) did the I/O through >>>> the event loop; if the main thread stopped, so did Windows event >>>> dispatching, and hence no socket I/O. >>>> >>> There is such thing. >>> Try to explore the way how debugger handling this (when process you >>> want to debug is current UI process), or when you pressing interrupt >>> key. >>> >>> See Debugger>>openOn: process context: context label: title >>> contents: >>> contentsStringOrNil fullView: bool >>> >>> at 'Project spawnNewProcessIfThisIsUI: process' >>> >>> >>> >>>> Dolphin to some extent, and WindowBuilder to (IIRC) a large extent >>>> create modal loops in Smalltalk code. I see a few references to >>>> such things in Pharo, but I'm fairly lost. Where should I start >>>> reading and/or browsing? >>>> >>>> Bill >>>> >>>> >>>> >>>> >>>> _______________________________________________ >>>> Pharo-project mailing list >>>> Pharo-project(a)lists.gforge.inria.fr >>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>>> >>> >>> >>> >>> -- >>> Best regards, >>> Igor Stasenko AKA sig. >>> >>> _______________________________________________ >>> 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 >> > > > > -- > Best regards, > Igor Stasenko AKA sig. > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Aug. 16, 2009

Re: [Pharo-project] Class browser with changing title.

by StÃ©phane Ducasse

Ah ok then the fix should be sent to omnibrowse mailing-list I do not know what is the process colin is following for enh inclusion On Aug 16, 2009, at 12:04 PM, Henrik Sperre Johansen wrote: > This change was for the OB-browsers. > IMHO, I'd be nice to have the same functionality in (the thing > previously known as) Pharo-core too, though :) > > Cheers, > Henry > > On 16.08.2009 11:02, StÃ©phane Ducasse wrote: >> Hi javier >> >> did you sign the license agreement? and send it to me :)? >> Then open an entry in the bug tracker and add you changes there. >> >> >> Stef >> >> On Aug 15, 2009, at 2:28 AM, Javier PimÃ¡s wrote: >> >> >>> Thanks everybody for the answers of last post. Finally I used the >>> technique Mariano recommended because it was just what I wanted. >>> >>> Here I'm proposing a really small change to the class browser so >>> that whenever a class or method is selected it's title is changed >>> accordingly. The title produced is such that you can distinguish the >>> browsers when looking at the taskbar (very usefull when you have >>> many browsers opened). In case you like it, it would be nice to have >>> it included in main pharo. >>> >>> -- >>> Javier PimÃ¡s >>> Ciudad de Buenos Aires >>> <ClassBrowserchange. >>> 1.cs>_______________________________________________ >>> 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

Aug. 16, 2009

Re: [Pharo-project] Beta: browser missing splitters?

by Lukas Renggli

2009/8/16 Damien Cassou <damien.cassou(a)gmail.com>: > This seems related to Seaside and not to Pharo. Could you please repost there? No, this is clearly not related to Seaside, but to OB and Pharo. >> One thing that stands out to me is that the panes in the browser appear to lack splitters, so one is stuck with their relative sizes :( That's an OB issue. It has been discussed on the OB list several times. Unfortunately the problem cannot be easily solved, as when the selection changes the navigation columns to the right get recreated. >> As a secondary item, when trying to click-drag where a splitter might be, it picks up the entire browser; IMHO, it should ignore the input. Â Better still, it should have splitters. That's a Morphic issue. Morphic starts to drag the owning window if the window background or a containing morph without drag/click action is pressed. Cheers, Lukas -- Lukas Renggli http://www.lukas-renggli.ch

Aug. 16, 2009

Re: [Pharo-project] Complex Number Discussion

by Schwab,Wilhelm K

Ken, Unit tests are only as good as their coverage. The danger is in the code that is not in your image. Bill -----Original Message----- From: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Ken.Dickey Sent: Sunday, August 16, 2009 9:28 AM To: pharo-project(a)lists.gforge.inria.fr Subject: Re: [Pharo-project] Complex Number Discussion HELP REQUEST I am working an old, very slow machine and must be missing something. I have browsed senders of #sqrt and run the full test suite with sqrt either answering a complex or giving an error on negative arguments and have not seen a difference. Can someone please send me a/some non-trivial examples of where returning complex results for negative arguments breaks something. Thanks a bunch, -KenD _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Aug. 16, 2009

Re: [Pharo-project] Analog to Dolphin's #forkMainIfMain?

by Igor Stasenko

2009/8/16 Schwab,Wilhelm K <bschwab(a)anest.ufl.edu>: > Sig, > > Two UI processes polling for input is probably what has happened. Â I should give some attention to how Dolphin prevents that. Â Two things that come to mind are raising the priority of a new UI thread to create a modal event loop, and (which Pharo almost certainly does too) starting a new UI thread when needed. > > My TimedEvaluator class has headless and "with progres" subclasses. Â The latter will need some porting, and perhaps the headless one should simply block, or at least do so in Pharo. > > Terminating the UI thread seems a little harsh, but that might be what is needed. Sure it is what debugger does when you closing its window - it terminating the process you currently debugging. Nothing harsh or wrong and nothing to worry about (usually). :) >Another option might be to suspend the old UI thread, start the new one, and then undo the damage at the end. There are is a little damage which is done when you doing that - mainly the event which is currently handled is lost, but since your intent to terminate the current process, as a result of event handling, nothing wrong with it. As for the rest , when you start a new UI process everything continues to work normally. >Â Is that something that #forkMainIfMain should do automatically? Â One of the things that drives me nuts is whether a #suspend would stop the thread that is trying to do the work =:0 > There should be some process which polling the events from VM, even if they are not handled. The only case when its not needed at all is in headless mode. Otherwise , at least on windows, when VM internal event buffer overflows you start receiving warnings about it. > Bill > > > > -----Original Message----- > From: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Igor Stasenko > Sent: Sunday, August 16, 2009 5:05 AM > To: Pharo-project(a)lists.gforge.inria.fr > Subject: Re: [Pharo-project] Analog to Dolphin's #forkMainIfMain? > > 2009/8/16 Schwab,Wilhelm K <bschwab(a)anest.ufl.edu>: >> Sig, all, >> >> I have been preparing MC packages with classes and method designed to >> soften the blow of moving much of my domain code to Pharo. Â In this >> case, I have some sends of ProcessorSchedler>>forkMainIfMain, so I >> created that method. Â Initially, I made it emtpy, and then based on >> what you helpe me find, I tried >> >> ProcessorScheduler>>forkMainIfMain >> Â Project spawnProcessIfThisIsUI:self activeProcess. >> >> >> The above gets called from something that then immediately waits on a semaphore that is signalled by one of two threads. Â One of the threads waits on a timer, the other tries to evaluate a block; creating a background worker thread that will run for a limited time. Â There is a test case that tries various combinations, some of which should succeed and some should time out. Â I have used these things in production in Dolphin for some time. >> >> In Dolphin, #forkMainIfMain allows the UI to be responsive during these tests, but trying the above in Pharo turns ugly. Â There are problems that appear to related to two UI processes - running short of events or something like that. Â The tests run for only a few seconds, though I suppose I could try to allow enough time to look around, but then I'm probably not the right person to do the looking anyway. >> >> DUMB question: the argument to #spawnProcessIfThisIsUI: is named suspendedProcess. Â Do I need to ensure the process in question is indeed suspended before entering the method? Â If so, then I start wondering how to get there from #forkMainIfMain, but it's a little late for my brain to take on that question. >> >> One thing is certain: what I tried did not work. Â There were errors from the event loop and even some screen scarring. >> > > I think, once you spawn a new UI process by your code, you should prevent an old process from returning back to World/WorldState event handling, by simply terminating it after you done. > Otherwise, again, take a look what debugger does, when you clicking 'proceed' on a process which being debugged and which was a UI process. It should do some tricks, otherwise you end up with two event loops polling the same event source. > >> Bill >> >> >> -----Original Message----- >> From: pharo-project-bounces(a)lists.gforge.inria.fr >> [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Igor >> Stasenko >> Sent: Saturday, August 15, 2009 3:29 PM >> To: Pharo-project(a)lists.gforge.inria.fr >> Subject: Re: [Pharo-project] Analog to Dolphin's #forkMainIfMain? >> >> 2009/8/15 Schwab,Wilhelm K <bschwab(a)anest.ufl.edu>: >>> Is there anything in Pharo that starts a new main thread to carry on for one that is about to get blocked? Â It might be that Pharo does not need it, since sockets are serviced by the VM, where Dolphin (at least prior to overlapped calls) did the I/O through the event loop; if the main thread stopped, so did Windows event dispatching, and hence no socket I/O. >>> >> There is such thing. >> Try to explore the way how debugger handling this (when process you want to debug is current UI process), or when you pressing interrupt key. >> >> See Debugger>>openOn: process context: context label: title contents: >> contentsStringOrNil fullView: bool >> >> at 'Project spawnNewProcessIfThisIsUI: process' >> >> >> >>> Dolphin to some extent, and WindowBuilder to (IIRC) a large extent create modal loops in Smalltalk code. Â I see a few references to such things in Pharo, but I'm fairly lost. Â Where should I start reading and/or browsing? >>> >>> Bill >>> >>> >>> >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>> >> >> >> >> -- >> Best regards, >> Igor Stasenko AKA sig. >> >> _______________________________________________ >> 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 >> > > > > -- > Best regards, > Igor Stasenko AKA sig. > > _______________________________________________ > 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 > -- Best regards, Igor Stasenko AKA sig.

Aug. 16, 2009

Re: [Pharo-project] Complex number support discussion

by Ken.Dickey

gor Stasenko <siguctua(a)gmail.com> > Let me restate where we started from. We started from point: > Array new: 0.2i Again, how is this different in pattern from dealing with Â Array new: 1/2 Â Array new: -17 Â ... ?? -KenD PS: Â Complex real: (0.5 + 0i) imaginary: (0 + 0i) Complex can only have instances of Number as components. Â The lack of checks is an error.

Aug. 16, 2009