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

Re: [Pharo-project] vm-maker

by David T. Lewis

On Tue, Jun 09, 2009 at 05:56:38PM +0400, danil osipchuk wrote: > Hello squeak people > > Does anyone have a hint how to get (with reasonable effort) current > vmmaker setup? May be there is a prepared image somewhere? I'm > interested in building vm on windows. When I follow these > instructions: http://wiki.squeak.org/squeak/6102 i stuck during > loading of vmmaker from the squeak-map > > regards, > Danil Windows build instructions: http://squeakvm.org/win32/ http://squeakvm.org/cgi-bin/viewcvs.cgi/trunk/platforms/win32/docs/ Up to date VMMaker packages are on SqueakSource project VMMaker. The SqueakMap and Universes entries are a bit out of date. Dave

June 10, 2009

Re: [Pharo-project] new mailist?

by Serge Stinckwich

On Wed, Jun 10, 2009 at 6:08 AM, Jon Hancock<jhancock(a)shellshadow.com> wrote: > I have to unsubscribe. Â This list is too active. Â It clogs downloading > of my email. Â It would be wonderful if the list were run on something > with more options such as google groups. Â thanks guys. Â look forward > to pharo's continued growth. You can also follow the list on gmane: http://dir.gmane.org/gmane.comp.lang.smalltalk.pharo.devel Best regards, -- Serge Stinckwich UMI UMMISCO 209 (IRD/UPMC), Hanoi, Vietnam Smalltalkers do: [:it | All with: Class, (And love: it)] http://doesnotunderstand.org/

June 10, 2009

Re: [Pharo-project] Syntax error loading Coral

by David T. Lewis

On Tue, Jun 09, 2009 at 07:42:57PM +0200, St?phane Ducasse wrote: > luc > > > > "UnixProcess>>argsAsFlatArrayAndOffsets:". I guess it is an UTF-8 > > > problem. > > > Any ideas for a solution ? > > could you repost an email with a clear test showing that it breaks? > like that the UnixProcess father may answer :) > Stef A test would be great. I know only simple English, so anything more complex than 5-bit Baudot encoding may have bugs ;-) Note that UnixProcessAccessorTestCase>>testArgsAsFlatArrayAndOffsets is a test that documents how the method should behave. Dave

June 10, 2009

[Pharo-project] new mailist?

by Jon Hancock

I have to unsubscribe. This list is too active. It clogs downloading of my email. It would be wonderful if the list were run on something with more options such as google groups. thanks guys. look forward to pharo's continued growth. Jon

June 9, 2009

Re: [Pharo-project] [Seaside] Seaside 2.8.4 image crashes [newbie]

by Adrian Lienhard

Yes, this is a bug in the Unix VM. See the following issue, which describes a workaround: http://code.google.com/p/pharo/issues/detail?id=855 HTH, Adrian On Jun 9, 2009, at 23:46 , Lukas Renggli wrote: > This is certainly not your fault. It has probably to do with a > missing plugin. > > I'll forward it to the Pharo list, maybe somebody knows more about > this? I think I heard that problem before. > > Lukas > > On Tue, Jun 9, 2009 at 11:41 PM, Ivar > Refsdal<refsdal.ivar(a)gmail.com> wrote: >> Hello all, >> >> I'm a very fresh newbie, so the problem could just be myself. >> Apologies in advance >> if that is the case. However I'm getting a crash when doing the >> following after starting Seaside with ./seaside.sh: >> First going to http://localhost:8080/seaside/magritte/editor in a >> web browser, >> then clicking 'Add' and then 'Save' without entering any data. >> Then when clicking 'Preview' Seaside crashes with the following >> message: >> >> Segmentation fault >> >> 2022517340 UUID>initialize >> 2022517224 Behavior>new: >> 2022517132 >new >> 2022517040 >uuid >> 2022516948 >new >> 2022516856 >defaultAccessor >> 2022516764 MADescription>accessor >> 2022516672 MADescription>hash >> 2022516580 Dictionary>scanFor: >> 2022516488 Set>findElementOrNil: >> 2022516180 Dictionary>at:ifAbsent: >> 2022516088 MAAdaptiveModel>readUsing: >> 2022515996 MAMemento>pullRaw >> 2022515840 OrderedCollection>do: >> 2022515748 MAContainer>do: >> 2022515656 MAMemento>pullRaw >> 2022515564 MAMemento>pull >> 2022515452 MACachedMemento>reset >> 2022515360 MACheckedMemento>reset >> 2022515268 >model:description: >> 2022514976 MAContainer>asComponentOn: >> 2022514884 Object>asComponent >> 2022514792 MADescriptionEditor>preview >> 2022514700 WASubmitButtonTag>on:of: >> 2022514496 WAActionCallback>evaluateWithArgument: >> 2022514036 WACallback>evaluateWithField: >> 2022513760 WACallbackStream>processCallbacksWithOwner: >> 2022509456 WAPresenter>processCallbackStream: >> 2022509364 WAPresenter>processChildCallbacks: >> 2022509272 WAComponent>decorationChainDo: >> 2022509180 WAComponent>nextPresentersDo: >> 2022509060 WAComponent>childrenDo: >> 2022508968 SequenceableCollection>do: >> 2022508836 WAComponent>childrenDo: >> 2022508744 WAComponent>nextPresentersDo: >> 2022508652 WAPresenter>processChildCallbacks: >> 2022508560 WAPresenter>processCallbackStream: >> 2022508392 WAToolFrame>processCallbackStream: >> 2022508300 BlockClosure>on:do: >> 2022508196 WAToolFrame>withDeprecatedHandlerDo: >> 2022508104 WAToolFrame>processCallbackStream: >> 2022508012 WARenderContinuation>processCallbacks: >> 2022507884 WAComponent>decorationChainDo: >> 2022504988 WARenderContinuation>processCallbacks: >> 2022504896 WARenderContinuation>handleRequest: >> 2022504804 BlockClosure>on:do: >> 2022504712 WARenderContinuation>withNotificationHandler: >> 2022504328 WARenderContinuation>handleRequest: >> 2022501884 WASessionContinuation>value: >> 2022501164 WASession>performRequest: >> 2022501072 WASession>responseForRequest: >> 2022500980 BlockClosure>on:do: >> 2022500872 WASession>withErrorHandler: >> 2022499892 BlockClosure>on:do: >> 2022499800 WASession>withErrorHandler: >> 2022499708 WASession>responseForRequest: >> 2022499616 BlockClosure>on:do: >> 2022499500 >use:during: >> 2022499312 WASession>responseForRequest: >> 2022499220 WASession>withEscapeContinuation: >> 2022499128 >currentDo: >> 2022499016 WASession>withEscapeContinuation: >> 2022498904 WASession>responseForRequest: >> 2022498812 WASession>incomingRequest: >> 2022498548 BlockClosure>on:do: >> 2022498456 WAProcessMonitor>critical:ifError: >> 2022498364 BlockClosure>ensure: >> 2022498272 WAProcessMonitor>critical:ifError: >> 2022498640 BlockClosure>newProcess >> Aborted >> >> I'm using this image file (no changes made): >> http://www.seaside.st/distributions/Seaside-2.8.4.app.zip >> Otherwise I'm on Ubuntu 9.04 i386, nothing special. Let me know if I >> can provide more details. >> I also tried executing the cleanup commands in the workspace, but it >> didn't help. >> The crash does not occur with the previous image I tried: >> Seaside-2.8-578.app. >> >> Any suggestions? >> Thanks, >> >> Kind regards, >> Ivar Refsdal >> >> (First post, hope everything went well.) >> _______________________________________________ >> seaside mailing list >> seaside(a)lists.squeakfoundation.org >> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside >> > > > > -- > Lukas Renggli > http://www.lukas-renggli.ch > _______________________________________________ > seaside mailing list > seaside(a)lists.squeakfoundation.org > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

June 9, 2009

Re: [Pharo-project] [Seaside] Seaside 2.8.4 image crashes [newbie]

by Schwab,Wilhelm K

On Ubuntu 9.04, find the UUIDPlugin folder and rename the _folder_ to something like UUIDPlugin-not-used and all should be well. -----Original Message----- From: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Lukas Renggli Sent: Tuesday, June 09, 2009 4:47 PM To: Seaside - general discussion Cc: Pharo Development Subject: Re: [Pharo-project] [Seaside] Seaside 2.8.4 image crashes [newbie] This is certainly not your fault. It has probably to do with a missing plugin. I'll forward it to the Pharo list, maybe somebody knows more about this? I think I heard that problem before. Lukas On Tue, Jun 9, 2009 at 11:41 PM, Ivar Refsdal<refsdal.ivar(a)gmail.com> wrote: > Hello all, > > I'm a very fresh newbie, so the problem could just be myself. > Apologies in advance > if that is the case. However I'm getting a crash when doing the > following after starting Seaside with ./seaside.sh: > First going to http://localhost:8080/seaside/magritte/editor in a web > browser, then clicking 'Add' and then 'Save' without entering any data. > Then when clicking 'Preview' Seaside crashes with the following message: > > Segmentation fault > > 2022517340 UUID>initialize > 2022517224 Behavior>new: > 2022517132 >new > 2022517040 >uuid > 2022516948 >new > 2022516856 >defaultAccessor > 2022516764 MADescription>accessor > 2022516672 MADescription>hash > 2022516580 Dictionary>scanFor: > 2022516488 Set>findElementOrNil: > 2022516180 Dictionary>at:ifAbsent: > 2022516088 MAAdaptiveModel>readUsing: > 2022515996 MAMemento>pullRaw > 2022515840 OrderedCollection>do: > 2022515748 MAContainer>do: > 2022515656 MAMemento>pullRaw > 2022515564 MAMemento>pull > 2022515452 MACachedMemento>reset > 2022515360 MACheckedMemento>reset > 2022515268 >model:description: > 2022514976 MAContainer>asComponentOn: > 2022514884 Object>asComponent > 2022514792 MADescriptionEditor>preview 2022514700 > WASubmitButtonTag>on:of: > 2022514496 WAActionCallback>evaluateWithArgument: > 2022514036 WACallback>evaluateWithField: > 2022513760 WACallbackStream>processCallbacksWithOwner: > 2022509456 WAPresenter>processCallbackStream: > 2022509364 WAPresenter>processChildCallbacks: > 2022509272 WAComponent>decorationChainDo: > 2022509180 WAComponent>nextPresentersDo: > 2022509060 WAComponent>childrenDo: > 2022508968 SequenceableCollection>do: > 2022508836 WAComponent>childrenDo: > 2022508744 WAComponent>nextPresentersDo: > 2022508652 WAPresenter>processChildCallbacks: > 2022508560 WAPresenter>processCallbackStream: > 2022508392 WAToolFrame>processCallbackStream: > 2022508300 BlockClosure>on:do: > 2022508196 WAToolFrame>withDeprecatedHandlerDo: > 2022508104 WAToolFrame>processCallbackStream: > 2022508012 WARenderContinuation>processCallbacks: > 2022507884 WAComponent>decorationChainDo: > 2022504988 WARenderContinuation>processCallbacks: > 2022504896 WARenderContinuation>handleRequest: > 2022504804 BlockClosure>on:do: > 2022504712 WARenderContinuation>withNotificationHandler: > 2022504328 WARenderContinuation>handleRequest: > 2022501884 WASessionContinuation>value: > 2022501164 WASession>performRequest: > 2022501072 WASession>responseForRequest: > 2022500980 BlockClosure>on:do: > 2022500872 WASession>withErrorHandler: > 2022499892 BlockClosure>on:do: > 2022499800 WASession>withErrorHandler: > 2022499708 WASession>responseForRequest: > 2022499616 BlockClosure>on:do: > 2022499500 >use:during: > 2022499312 WASession>responseForRequest: > 2022499220 WASession>withEscapeContinuation: > 2022499128 >currentDo: > 2022499016 WASession>withEscapeContinuation: > 2022498904 WASession>responseForRequest: > 2022498812 WASession>incomingRequest: > 2022498548 BlockClosure>on:do: > 2022498456 WAProcessMonitor>critical:ifError: > 2022498364 BlockClosure>ensure: > 2022498272 WAProcessMonitor>critical:ifError: > 2022498640 BlockClosure>newProcess > Aborted > > I'm using this image file (no changes made): > http://www.seaside.st/distributions/Seaside-2.8.4.app.zip > Otherwise I'm on Ubuntu 9.04 i386, nothing special. Let me know if I > can provide more details. > I also tried executing the cleanup commands in the workspace, but it > didn't help. > The crash does not occur with the previous image I tried: Seaside-2.8-578.app. > > Any suggestions? > Thanks, > > Kind regards, > Ivar Refsdal > > (First post, hope everything went well.) > _______________________________________________ > seaside mailing list > seaside(a)lists.squeakfoundation.org > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside > -- Lukas Renggli http://www.lukas-renggli.ch _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

June 9, 2009

Re: [Pharo-project] About EndOfStream notification [was Streams - #nextLine]

by Schwab,Wilhelm K

Stef, A statement on pros/cons sounds like a good place to start. Re the VW/Dolphin behavior, the way to look at the errors is that they tell you what went wrong and where. If the errors truly are superfluous, then you probably should be using #nextAvailable:, which truncates and does not raise errors. You asked about a backwardly compatible solution. I think the pluggable exception idea is probably the best bet for that. Bill -----Original Message----- From: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of StÃ©phane Ducasse Sent: Tuesday, June 09, 2009 3:20 PM To: Pharo-project(a)lists.gforge.inria.fr Subject: Re: [Pharo-project] About EndOfStream notification [was Streams - #nextLine] > Nicolas, > > Adding #nextAvailable: hurts nothing, but changing #next: (and #next > too) will break existing code. In VW, it is only #next that has the > silent failure trap, and while Cincom was willing to consider a > change, they ultimately declined to make it. I am convinced that > Dolphin gets it right, but I would be surprised to see us adopt its > behavior. I would be thrilled if we did so, but doubt it will happen. > Failing such breaking changes, I need to create a way to have my code > work, which is why I started adding my own methods. > > Your pluggable exception/defaultAction idea is worth a shot. Some > simple testing should show whether it can preserve current behavior > and throw exceptions, respectively. I think I heard Stef as much as > say he would support it if it does serve both masters. Stef? As I said I would like to have a one page description of the problem, solution, pros and cons May be put it on the wiki Right now we are messy in terms of process for changes. I personnally always hated the VW behavior because we lost a lot of time with code trapping error. But I do not want to take decision on my emotion because I could be wrong. So do a one page proposal with problem, solution, pros and cons. Stef _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

June 9, 2009

Re: [Pharo-project] [Seaside] Seaside 2.8.4 image crashes [newbie]

by Lukas Renggli

This is certainly not your fault. It has probably to do with a missing plugin. I'll forward it to the Pharo list, maybe somebody knows more about this? I think I heard that problem before. Lukas On Tue, Jun 9, 2009 at 11:41 PM, Ivar Refsdal<refsdal.ivar(a)gmail.com> wrote: > Hello all, > > I'm a very fresh newbie, so the problem could just be myself. > Apologies in advance > if that is the case. However I'm getting a crash when doing the > following after starting Seaside with ./seaside.sh: > First going to http://localhost:8080/seaside/magritte/editor in a web browser, > then clicking 'Add' and then 'Save' without entering any data. > Then when clicking 'Preview' Seaside crashes with the following message: > > Segmentation fault > > 2022517340 UUID>initialize > 2022517224 Behavior>new: > 2022517132 >new > 2022517040 >uuid > 2022516948 >new > 2022516856 >defaultAccessor > 2022516764 MADescription>accessor > 2022516672 MADescription>hash > 2022516580 Dictionary>scanFor: > 2022516488 Set>findElementOrNil: > 2022516180 Dictionary>at:ifAbsent: > 2022516088 MAAdaptiveModel>readUsing: > 2022515996 MAMemento>pullRaw > 2022515840 OrderedCollection>do: > 2022515748 MAContainer>do: > 2022515656 MAMemento>pullRaw > 2022515564 MAMemento>pull > 2022515452 MACachedMemento>reset > 2022515360 MACheckedMemento>reset > 2022515268 >model:description: > 2022514976 MAContainer>asComponentOn: > 2022514884 Object>asComponent > 2022514792 MADescriptionEditor>preview > 2022514700 WASubmitButtonTag>on:of: > 2022514496 WAActionCallback>evaluateWithArgument: > 2022514036 WACallback>evaluateWithField: > 2022513760 WACallbackStream>processCallbacksWithOwner: > 2022509456 WAPresenter>processCallbackStream: > 2022509364 WAPresenter>processChildCallbacks: > 2022509272 WAComponent>decorationChainDo: > 2022509180 WAComponent>nextPresentersDo: > 2022509060 WAComponent>childrenDo: > 2022508968 SequenceableCollection>do: > 2022508836 WAComponent>childrenDo: > 2022508744 WAComponent>nextPresentersDo: > 2022508652 WAPresenter>processChildCallbacks: > 2022508560 WAPresenter>processCallbackStream: > 2022508392 WAToolFrame>processCallbackStream: > 2022508300 BlockClosure>on:do: > 2022508196 WAToolFrame>withDeprecatedHandlerDo: > 2022508104 WAToolFrame>processCallbackStream: > 2022508012 WARenderContinuation>processCallbacks: > 2022507884 WAComponent>decorationChainDo: > 2022504988 WARenderContinuation>processCallbacks: > 2022504896 WARenderContinuation>handleRequest: > 2022504804 BlockClosure>on:do: > 2022504712 WARenderContinuation>withNotificationHandler: > 2022504328 WARenderContinuation>handleRequest: > 2022501884 WASessionContinuation>value: > 2022501164 WASession>performRequest: > 2022501072 WASession>responseForRequest: > 2022500980 BlockClosure>on:do: > 2022500872 WASession>withErrorHandler: > 2022499892 BlockClosure>on:do: > 2022499800 WASession>withErrorHandler: > 2022499708 WASession>responseForRequest: > 2022499616 BlockClosure>on:do: > 2022499500 >use:during: > 2022499312 WASession>responseForRequest: > 2022499220 WASession>withEscapeContinuation: > 2022499128 >currentDo: > 2022499016 WASession>withEscapeContinuation: > 2022498904 WASession>responseForRequest: > 2022498812 WASession>incomingRequest: > 2022498548 BlockClosure>on:do: > 2022498456 WAProcessMonitor>critical:ifError: > 2022498364 BlockClosure>ensure: > 2022498272 WAProcessMonitor>critical:ifError: > 2022498640 BlockClosure>newProcess > Aborted > > I'm using this image file (no changes made): > http://www.seaside.st/distributions/Seaside-2.8.4.app.zip > Otherwise I'm on Ubuntu 9.04 i386, nothing special. Let me know if I > can provide more details. > I also tried executing the cleanup commands in the workspace, but it > didn't help. > The crash does not occur with the previous image I tried: Seaside-2.8-578.app. > > Any suggestions? > Thanks, > > Kind regards, > Ivar Refsdal > > (First post, hope everything went well.) > _______________________________________________ > seaside mailing list > seaside(a)lists.squeakfoundation.org > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside > -- Lukas Renggli http://www.lukas-renggli.ch

June 9, 2009

Re: [Pharo-project] New Extensible Inspector for Pharo-Core

by Frederic Pluquet

- the value of each instance variable is shown at left of the name of the inst var. - Descriptions are now limited to 5000 characters. The elements shown in "Elements" of an OrderedCollection are limited to the 500 first ones. FrÃ©d ---- FrÃ©dÃ©ric Pluquet UniversitÃ© Libre de Bruxelles (ULB) Assistant http://www.ulb.ac.be/di/fpluquet On Tue, Jun 9, 2009 at 9:06 PM, Alexandre Bergel <alexandre(a)bergel.eu>wrote: > > - Unfolding a branch that contains an element with a very > > very long > > printOn: seems to freeze the system. > > > > Ok, I should limit the size of the generated string (with ... at the > > end). > > > > I got an error niDescription not found. > > > > Do you have an example I can reproduce ? > > Hum... Load moose, CAnalyzer, then the linux kernel, and open a > NewInspector on the model. > I checked a bit the code, and apparently this issue will be solved if > you limit the size of the generated string. > > > - I spend a lot of time in unfolding branches to see field > > content. > > Maybe field values could be displayed without having to unfold ? > > > > Good idea. I'll see what I can do. > > Ok, I will be delighted to check it out > > Cheers, > Alexandre > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > 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 >

June 9, 2009

Re: [Pharo-project] New Extensible Inspector for Pharo-Core

by Frederic Pluquet

On Tue, Jun 9, 2009 at 7:57 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>wrote: > Hi frederic > > Here is some feedback > - Continue!!! Thanks :) > Now could you: > - add a class comment to classes. I have to browse the class > - categorise the methods. > - avoid using category in your package. > I do not want to have undocumented new code in pharo. Ok done. > > > - Instead of fields can you use > InstVar > Fields is not smalltalkish Done. > > > - when we use an inspector/explorer we can see really fast the value > of iv without > having to click on something. > may be you should propose something > classListIndex : 1 Difficult to do without speak to morphic directly. I must found another way. > > > - Why when I browse a symbol I do not get #in front? Fixed. > > - In some case we have contents what is it? Accessible elements of the collection. Changed to "Elements". For dictionaries, you have "Elements" (key => value, inspecting the value) and "Keys" (inspecting the keys objects, having a child "Value" to retrieve the associated value in the dictionary :)). > - why when I browse an array I do not get # ? > > > - roots are not obviously displayed > > It seems that you lost your symbol > > openOn: t1 > | t2 t3 t4 | > t3 := MorphicToolBuilder new. > (t4 := (t2 := self new on: t1; > yourself) buildWith: t3) > openInWorld. > ^ t2 > Yes, I have some problem with my image... I'll verify all my methods...

June 9, 2009