- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Notifiers
by Bill Schwab Dec. 20, 2008

Dec. 20, 2008

All I did was download the dev image, but you are probably correct about the OB tools. This was tried, fairly controversial, and quickly rejected on Dolphin some time back. It's fine until things get ugly, and can then end up tossing work in the trash. Being able to go straight to a debugger is great, but I think it is a poor choice for a default. The opportunity for a recursive meltdown increases dramatically, not to mention the performance hit if several try to open "all at once." Bill Wilhelm K. Schwab, Ph.D. University of Florida Department of Anesthesiology PO Box 100254 Gainesville, FL 32610-0254 Email: bschwab(a)anest.ufl.edu Tel: (352) 273-6785 FAX: (352) 392-7029 >>> cdrick65(a)gmail.com 12/20/08 12:52 PM >>> > I never implemented the pre-debug window, because I hate this extra > click that I have to do every single time I get a debugger. +1 I have never found it interesting... moreover I often forget to close it, resize, select end then full debugger to resize again... > The pre-debug window could certainly be added, but I don't see any > benefit in doing so. In my opinion the pre-debugger is a remnant of > Smalltalk-80, where there was no full debugger yet. > > Lukas > > On Sat, Dec 20, 2008 at 5:52 PM, StÃ©phane Ducasse > <stephane.ducasse(a)inria.fr> wrote: >> From my side this is not something intentional so may be this a >> preference somewhere. >> >> On Dec 20, 2008, at 5:20 PM, Bill Schwab wrote: >> >>> Hello all, >>> >>> One change I do not like is that errors bring up a debugger vs. >>> starting >>> with a notifier. Beyond a "we fear change" <g> reaction, it can get >> >> :) >> >>> >>> expensive if things are bad enough to create errors in rapid >>> succession. >>> Is there a preference I can set to get the previous behavior? >>> >>> Bill >>> >>> >>> >>> Wilhelm K. Schwab, Ph.D. >>> University of Florida >>> Department of Anesthesiology >>> PO Box 100254 >>> Gainesville, FL 32610-0254 >>> >>> Email: bschwab(a)anest.ufl.edu >>> Tel: (352) 273-6785 >>> FAX: (352) 392-7029 >>> >>> >>> _______________________________________________ >>> 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 >> > > > > -- > 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 > -- CÃ©drick _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

1 0

[Pharo-project] Fwd: could you sign the pharo license?
by StÃ©phane Ducasse Dec. 20, 2008

Dec. 20, 2008

for archive Begin forwarded message: > From: Keith Hodges <keith_hodges(a)yahoo.co.uk> > Date: December 19, 2008 5:36:26 PM CEST > To: StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > Subject: Re: could you sign the pharo license? > > StÃ©phane Ducasse wrote: >> Because I would like to have a look at some of your code and I would >> like to avoid >> making mess. >> >> Stef > All my work is licenced FRFGPL > > FREELY RECEIVED FREELY GIVEN PUBLIC LICENSE > Version 1, December 2006 > > Copyright (C) 2006 Keith Hodges > > Everyone is permitted to copy and distribute verbatim or modified > copies of this license document, and changing it is allowed as long > as the name is changed. > > FREELY RECEIVED FREELY GIVEN PUBLIC LICENSE > TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION > > 0. You just DO WHATEVER YOU WANT TO > > this is my own derivative of the WTFPL > > Keith >

5 7

Re: [Pharo-project] New pharo-dev based on 10196
by Bill Schwab Dec. 20, 2008

Dec. 20, 2008

Adrian, Loading SqueakMap might just prolong the pain. If I am following correctly, the idea would be to use a universe to load the main package and then MC to grab the rest to my image to do what I want. The ideal solution would be to get SSL registered in the universe. Is that the idea? Bill Wilhelm K. Schwab, Ph.D. University of Florida Department of Anesthesiology PO Box 100254 Gainesville, FL 32610-0254 Email: bschwab(a)anest.ufl.edu Tel: (352) 273-6785 FAX: (352) 392-7029 >>> adi(a)netstyle.ch 12/20/08 5:16 AM >>> In a recent discussion with Marcus and Lukas we came to the conclusion that a package universe for Pharo 1.0 would be the best solution. Somebody would be responsible to manage this universe and only add packages that are tested and known to work. I think this is really important that we have higher standards regarding external packages. In my experience with SqueakMap, the chance that a package actually works is less than the chance it is not working. This is a show stopper for newcomers. Our plan was to remove SqueakMap from Pharo-core, but I assume it could be put into the universe so it can be loaded again. Cheers, Adrian On Dec 20, 2008, at 01:04 , Bill Schwab wrote: > Damien, > > Thanks for making the new image. Is there a way to tell the image to > display walkbacks instead of going straight into the debugger? > > The new image seemed a nice excuse to play catch-up, which means > getting a few things loaded. > > Seaside - I recalled discussion of it, and quckly stumbled onto a > closed bug report about > > ScriptLoader new universalInstaller universe install: 'Seaside'. > > That appears to work. The cryptography team's work will be important. > This gets weird fast. I have a 3.9 image where it is installed > correctly and works; I have very little idea how that happened. My > subsequent installation attempts appear not to be complete. > > SqueakMap appears to be going away in Pharo. Replacing it appear to > be > Installer, ScriptLoader, and maybe some of your tools to build the > developer images. Is there a clear correct way to install packages > now? > Put another way, if I make an attempt to sort out installing the > cryptography and SSL classes in Pharo, how would recommend attacking > it? > > Pharo is not even in beta yet, so no complaints, but I am missing > something on how to go from a new core image to something that is > ready > for use. > > Bill > > > > Wilhelm K. Schwab, Ph.D. > University of Florida > Department of Anesthesiology > PO Box 100254 > Gainesville, FL 32610-0254 > > Email: bschwab(a)anest.ufl.edu > Tel: (352) 273-6785 > FAX: (352) 392-7029 > > > _______________________________________________ > 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

2 1

Re: [Pharo-project] Fwd: [squeak-dev] Re: [ANN] ConflictFinder (help needed!)
by Bill Schwab Dec. 20, 2008

Dec. 20, 2008

Stef, This looks great, but I think it underscores something that has bothered me for a while: the various packages should not be prompting on installation. The updated Seaside installation is vastly improved, but it still comes to a dead halt over user-name/password for the configuration utility; those things can be set by a do-it after the package is installed, and I think that should be the default approach, so that loading the code does just that. Just my 2 asCents. Bill Wilhelm K. Schwab, Ph.D. University of Florida Department of Anesthesiology PO Box 100254 Gainesville, FL 32610-0254 Email: bschwab(a)anest.ufl.edu Tel: (352) 273-6785 FAX: (352) 392-7029

1 0

Re: [Pharo-project] New pharo-dev based on 10196
by Bill Schwab Dec. 20, 2008

Dec. 20, 2008

Stef, You are certainly welcome to beat me to it, though it could be a simple matter of my not having installed all of it. My goal was/is to install the cryptography team's work, including SSL sockets. One possible explanation is as follows: (1) the main package wants to be installed from a universe; (2) SSL is separate. That's just a guess. I will take another crack at it. Thanks! Bill Wilhelm K. Schwab, Ph.D. University of Florida Department of Anesthesiology PO Box 100254 Gainesville, FL 32610-0254 Email: bschwab(a)anest.ufl.edu Tel: (352) 273-6785 FAX: (352) 392-7029 >>> stephane.ducasse(a)inria.fr 12/20/08 2:59 AM >>> Bill report any problem to load packages and we willcheck what we can do? Do you have something that we can repeat. And indeed we prefer MC as package format. Stef On Dec 20, 2008, at 1:04 AM, Bill Schwab wrote: > Damien, > > Thanks for making the new image. Is there a way to tell the image to > display walkbacks instead of going straight into the debugger? > > The new image seemed a nice excuse to play catch-up, which means > getting a few things loaded. > > Seaside - I recalled discussion of it, and quckly stumbled onto a > closed bug report about > > ScriptLoader new universalInstaller universe install: 'Seaside'. > > That appears to work. The cryptography team's work will be important. > This gets weird fast. I have a 3.9 image where it is installed > correctly and works; I have very little idea how that happened. My > subsequent installation attempts appear not to be complete. > > SqueakMap appears to be going away in Pharo. Replacing it appear to > be > Installer, ScriptLoader, and maybe some of your tools to build the > developer images. Is there a clear correct way to install packages > now? > Put another way, if I make an attempt to sort out installing the > cryptography and SSL classes in Pharo, how would recommend attacking > it? > > Pharo is not even in beta yet, so no complaints, but I am missing > something on how to go from a new core image to something that is > ready > for use. > > Bill > > > > Wilhelm K. Schwab, Ph.D. > University of Florida > Department of Anesthesiology > PO Box 100254 > Gainesville, FL 32610-0254 > > Email: bschwab(a)anest.ufl.edu > Tel: (352) 273-6785 > FAX: (352) 392-7029 > > > _______________________________________________ > 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

1 0

[Pharo-project] Fwd: [squeak-dev] Re: [ANN] ConflictFinder (help needed!)
by StÃ©phane Ducasse Dec. 20, 2008

Dec. 20, 2008

Begin forwarded message: > From: Andreas Raab <andreas.raab(a)gmx.de> > Date: December 20, 2008 7:52:01 AM CEST > To: The general-purpose Squeak developers list <squeak-dev(a)lists.squeakfoundation.org > > > Subject: [squeak-dev] Re: [ANN] ConflictFinder (help needed!) > Reply-To: The general-purpose Squeak developers list <squeak-dev(a)lists.squeakfoundation.org > > > > Some progress: >> [x] Find a good name for the integration testing project. > > Done. The project is now on http://squeaksource.com/InT.html (as you > can see I got really creative ;-) BTW, the project is world-writable > - if you have an improvement just go right at it and post it into > the repository. > >> [x] Following dependencies. > > Done. ConflictFinder now also has a utility method that you can use > to run the entire process: > > ConflictFinder findConflictsInUniverse: > UUniverse systemUniverse updatePackagesViaWWW > >> [x] Providing the "right" answers automatically > > Done. ConflictFinder now provides answers for everything (and as you > can guess they are not particularly intelligent answers ;-) When > input is required, ConflictFinder logs both question and answer so > that if something goes wrong we can find out why. For confirmations > it flips a coin so be aware that a question like "would you like to > send 1 million dollars to Tim now?" might get the wrong answer. > > Also, logging has been improved to report warnings (like MC warnings > about unresolved dependencies) as well as errors if anything should > go wrong during load. > > Finally, I removed the LFP/Installer dependencies since I didn't > want to modify the base 3.10.2 system (loading LFP / Installer could > affect other parts of the system). > > Which means that in theory you should now be able to: > * Load the Integration package into 3.10.2 > * Fire up the above expression > * Have it run until Squeak runs out of memory > * Post the report about your run here. > > Since the weekend is up ahead maybe one or two of you have a bit of > time to give this a try. I'm currently running the test in the > background; below is my output so far (it looks like OBTraits is > missing a dependency in 3.10). > > Cheers, > - Andreas > > > --------------------------------------------------------------------- > > Analysing base system ... done. > > OSProcess > --------- > Loading ... > Finding conflicts... > > FFI > --- > Loading ... > Finding conflicts... > > Algernon > -------- > Loading ... > Question: Would you like to open an instance of Algernon on the > current project? > Answer: false > Finding conflicts... > > Video and Image Processing > -------------------------- > Loading ... > Finding conflicts... > > SmaCC runtime > ------------- > Loading ... > Finding conflicts... > > DynamicBindings > --------------- > Loading ... > Finding conflicts... > > SimpleLog > --------- > Loading ... > Finding conflicts... > > KomServices > ----------- > Loading ... > Finding conflicts... > > KomHttpServer > ------------- > Loading ... > Finding conflicts... > > SeasideAdaptersCompatibility > ---------------------------- > Loading ... > Finding conflicts... > > PostgreSQL Client > ----------------- > Loading ... > Finding conflicts... > > Lisp > ---- > Loading ... > Finding conflicts... > > Seaside > ------- > Loading ... > Question: Please choose a username for > the application 'config' > Answer: 2 - yeah, sure whatever > Finding conflicts... > > NetStrings > ---------- > Loading ... > Finding conflicts... > > Telnet > ------ > Loading ... > Question: The default fixed-width font is abominable. > Do you want me to create a better fixed-width font for you? > Answer: true > Finding conflicts... > > AST > --- > Loading ... > Finding conflicts... > > HTTPClient > ---------- > Loading ... > Finding conflicts... > Object>>displayString (conflicts with Seaside) > String>>trimBlanks (conflicts with Seaside) > > Refactoring Engine > ------------------ > Loading ... > Finding conflicts... > > Polymorph Widgets > ----------------- > Loading ... > Finding conflicts... > > Speech > ------ > Loading ... > Finding conflicts... > > TraitsOmniBrowser > ----------------- > Loading ... > WARNING: This package depends on the following classes: > OBMethodNode > OBClassAwareNode > OBSystemBrowser > OBClassCategoryNode > OBMethodCategoryNode > OBMethodDefinition > OBClassNode > You must resolve these dependencies before you will be able to load > these definitions: > OBAliasMethodNode > OBAliasMethodNode classSide>>on: > OBAliasMethodNode>>alias > OBAliasMethodNode>>alias: > OBAliasMethodNode>>fullName > OBAliasMethodNode>>name > OBAliasMethodNode>>source > OBClassAwareNode>>addCommentComponentsTo: > OBClassAwareNode>>addComponentsTo: > OBClassAwareNode>>browse > OBClassAwareNode>>defineClass:notifying: > OBClassAwareNode>>indent > OBClassAwareNode>>indentedNameIndicatingAbstractness > OBClassAwareNode>>signalSelectionOf: > OBClassAwareNode>>superior: > OBClassCategoryNode>>classAndTraitCommentsHierarchically > OBClassCategoryNode>>classesAndComponentTraits > OBClassCategoryNode>>classesAndTraitsHierarchically > OBClassCategoryNode>>classesShowingAbstractness > OBClassCategoryNode>>commentsShowingAbstractness > OBClassCategoryNode>>metaclassesAndClassTraitsHierarchically > OBClassCategoryNode>>metaclassesShowingAbstractness > OBClassCategoryNode>>registerAsShowingAbstractness: > OBClassNode>>categories > OBClassNode>>categoryNodeNamed: > OBClassNode>>dropSelector > OBClassNode>>localCategory > OBClassNode>>rename > OBClassNode>>traits > OBClassNode>>virtualCategories > OBClassTraitNode > OBClassTraitNode>>nonMetaName > OBClassTraitNode>>setClass: > OBClassTraitNode>>stringName > OBLocalMethodCategoryNode > OBLocalMethodCategoryNode classSide>>localCategory > OBLocalMethodCategoryNode classSide>>on: > OBLocalMethodCategoryNode>>category > OBLocalMethodCategoryNode>>methodReferences > OBLocalMethodCategoryNode>>methods > OBMethodCategoryNode classSide>>on:inTrait: > OBMethodCategoryNode>>methodReferences > OBMethodCategoryNode>>signifier > OBMethodCategoryNode>>signifyingName > OBMethodDefinition>>category > OBMethodDefinition>>text > OBMethodNode>>browseInheritance > OBMethodNode>>browseVersions > OBMethodNode>>dropOnTraitTransformation: > OBMethodNode>>isDescendantOfMethodCat: > OBMethodNode>>isRequired > OBMethodNode>>name > OBMethodNode>>signifyingName > OBMethodNode>>textcolor > OBMethodNode>>virtualMethodCategoryPrimeAttribute > OBNoCommentNode > OBNoCommentNode classSide>>on: > OBNoCommentNode>>color > OBNoCommentNode>>indent > OBNoCommentNode>>name > OBNoCommentNode>>setClass: > OBNoCommentNode>>stringName > OBNoCommentNode>>text > OBNonLocalMethodNode > OBNonLocalMethodNode>>actions > OBNonLocalMethodNode>>exclude > OBNonLocalMethodNode>>isAlias > OBNonLocalMethodNode>>isConflict > OBNonLocalMethodNode>>removeAlias > OBNonLocalMethodNode>>species > OBNonLocalMethodNode>>textcolor > OBRequiredBrowser > OBRequiredBrowser classSide>>defaultMetagraph > OBRequiredBrowser classSide>>title > OBRequiredSelectorNode > OBRequiredSelectorNode>>proposedHeader > OBRequiredSelectorNode>>remove > OBRequiredSelectorNode>>source > OBRequiredSelectorNode>>species > OBSystemBrowser classSide>>onTrait: > OBSystemBrowser classSide>>onTrait:category: > OBSystemBrowser classSide>>onTrait:selector: > OBSystemBrowser classSide>>openOnTrait: > OBSystemBrowser classSide>>openOnTrait:category: > OBSystemBrowser classSide>>openOnTrait:selector: > OBTraitCommentNode > OBTraitCommentNode classSide>>on: > OBTraitCommentNode>>setClass: > OBTraitCommentNode>>stringName > OBTraitCommentNode>>text > OBTraitCommentNode>>text: > OBTraitNode > OBTraitNode>>actions > OBTraitNode>>addToTraitCompositionOf: > OBTraitNode>>color > OBTraitNode>>indent > OBTraitNode>>name > OBTraitNode>>remove > OBTraitNode>>species > OBTraitNode>>stringName > OBTraitNode>>surroundingHierarchy > OBTraitNode>>trait > OBTraitStructureBrowser > OBTraitStructureBrowser classSide>>addTo:class:comment:metaclass: > OBTraitStructureBrowser classSide>>defaultMetaNode > OBTraitStructureBrowser classSide>>defaultMetagraph > OBTraitStructureBrowser classSide>>hierarchicalMetaNodeWithSignifiers > OBTraitStructureBrowser classSide>>temp > OBTraitStructureBrowser classSide>>title > OBTraitStructureBrowser>>messageCategoryList > OBTraitStructureBrowser>>messageList > OBTraitStructureBrowser>>onClass:category: > OBTraitStructureBrowser>>onTrait:category: > OBTraitTransformationNode > OBTraitTransformationNode classSide>>on: > OBTraitTransformationNode>>actions > OBTraitTransformationNode>>categories > OBTraitTransformationNode>>classRef > OBTraitTransformationNode>>dropSelector > OBTraitTransformationNode>>localCategory > OBTraitTransformationNode>>setTransformation: > OBTraitTransformationNode>>stringName > OBTraitTransformationNode>>trait > OBTraitTransformationNode>>traits > OBTraitTransformationNode>>transformation > OBVirtualMethodCategoryNode > OBVirtualMethodCategoryNode classSide>>actionsForParent: > OBVirtualMethodCategoryNode classSide>>on:inClass: > OBVirtualMethodCategoryNode classSide>>on:inTrait: > OBVirtualMethodCategoryNode classSide>>onSignifier:inClass: > OBVirtualMethodCategoryNode>>definition > OBVirtualMethodCategoryNode>>methods > OBVirtualMethodCategoryNode>>setName:class:signifier: > OBVirtualMethodCategoryNode>>signifier > OBVirtualMethodCategoryNode>>signifyingName > OBVirtualMethodCategoryNode>>species > > Finding conflicts... > LazyListMorph>>display:atRow:on: (conflicts with Polymorph Widgets) > > Folktale > -------- > Loading ... > Finding conflicts... > > Magritte-Model > -------------- > Loading ... > Finding conflicts... > > OmniBrowser > ----------- > Loading ... > Finding conflicts... > Text>>colorAt: (conflicts with TraitsOmniBrowser) > > Installer > --------- > Loading ... > WARNING: You are about to load new versions of the following > packages that have unsaved changes in the image. If you continue, > you will lose these changes. > > Installer-Core > Finding conflicts... > > Monticello2-Core > ---------------- > Loading ... > Finding conflicts... > > PieChartMorph > ------------- > Loading ... > Finding conflicts... > > Shout > ----- > Loading ... > Finding conflicts... > > SandstoneDb > ----------- > Loading ... > Finding conflicts... > > Pier-Model > ---------- > Loading ... > Finding conflicts... > > PWS > --- > Loading ... > Finding conflicts... > > OmniBrowser-TraitsIntegration > ----------------------------- > Loading ... > Finding conflicts... > > VBRegex > ------- > Loading ... > Finding conflicts... > > SqCVS > ----- > Loading ... > Finding conflicts... > >

1 0

[Pharo-project] Fwd: [squeak-dev] [ANN] ConflictFinder (help needed!)
by StÃ©phane Ducasse Dec. 20, 2008

Dec. 20, 2008

Begin forwarded message: > From: Andreas Raab <andreas.raab(a)gmx.de> > Date: December 17, 2008 6:52:02 AM CEST > To: The general-purpose Squeak developers list <squeak-dev(a)lists.squeakfoundation.org > > > Subject: [squeak-dev] [ANN] ConflictFinder (help needed!) > Reply-To: The general-purpose Squeak developers list <squeak-dev(a)lists.squeakfoundation.org > > > > Folks - > > In light of Greg's recent issues with conflicts between packages I > spent this evening writing a little tool called ConflictFinder. What > it does is taking a set of actions and computes conflicts arising > from running these actions. In its simplest use it works like here: > > ConflictFinder findConflictsIn:{ > 'FooPackage' -> [(FileStream readOnlyFileNamed: 'Foo.st') fileIn]. > 'MantisFix1234' -> [Installer mantis ensureFix: 1234]. > 'Mumble' -> [MczInstaller installFileNamed: 'Foo-xyz. > 123.mcz']. > }. > > It prints the analysis to the transcript by default but you can > override its log file appropriately. Since I didn't know how to get > the universe browser to load stuff automatically, I decided to cheat > and run it like here to test it on the problem in question: > > ConflictFinder findConflictsIn:{ > 'SmallDEVS' -> [self notify: 'Please load SmallDEVS']. > 'Polymorph' -> [self notify: 'Please load Polymorph']. > }. > > After loading the packages manually when prompted the analysis > showed this result: > > LabelMorph (conflicts with SmallDEVS) > LabelMorph>>initialize (conflicts with SmallDEVS) > LabelMorph>>drawOn: (conflicts with SmallDEVS) > StringMorph>>minHeight (conflicts with SmallDEVS) > > So there is a conflict between LabelMorph in the packages *as well > as* StringMorph>>minHeight (which happens to be an equivalent > modification but shows that the tool does indeed unearth unexpected > conflicts). > > The next step would be to find someone who ties this into the > universe browser and just starts loading packags randomly. At which > point a concerted community action of just people reporting back > their results should be able of finding 90% of the conflicts in the > current PU in no time. > > Any volunteers for helping with this? > > Cheers, > - Andreas >

1 0

Dec. 20, 2008

Begin forwarded message: > From: "Eliot Miranda" <eliot.miranda(a)gmail.com> > Date: December 19, 2008 7:52:21 PM CEST > To: "The general-purpose Squeak developers list" <squeak-dev(a)lists.squeakfoundation.org > > > Subject: Re: [squeak-dev] Re: Resume Problems > Reply-To: The general-purpose Squeak developers list <squeak-dev(a)lists.squeakfoundation.org > > > > Hi Zulq, > > I made sure this was fixed in VisualWorks. Steve Dahl and I > fixed this together. Here's an analogous fix for Squeak. The > essential change is to make Object>>doesNotUnderstand: check if the > MessageNotUnderstood exception was handled or not, so > > MessageNotUnderstood new > message: aMessage; > receiver: self; > signal. > ^ aMessage sentTo: self. > > is replaced with > > (exception := MessageNotUnderstood new) > message: aMessage; > receiver: self. > resumeValue := exception signal. > ^exception reachedDefaultHandler > ifTrue: [aMessage sentTo: self] > ifFalse: [resumeValue] > > HTH > > On Fri, Dec 19, 2008 at 8:13 AM, Zulq Alam <me(a)zulq.net> wrote: > Hi Klaus, > > > Klaus D. Witzel wrote: > Nah, the result has nothing to do with #on:do: resuming with 1, you > better > try > > [('abc' + 1) + 1] > on: MessageNotUnderstood > do: [:e | e resume: -1] > > which still says 2. This because someone, behind you back, put > #asNumber > arithmethic into ByteString ... now this attempts (Number readFrom: > 'abc') > which gives 0 for your +1 +1 and so 2. > > You may want to start DNU testing with ('abc' break; + 1) and then see > where it goes. > > Hmm... I think something is not right or at the very least the > semantics are subtly different than I expect. > > VisualWorks: > [Object new blah + 1] > on: MessageNotUnderstood > do: [:e | e resume: 1] " = 2 " > > [MessageNotUnderstood signal + 1] > on: MessageNotUnderstood > do: [:e | e resume: 1] " = 2 " > > Squeak: > [Object new blah + 1] > on: MessageNotUnderstood > do: [:e | e resume: 1] " infinite recursion!!! " > > [MessageNotUnderstood signal + 1] > on: MessageNotUnderstood > do: [:e | e resume: 1] " = 2 " > > > If I look at doesNotUnderstand: in both I see that in VW the resumed > value is returned. In Squeak is is not... surely this can't be right? > > As for my problem, I think a simpler solution is to pass an adaptor/ > proxy object to the block rather than the tag itself. This adaptor > can then marshal behaviour such that it will act as a message eating > null if it receives an MNU from the tag it's looking after. > > Thanks, > Zulq. > > >

1 0

Dec. 20, 2008

Begin forwarded message: > Resent-From: Bert Freudenberg <bert(a)freudenbergs.de> > From: Bert Freudenberg <bert(a)freudenbergs.de> > Date: December 17, 2008 12:28:26 AM CEST > Resent-To: Sugar Devel <sugar-devel(a)lists.sugarlabs.org> > To: Sugar Devel <sugar-devel(a)lists.sugarlabs.org> > Resent-Cc: OLPC Etoys <etoys(a)lists.laptop.org>, OLPC Development <devel(a)lists.laptop.org > > > Subject: [Etoys] [RELEASE] Etoys 4.0 > > (resent with new download URLs and a bit more prose) > > Hi folks, > > this is the first release of Etoys 4.0. The major version jump > signifies the end of our two-year relicensing effort. > > Originally released in 1996, Apple relicensed the Squeak core under > the Apache 2.0 license in October 2006 - thanks to Steve, Alan, and > the lawyers involved. Then, Viewpoints Research collected written > relicensing agreements from several hundred later contributors under > the MIT license - thanks to Kim, and the Squeak community volunteers. > Finally, all the code in Etoys not explicitly covered by a relicensing > agreement was removed, or rewritten, or reverted to an earlier version > - kudos to Yoshiki for the bulk of that work. > > Looking forward to see Etoys properly packaged in more distros now :) > > We may have broken stuff while removing and rewriting, so please > report any oddities you notice. > > Note: Etoys comes in two parts, one is the base (in Sugar Glucose, but > will actually run on all platforms given a recent Squeak virtual > machine) and one the activity bundle (in Fructose). Following the > naming conventions the lower-case "etoys" package is the base while > the activity is capitalized as "Etoys". > > == Sources == > > http://download.sugarlabs.org/sources/sucrose/glucose/etoys/etoys-4.0.2201.… > > http://download.sugarlabs.org/sources/sucrose/fructose/Etoys/Etoys-97.tar.gz > > == Packaged == > > http://etoys.laptop.org/rpms/etoys-4.0.2201-1.noarch.rpm > > http://etoys.laptop.org/rpms/Etoys-97.xo > > == News == > > * removed/reverted/rewrote all methods not covered by Apache/MIT > license > * various fixes (#8928, #8929, #8879, #9058, and others) > > - Bert (for the Etoys team) - > > > _______________________________________________ > Etoys mailing list > Etoys(a)lists.laptop.org > http://lists.laptop.org/listinfo/etoys >

3 5

Re: [Pharo-project] New pharo-dev based on 10196
by Bill Schwab Dec. 20, 2008

Dec. 20, 2008

Keith, I'll have a look. My interest will probably be limited to Pharo; the 3.9 image is one of line of images I built to keep an eye on Squeak. I ended up looking at it today only because I knew I had the SSL sockets working somewhere. I'm surprised how easy it was to miss that the newer attempts were incomplete. That said, I think I now know what to look for, and where to go for reference of what needs to be present. Thanks, Bill Wilhelm K. Schwab, Ph.D. University of Florida Department of Anesthesiology PO Box 100254 Gainesville, FL 32610-0254 Email: bschwab(a)anest.ufl.edu Tel: (352) 273-6785 FAX: (352) 392-7029 >>> keith_hodges(a)yahoo.co.uk 12/19/2008 9:00:28 PM >>> Bill Schwab wrote: > Damien, > > Thanks for making the new image. Is there a way to tell the image to > display walkbacks instead of going straight into the debugger? > > The new image seemed a nice excuse to play catch-up, which means > getting a few things loaded. > > Seaside - I recalled discussion of it, and quckly stumbled onto a > closed bug report about > > ScriptLoader new universalInstaller universe install: 'Seaside'. > > That appears to work. The cryptography team's work will be important. > This gets weird fast. I have a 3.9 image where it is installed > correctly and works; I have very little idea how that happened. My > subsequent installation attempts appear not to be complete. > > SqueakMap appears to be going away in Pharo. Replacing it appear to be > Installer, ScriptLoader, and maybe some of your tools to build the > developer images. Is there a clear correct way to install packages now? > Put another way, if I make an attempt to sort out installing the > cryptography and SSL classes in Pharo, how would recommend attacking > it? > > Pharo is not even in beta yet, so no complaints, but I am missing > something on how to go from a new core image to something that is ready > for use. > > Bill > Hi Bill, I maintain that your best bet for keeping all the balls in the air for whatever target images that you have in mind will be Sake/Packages. load: Installer install: 'Packages'. And have a look around. The Pharo class is already there if you need a specialised install proceedure for pharo. Keith _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

1 0